Skip to content

chore(upstream): re-audit the cursor-pstack and mattpocock-skills pins so check-upstream-drift exits 0 #12356

New issue
New issue
Closed
Task
#12751
Closed
chore(upstream): re-audit the cursor-pstack and mattpocock-skills pins so check-upstream-drift exits 0#12356
Task
#12751
Assignees
kyle-sexton
Labels
host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.priority: mediumReal value, no hard deadline; normal backlog flow.status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

Description

@kyle-sexton
kyle-sexton
opened on Nov 2, 2026

This was generated by AI.

Parent

Sliced from #7588 (done-when 1, second half). Refs #7555.

Problem

bash scripts/check-upstream-drift.sh exits 1 on main (d54ab7a or later). The pstack record pins cursor/plugins@88d47514b8 (pstack 0.15.29), which contains the 99743e9c15 #7588 asked for. But upstream has moved past that pin, and the script reports 2 of 4 pages drifting:

  • docs/upstream/cursor-pstack.md: 433 rows, for example pstack/skills/reflect/SKILL.md, pstack/skills/arena/SKILL.md and pstack/skills/swarm/SKILL.md (M).
  • docs/upstream/mattpocock-skills.md: 20 rows, including new units under skills/in-progress/chief-of-staff/ and skills/in-progress/software-factory/.

Done when

  • Each drifting row in both pages is re-audited per docs/contracts/upstream-drift/README.md, "Pinned git upstreams", and the pins move to the audited commits.
  • bash scripts/check-upstream-drift.sh exits 0 on the PR head.

Out of scope

Activity

  1. kyle-sexton
    added
    host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.
    on Nov 2, 2026
  2. kyle-sexton
    added a parent issue on Nov 2, 2026
  3. github-actions
    added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 2, 2026

  4. github-actions commented on Nov 2, 2026

    @github-actions
    github-actionsBot
    on Nov 2, 2026 – with GitHub Actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Large
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: none

    Understood: upstream has moved past the pinned cursor-pstack and mattpocock-skills commits, so scripts/check-upstream-drift.sh exits 1. The work is to re-audit the drifting rows (433 and 20) per the upstream-drift contract, move both pins, and get the script to exit 0. The scope is clear, but at about 450 rows it likely needs splitting into smaller changes. No likely duplicates found among the open issues.

    Automated triage, applied by the lanes App.

  5. github-actions
    added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 2, 2026
  6. github-actions
    added the
    Task
    issue type on Nov 2, 2026
  7. melodic-automation-lanes
    added
    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.
    on Nov 2, 2026
  8. melodic-automation-lanes
    set
    Work status
    to
    ready
    on Nov 2, 2026
  9. melodic-automation-lanes
    added
    status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.
    and removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    on Nov 2, 2026

  10. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    melodic-automation-lanesBot
    on Nov 2, 2026
    Contributor

    Not admitted to the issue lane: it carries host-run; Size large: the split into sub-issues at intake is pending (owner Q93). Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).

  11. melodic-automation-lanes commented on Nov 2, 2026

    @melodic-automation-lanes
    melodic-automation-lanesBot
    on Nov 2, 2026
    Contributor

    The latest triage verdict holds nothing: admission moved the issue to status: confirmed; its comment says why.

  12. melodic-automation-lanes
    changed
    Work status
    to
    confirmed
    on Nov 2, 2026
  13. kyle-sexton
    self-assigned this
    on Nov 3, 2026

  14. kyle-sexton commented on Nov 3, 2026

    @kyle-sexton
    kyle-sexton
    on Nov 3, 2026
    MemberAuthor
    No description provided.
  15. kyle-sexton
    added a commit that references this issue on Nov 3, 2026

    fix(upstream): correct citations and stamps, and catch backticks in _…

    5164590
  16. kyle-sexton
    closed this as completedin #12751on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

host-runNeeds an unattended run on a host; the host runner takes it, not a person or the issue lane.priority: mediumReal value, no hard deadline; normal backlog flow.status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

Type

Task

Fields

Work status

confirmed

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions