Skip to content

marketplace: pstack recheck and listing budget #7588

Closed
4 of 4 issues completed
Closed

Description

@kyle-sexton

Parent

Refs #7555. Source: PLAN Phase 20, topic poteto-review. Thread: This marketplace (housekeeping).

Depends on

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

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).

Related

Activity

  1. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 16, 2026
  2. added theissue type on Oct 16, 2026
  3. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    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.

    Automated triage, applied by the lanes App.

  4. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 24, 2026
  5. 18 remaining items

  6. github-actions commented on Nov 2, 2026

    @github-actions
    Contributor
    No description provided.
  7. github-actions commented on Nov 2, 2026

    @github-actions
    Contributor
    No description provided.
  8. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    Contributor

    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

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41415827706

  9. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 2, 2026
  10. github-actions commented on Nov 2, 2026

    @github-actions
    Contributor
    No description provided.
  11. github-actions commented on Nov 2, 2026

    @github-actions
    Contributor
    No description provided.
  12. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 2, 2026
  13. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    Contributor

    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.

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41423904853

    To retry, remove needs-human and add agent-ready again.

  14. kyle-sexton commented on Nov 2, 2026

    @kyle-sexton
    MemberAuthor

    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):

  15. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    needs-specNeeds a Brief or plan before anyone can build it.
    on Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: mediumReal value, no hard deadline; normal backlog flow.status: readyTriaged, unblocked, and fully specified; eligible to pick up.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    Work status

    needs-spec

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions