Repository navigation
refactor(mmwstack): follow pstack and cut why to one file, recall starts its own investigators - #1527
Merged
Merged
Conversation
recall step 4 starts one read-only investigator per source the topic touches on the `judgment and prose` role, with the tools that source needs, instead of handing the sweep to the `why` skill. The `reader` role does not fit because its droid cannot run git or `gh`. The glossary gains the Recall investigator term. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
`why` answers from the record, not the code. It reads the commits and PR discussions behind the target and each later change, looks at other sources when the trail is thin, cites what the authors wrote, marks its own inferences, and says what the record does not answer. It starts no subagent. The investigators, the synthesizer, the confidence framework and the twelve `references/` files are gone, with the `why investigators` and `why synthesizer` roles (now retired names in `setup-mmwstack`) and the investigation glossary terms that only described them. The glossary keeps Null result and Evidence gap, which `why` and Recall still use. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
blast-radius pulls the PR and its commits itself and drops the "same rules as why" pointer. teach no longer narrows `why` because of a full sweep that does not exist. The README row and the understand guide describe `why` as an answer from the record that cites the authors, marks inferences, and says what the record does not answer. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Marks mmwstack as caught up with pstack 0.15.42 (cursor/plugins bf0c7cd, #1236). Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
why is now one short file that starts no subagent, so Comment Sicko runs it on a symbol itself when a claim rests on history. Drop the `needs: why` handoff from the role, the no-comments step 1 and the build-and-clean guide. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
This was referenced Nov 15, 2026
This was referenced Nov 15, 2026
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
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.
Why
pstack's latest upstream update (cursor/plugins#1236) cut
whyto one short file, deleted its investigators, synthesizer and references, and maderecallstart its own source investigators. mmwstack still ran seven evidence categories in parallel. This PR delivers #1523, part of #1519, and sets the plugin version to 0.15.42, the upstream version mmwstack now follows. It builds on #1522, so its base is that branch.What changed
whyis one paragraph in one file. It answers from the commits and PR discussions behind the code, looks further when that trail is thin, cites what the authors wrote, marks inferences as inferences, and says what the record does not answer. It starts no subagent. The twelve reference files are gone.recallstarts one investigator per source the topic touches, on thejudgment and proserole. Each is told to read only and write nothing, and gets the tools its source needs.why investigatorsandwhy synthesizerroles are retired insetup-mmwstack. The investigation glossary drops the terms that described them and gains Recall investigator.whyitself when a claim rests on history. Theneeds: whyhandoff is gone, becausewhyno longer starts agents.blast-radius,teach, the README and guide 03 describe the newwhy. Both plugin manifests read 0.15.42.Scope
claude-codedocs from the upstream commit.~/.agents. The owner reruns/setup-mmwstackto drop the retired droids and adds thereaderline.Tradeoffs
recallinvestigators do not usereader, because its droid is read-only and cannot rungitorgh.whydescription is upstream's short one. The old text promised parallel evidence categories, which no longer exist.Blast Radius
Door: two-way. The text reverts cleanly. The one-way part is outside this PR: deleting the retired droids and rewriting
~/.agents/mmwstack-models.md, which happens only when the owner reruns setup. Until thenrecalland the mode's default reader report an unfilledreaderrole.Verification
whyas the main chat on "why did mmwstack get renamed from pstack". It answered from the rename commit and PR Add mmwstack and run its delegates and owners on Droid #1514 with quotes, marked its inferences, and said the record gives no stated motive. It started no subagent. The answer is on the ticket.disable-model-invocationanywhere undermmwstack/.scripts/checkpasses.