[poteto]

Replaces #684 by @rudycelekli. This is the same commit, rebased onto current main. The author stays Rudy Celekli.

The fork branch could not take the rebase. The rebase brings in main's newer .github/workflows/validate-plugins.yml, and GitHub refuses that workflow update on a fork from an app without the workflows permission. A fork PR's CI also waits for maintainer approval, so this branch on cursor/plugins lets CI run.

Problem

After a stacker closes an obsolete PR and creates a replacement from the same branch, orch frontier set rejects that branch because its all-state forge query returns both PRs. The suggested recovery, closing stale PRs, cannot clear the error because closed rows are still included.

Change

Prefer the sole OPEN PR when selecting a branch anchor. Keep closed and merged anchors when no active PR exists, and continue to reject multiple active PRs. GitHub and Origin use the same policy. The Claude Code harness copy is regenerated.

Verification on the rebased tree

• node scripts/validate-plugins.mjs: all plugins validated.
• node scripts/generate-pstack-harness-trees.mjs --check: up to date.
• node scripts/check-pstack-docs.mjs: 0 problems.
• bun test in pstack/skills/poteto-mode/scripts: 72 pass, 0 fail. bun run typecheck (strict): exit 0.
• node --test pstack/skills/*/scripts/test/*.test.mjs: 58 pass, 0 fail, 92 skipped (no TLC on this machine).

No pstack version change.

  

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 260d4dc. Configure here.}

[cursor]

Historical fallback rejects merged replacements

Medium Severity · Logic Bug

When a branch has no OPEN pull request, branchPullRequest falls back to every historical row and still errors if more than one remains. After the replacement this change accepts later merges, orch frontier set fails walking that branch, and closing stale PRs cannot clear it.

 

^{Reviewed by Cursor Bugbot for commit 260d4dc. Configure here.}