Skip to content

Sync upstream pstack 0.15.36: re-port the agentic Orchestrate playbook - #699

Merged
creedants merged 8 commits into
mainfrom
landing/e61
Oct 28, 2026
Merged

creedants merged 8 commits into
mainfrom
landing/e61

Conversation

@creedants

Copy link
Copy Markdown
Owner

Syncs upstream pstack to 0.15.36 and re-ports the Orchestrate playbook to upstream's new agentic flow. Upstream rewrote Orchestrate so the coordinator supervises workers directly, keeps its program state in notes.md, and calls no scripts. It deleted the orch CLI and its store.

What changed

  • vendor/pstack/ matches cursor/plugins' pstack/ tree at c742dd61, and upstream.json and the README badge name 0.15.36.
  • t3/overrides/poteto-mode/playbooks/orchestrate.md is re-ported from the new upstream file. Program state is notes.md only, with no units.tsv, ledger.tsv, frontier.json, decisions.tsv, or status.md. The reply reports what landed, each PR's live state and verdict, what was dropped, and the decisions waiting on the user.
  • The port keeps upstream's rules with T3 mechanisms: a worker is reused only when the next step needs its retained state, otherwise a fresh child runs. Stalled or looping workers are stopped or replaced, judged by pushes and PR activity, and a late result is checked against the PR's current state. No scripts run except roles.py and land.py slot --. Verification uses control skills if installed, otherwise T3 preview tools for UI or the terminal for CLI.
  • t3/added/poteto-mode/references/orchestrate-t3.md is deleted. Its T3 rules live in the playbook, and no shipped file links it.
  • tests/test_build.py moves the exec-bit row from the deleted orch.ts to bootstrap.ts. tests/pstack_t3/test_verify_docs.py pins the new reply facts and rejects the five removed store files.

Verification

  • A fresh copy of upstream at c742dd61 is byte-identical to vendor/pstack/, checked by the worker and again by the reviewer.
  • python3 scripts/build.py leaves no diff and python3 scripts/check.py prints ok at the final head. tests.test_build and tests.test_pstack_t3, the 163 tests/pstack_t3 tests, and the 207 check tests pass there. The full suite passed (3958 tests) before the last one-line wording edit.
  • The reviewer showed each changed test row fails alone when its pinned behavior is removed.

Known limits

  • t3/added/pstack-runtime/gate-review.md still says an Orchestrate ledger.tsv row does not qualify as a verdict. That stays true and harmless with no ledger.
  • The override sits close under the size allowance, so the next upstream growth to this playbook needs a split.

Two review rounds. The first sent the port back for keeping upstream's removed store and dropping three supervision rules. The second round's one-line wording edit was applied from the reviewer's text and verified.

Coordinated by claudeAgent/claude-opus-5-5. Written by opencode-go/muse-spark-1.3-contributor. Reviewed by codex/gpt-6.1-sol.

Takes vendor/pstack to cursor/plugins c742dd61. Upstream rewrites
the orchestrate playbook around agentic coordination and deletes
the scripts/orch bookkeeping CLI.
Rewrites the override from the new upstream Topology and
Supervision with T3 substitutions and runtime links, deletes the
orchestrate-t3 reference with its rules folded inline, and
retargets the test_build CASES row to bootstrap.ts.
State is notes.md under local-state. Reuse goes through
t3_thread_send per Fresh children by default. Supervision
restores stop-or-replace and late-result reconciliation.
Spawn keeps the no-scripts rule with roles.py and land.py
slot exceptions. Trims unpinned wording to hold the size
allowance.
Pins what landed, live state and verdict with link, dropped
work and why, decisions waiting, the Visual reports link,
and the reply-text carryover. Fails when the old store
vocabulary returns to the reply.
The guide carries the reworded Orchestrate paragraph, not a version bump.
Applies the review's edits from reports/D56-review-2.md at cf11dc7298edcdba5fe4c3813beec61de5a7c248.
@creedants
creedants merged commit a5b8faf into main Oct 28, 2026
15 checks passed
@creedants
creedants deleted the landing/e61 branch October 28, 2026 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant