Repository navigation
chore: sync with cursor/plugins — feat(pstack): new default models, one-file why and how, statechart fixes, sharpen and reflect text (#1236) - #81
Merged
SmailG merged 2 commits intoNov 15, 2026
Conversation
…xes, sharpen and reflect text (cursor#1236) * feat(pstack): have sharpen ask for prototypes and swap a reflect example - sharpen: the rewritten prompt now asks the agent to prototype any choice an experiment can settle and recommend an option from what it observed. Product and preference choices stay with the user. The README and guide describe the new last line. - reflect: the synthesizer's example of a detail that drifts is now a function rename instead of a model-name rename. Co-authored-by: lauren <poteto@users.noreply.github.com> * chore(pstack): bump to 0.15.37 Co-authored-by: lauren <poteto@users.noreply.github.com> * fix(pstack): report the spec's line and column when SANY cannot read it When SANY's XML run fails, check() reruns SANY in plain mode and reports that run's error section, capped at 40 lines. The message used to be the tail of the XML run, which is a Java stack trace. Three tests cover an unknown name, a parse error, and twelve unknown names. Co-authored-by: lauren <poteto@users.noreply.github.com> * chore(pstack): bump to 0.15.38 Co-authored-by: lauren <poteto@users.noreply.github.com> * fix(pstack): enter a parent state through its border in statechart charts An arrow from outside a parent state could run through the parent's title. The Mermaid backend now ends such an arrow at the parent's border, and the parent's start marker goes on to the state inside. A lone arrow keeps its label. When one state leads to several states inside, each label moves to the start marker's arrow. A parent that two or more states lead into keeps its direct arrows. Tests share one reader of a chart's arrows in test/drawn.ts. Two chart tests and one render test cover the new drawing. Co-authored-by: lauren <poteto@users.noreply.github.com> * chore(pstack): bump to 0.15.39 Co-authored-by: lauren <poteto@users.noreply.github.com> * refactor(pstack): cut why to one short file that names no source why is now one file with a 48-word body. It tells the agent to answer from the commits and PR discussions behind the code, to look further when that trail is thin, to cite what the authors wrote, to mark inferences, and to say what the record does not answer. The investigators, the synthesizer, the model routing, the output format, and the files under references/ are deleted. - recall starts its own investigator for each source instead of borrowing why's investigators and source playbooks. - blast-radius and teach stop pointing at parts why no longer has. - poteto-mode keeps its route to why and drops it from the lists of skills that set their own subagent type or model roles. - setup-pstack drops the two why roles. - poteto-help, the README and the guide describe the new why. Co-authored-by: lauren <poteto@users.noreply.github.com> * chore(pstack): bump to 0.15.40 Co-authored-by: lauren <poteto@users.noreply.github.com> * refactor(pstack): stop routing to how and cut how to one file how is now one file. It starts one read-only subagent with a short brief and presents the output. The model routing, complexity gate, explorers, output format and both prompt templates are deleted. poteto-mode no longer runs how. The trigger line is gone. The Investigation, Feature, Bug fix, Hillclimb, Perf issue and Refactoring playbooks, architect, no-comments and its comment-sicko agent tell the agent to trace the code itself. setup-pstack drops the two how roles. The Benny automation skills trace directly and no longer require how. teach and the poteto-help catalog keep how. The README and guide describe the new flow. Co-authored-by: lauren <poteto@users.noreply.github.com> * chore(pstack): bump to 0.15.41 Co-authored-by: lauren <poteto@users.noreply.github.com> * feat(pstack): route defaults to Fable 5.2, Opus 5.5 and Gemini 4 Carbon The role labels and the four budgets stay. Only the defaults change. - hardest tasks: claude-fable-5-2-max. - feature, refactoring, bug-fix, perf-issue, hillclimb: claude-opus-5-5-xhigh. - swarm workers, reflect tooling, verification and trivial mechanical edits: claude-opus-5-5-high-fast. - arena runners, arena cross-judge pool, architect runners and interrogate reviewers: claude-fable-5-2-high, claude-opus-5-5-high-fast, gemini-4-carbon-high. Fable is its own family, apart from the other Claude models, and the two are one vendor for arena's cross-judge. Gemini tops out at high, and Fable 5.2 and Gemini have no fast slug. Each budget now moves a role's default effort by steps, so large still equals the defaults. setup-pstack writes a defaults marker line. A rule without it is from an older setup, and its old default values take the new defaults on the next run. Other values stay as the user's choice. Grok 4.7 is no longer a default. setup-pstack names its slug pattern once, to recognize an old default in an existing rule file. Co-authored-by: lauren <poteto@users.noreply.github.com> * chore(pstack): bump to 0.15.42 Co-authored-by: lauren <poteto@users.noreply.github.com> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>
…w-default-models-one-file-why-and-how-statecha
SmailG
deleted the
sync/feat-pstack-new-default-models-one-file-why-and-how-statecha
branch
November 15, 2026 13:26
|
Caution Review failedThe pull request is closed.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
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.
Upstream changes
bf0c7cd feat(pstack): new default models, one-file why and how, statechart fixes, sharpen and reflect text (cursor#1236)
Automated sync via sync-upstream workflow