Repository navigation
feat(meta-mode): harden portable workflow tooling - #29
Merged
Merged
Conversation
3metaJun
changed the base branch from
main
to
feat/meta-mode-playbook-validation
October 5, 2026 05:38
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…rify files Checkpoints now live under the common Git directory keyed per worktree, so removing a linked worktree no longer deletes them and ids cannot collide. read picks the newest by publishedAt, hashes the referenced files and reports changed or missing ones, and only begin requires a Git identity. Playbooks and the guide call the tool through <meta-mode-tools> instead of a cwd-relative path. The test resolves the script from import.meta.url so it runs under bun test. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A failing git status now yields an explicit unknown dirty state classified as hold-unknown instead of clean. The transcript scan collapses runs of backslashes so JSONL-escaped Windows paths match. The test is replaced by an end-to-end run over a temporary repository, worktree, and fake transcripts. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
… merges orch reads a legacy ledger.tsv header as unbound rows (never verified) and migrates it on the next write. The orchestrate playbook now states the real (pr, head sha) key. guardedMergeArgs validates head as a full object id. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
3metaJun
changed the base branch from
feat/meta-mode-playbook-validation
to
main
October 5, 2026 17:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
mstack's long-running workflow support still had portability and durability gaps. Worktree cleanup depended on Unix shell tools, resume state lacked a durable portable checkpoint, shipping verdicts were not structurally tied to patch identity, and several pstack safety mechanisms were missing or implicit.
Scope
Verification
npm testwith 245 passing tests.node --test tools/meta-mode/resume.test.mjs tools/meta-mode/pr-safety.test.mjswith 8 passing tests.node scripts/validate.mjs.node scripts/skill-baseline.mjs --check.node tools/meta-mode/check-playbooks.mjs ..npm pack --dry-run --json.Known limitation: Bun-specific orch tests were not runnable in this environment because Bun is unavailable. The integrated Node/npm suite passed, and the limitation is recorded in the implementation report.
Agent: GPT-5 via pi