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
Shrunk. The Cursor pstack 0.15.29 sync (#234) refreshes the "Incorporate a change" steps in UPSTREAM.md from its own run: the per-commit decision table, how to handle files that need review, the verifier registry's skills list, recipe updates, and --wide. This issue no longer waits on #105.
A repository-local sync skill stays unscheduled until a contributor's sync goes wrong because the written steps were not enough.
Original request
Goal
Turn the "Incorporate a change" section of UPSTREAM.md into a repository-local skill that any agent follows to sync Cursor pstack, in Claude Code or Codex, as a maintainer or a contributor. It sits beside verify-open-pstack.
Why the change from Factory (2026-10-12)
The original body asked for a runbook that a Factory planner and builder follow. No Factory branch has merged here since PR #111 on 2026-10-04, and the 0.15.17 sync came from a contributor's fork (#143, PR #145). Contributor-facing tooling should not depend on Factory.
The shrunk scope shipped: #240 rewrote UPSTREAM.md's "Incorporate a change" steps from the 0.15.29 sync's own run. A repository-local sync skill isn't planned. Reopen this if a sync goes wrong because the written steps were not enough.
Activity
[-]Write a factory-runnable upstream sync runbook[/-][+]Write an agent-runnable upstream sync skill[/+]ericlitman commentedon Oct 21, 2026
The shrunk scope shipped: #240 rewrote
UPSTREAM.md's "Incorporate a change" steps from the 0.15.29 sync's own run. A repository-local sync skill isn't planned. Reopen this if a sync goes wrong because the written steps were not enough.chore: record the Cursor pstack 0.15.29 sync and release 1.16.0 (eric…