Repository navigation
marketplace: pstack recheck and listing budget #7588
Description
Parent
Refs #7555. Source: PLAN Phase 20, topic poteto-review. Thread: This marketplace (housekeeping).
Depends on
- config-cascade: settings resolution and convention home #7571 Settings resolution and convention home (sequence)
- skill-quality: skill authoring, quality and catalog #7582 Skill authoring, quality and catalog (the listing-budget slice waits on the description
pilot)
Outcome
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.
Decisions
- One pstack recheck PR at 99743e9c15 (0.15.25 plus pstack: restate four overspecified principles as reasoning, not rules cursor/plugins#633, refactor(source-control): one shared babysit authorship/finding/approval classifier + golden fixtures (#534) #634) during delivery (D0,
Q557). Origin: ours. skillListingBudgetFractionstays 0.07 until the description pilot ships; fleet value set in feat(context-budget): keep plugin skill descriptions visible when the skill listing overflows #6458
(Q187).- 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.mdis at least 1 (0 on main) and
bash scripts/check-upstream-drift.shexits 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).
Related
- feat(context-budget): keep plugin skill descriptions visible when the skill listing overflows #6458 keep plugin skill descriptions visible on listing overflow (sub-issue of this thread); the fleet listing-budget value is set there.
- docs: reword nine pre-existing passages that track upstream pstack and mattpocock text #7052 reword passages tracking upstream pstack text (sub-issue of this thread).
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.
kyle-sexton commentedon Oct 24, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 24, 2026
Not admitted to the issue lane yet: blocker #7582 is not closed by a listed human or a merge.