docs(process): record the Discussions round-log, agent identity and root-cause grouping - #157
Merged
Merged
Conversation
Round records moved to GitHub Discussions in 2026-08 but nothing in the repo said so, and /next-issue still assumed one issue means one fix site. - AGENTS.md: name Discussions as the round-record store and log.md as closed; correct the area label range (13 -> 15, and say to count rows). - next-issue: write every gh call as ms609-agent and request review from the maintainer; read each red-team body for its full file list, since issues are now filed by root cause and routinely span several sites; never brief a chip against an issue that asks for a decision. - next-issue: carry a verifier's corrections into the brief in place of the finder's original numbers. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The area:N row was edited on both sides: cpp-search clarified that the label marks code ownership rather than the finding round, this branch noted that the range grows. Both are kept. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The identity paragraph restated AGENTS.md's own Agent identity section; it now carries only what is specific to dispatch. "One issue is no longer one fix site" and "the old coordination-commit exception is gone" describe a transition rather than a rule, and the `task` label was defined by the file it was migrated from. log.md no longer keeps `last_focus:`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation only — no package code, no tests, nothing for CI to compile.
Three process facts established in the 2026-08-05/06 red-team sessions were live in
practice but written down nowhere the next agent would look.
Round records are GitHub Discussions. The move happened because
dev/red-team/log.mdsits on a protected branch, so a finished round's record was hostage to a code review it
has nothing to do with — four completed rounds and 56 findings once sat stranded on an
unmerged PR while the file in
cpp-searchstill named a stalelast_focus:. ButAGENTS.mdstill pointed atlog.mdas rotation state, so an agent following it wouldappend there, exactly as this session did three times before the gap was noticed.
One issue is no longer one fix site.
/red-teamnow files by root cause: 31 verifiedcandidates became 7 issues, several spanning multiple files.
/next-issuesizes tranchesand checks file collisions per issue, so it would have under-sized every tranche and missed
collisions in files named only in a body.
Chips must not be briefed against decision issues. A chip given one picks a branch and
presents it as a fix — a reviewable-looking PR that quietly settles a question the
maintainer meant to answer.
Also corrects the
area:Nlabel range (13→15) and says to count the rows rather thantrust the range, which is how it went stale.
The corresponding
/red-teamskill changes are user-level (~/.claude/skills/red-team/)and not in this repo.
🤖 Generated with Claude Code