You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
marketplace: pstack recheck and listing budget #7588
The pstack upstream record is re-pinned at cursor/plugins 99743e9c15 with the newer principles
re-mapped, and the fleet listing budget is set from the pilot's measured readings.
Send Automation Lanes the cluster-first and filing-rule advice (D68, Q63); already messaged (GUIDE
121), so this item only confirms it landed.
Key interfaces
None (the design names no contract for these items; the module layout lists "Housekeeping: one
pstack recheck PR at 99743e9c15; skillListingBudgetFraction stays 0.07 until the description pilot
ships").
Slices, filed when this phase starts: pstack-recheck, listing-budget.
Done when
rg -c '99743e9c15' docs/upstream/cursor-pstack.md is at least 1 (0 on main) and bash scripts/check-upstream-drift.sh exits 0.
The listing-budget value is set only after the description pilot's readings are posted.
Out of scope
Placing the re-mapped principles (discipline thread).
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
I read this as two housekeeping items. The first is to re-pin the pstack upstream record at cursor/plugins 99743e9c15 and re-map the newer principles. It is done when docs/upstream/cursor-pstack.md mentions that commit and scripts/check-upstream-drift.sh exits 0. The second is to set the fleet listing budget only after the description pilot's readings are posted. skillListingBudgetFraction stays 0.07 until then. The issue records its decisions and done-when items, so I have no open questions.
The listing-budget item waits on #7582. I could not check whether #7571 or #7582 are still open, because they are outside the open-issues list I was given. Related: #6458 and #7052. I found no likely duplicates.
The work-resolve-issue lane stopped on this issue (already-done): the run found the issue's work already on the default branch at a commit it cites, so the issue closes.
Its reason cites no pull request merged into the default branch, or commit on it, made after the issue opened whose commit message closes this issue, so it retries instead of closing.
It keeps agent-ready, and work-unblock starts it again (retry 2 of 2).
In the run's words:
already-done: both done-when items are already met on the default branch at 5244e47. (1) pstack recheck: docs/upstream/cursor-pstack.md is pinned at cursor/plugins88d47514b8 (pstack 0.15.29), which contains 99743e9c15. The record names 99743e9c15 on lines 19, 23, 25, 92, 93, 98, 99, 102 and 111, and re-maps the principles that cursor/plugins#633 and #634 restated. (2) Listing budget: #6458 closed as completed on 2026-11-02, after the description pilot (PR #12021, sub-issue #11954) merged and posted its readings. Its measurement comment chose fraction 0.07, the value already at .claude/settings.json:61 (set by PR #6805), so no settings change is needed.
What the run says it did not do:
bash scripts/check-upstream-drift.sh: not run. This lane permits no such command, and the script needs gh API access to read upstream trees. The pin it checks is unchanged on main; recheck it in CI or by hand before closing.
Did not open the #6458 pilot 'Probe result' comment on #11954 directly; the closure and the chosen fraction come from #6458's own page
The Automation Lanes confirmation in the issue's Decisions (D68/Q63, GUIDE 121) is not a done-when item and was not checked; it needs a person
The work-resolve-issue lane stopped partway through this issue and needs a person.
Reason: security
Matched security word: attack. A match holds the stop whether or not the text names a risk, so read the word in context below.
Why, in the run's own words:
already-done: the default branch at 652a2c1 already holds the pstack recheck this issue asks for. docs/upstream/cursor-pstack.md pins cursor/plugins88d47514b82e7c44f00f2b2a72ff6dd12158038c (pstack 0.15.29), which contains 99743e9c15 (lines 10-27). The principle rows that cursor/plugins#633 and #634 changed (attack-the-premise and fix-root-causes, type-system-discipline, migrate-callers-then-delete-legacy-apis, make-operations-idempotent, test-behavior-not-implementation, swarm, poteto-mode) carry re-check stamps for that range. rg -c '99743e9c15' on the page already returns a count above 0. The listing-budget slice needs no change here: the issue's Decisions keep skillListingBudgetFraction at 0.07 until the description pilot ships and set the fleet value in #6458.
What the run says it did not do:
bash scripts/check-upstream-drift.sh was not run. This lane can run only the named wrappers and has no gh access for the script, so it is unconfirmed whether upstream HEAD has moved past the 88d47514b8 pin since then.
Listing-budget value: the issue gates it on the description pilot's readings and sets the fleet value in #6458. No edit was made here.
Tidy, review and verify were skipped because there is no diff.
Activity
github-actions commentedon Oct 16, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
I read this as two housekeeping items. The first is to re-pin the pstack upstream record at cursor/plugins 99743e9c15 and re-map the newer principles. It is done when
docs/upstream/cursor-pstack.mdmentions that commit andscripts/check-upstream-drift.shexits 0. The second is to set the fleet listing budget only after the description pilot's readings are posted.skillListingBudgetFractionstays 0.07 until then. The issue records its decisions and done-when items, so I have no open questions.The listing-budget item waits on #7582. I could not check whether #7571 or #7582 are still open, because they are outside the open-issues list I was given. Related: #6458 and #7052. I found no likely duplicates.
Automated triage, applied by the lanes App.
18 remaining items
github-actions commentedon Nov 2, 2026
github-actions commentedon Nov 2, 2026
melodic-automation-lanes commentedon Nov 2, 2026
The work-resolve-issue lane stopped on this issue (
already-done): the run found the issue's work already on the default branch at a commit it cites, so the issue closes.Its reason cites no pull request merged into the default branch, or commit on it, made after the issue opened whose commit message closes this issue, so it retries instead of closing.
It keeps
agent-ready, and work-unblock starts it again (retry 2 of 2).In the run's words:
What the run says it did not do:
Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41415827706
github-actions commentedon Nov 2, 2026
github-actions commentedon Nov 2, 2026
melodic-automation-lanes commentedon Nov 2, 2026
The work-resolve-issue lane stopped partway through this issue and needs a person.
Reason:
securityMatched security word:
attack. A match holds the stop whether or not the text names a risk, so read the word in context below.Why, in the run's own words:
What the run says it did not do:
Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41423904853
To retry, remove
needs-humanand addagent-readyagain.kyle-sexton commentedon Nov 2, 2026
This was generated by AI.
Closing as completed: done-when 2 and the pin are met; the drift-check half of done-when 1 is sliced to #12356.
Checked against origin/main (d54ab7a or later):
rg -c '99743e9c15' docs/upstream/cursor-pstack.mdreturns 9. The page now pinscursor/plugins@88d47514b8(pstack 0.15.29), which contains99743e9c15, and re-checks the rows work-items:triage: umbrella-fold routing misses the umbrella-side membership comment (item-side only, 3x this session) #633 and refactor(source-control): one shared babysit authorship/finding/approval classifier + golden fixtures (#534) #634 changed at that commit.bash scripts/check-upstream-drift.shexits 1. Upstream moved past the pin:cursor-pstack.mdshows 433 drift rows andmattpocock-skills.mdshows 20. chore(upstream): re-audit the cursor-pstack and mattpocock-skills pins so check-upstream-drift exits 0 #12356 carries the re-audit and the exit-0 check..claude/settings.jsonsetsskillListingBudgetFractionto 0.07, which equals that stated fraction. feat(context-budget): keep plugin skill descriptions visible when the skill listing overflows #6458 closed completed on that basis.attackinattack-the-premise, a pstack principle name. That is not a security finding. The lane's own reading agrees with this record (already done; drift check not run), soneeds-humanandneeds-speccome off with this close. Blockers perf(session-flow): run the description trim pilot and measure skill visibility #11954 and config-cascade: resolver and reader implement the config ADR (overlay, policy floors, root classification, --ref) #7938 are both closed.