Skip to content

Spec 081: Executor docs, tests, and rename cleanup#70

Merged
mrmaxsteel merged 23 commits intomainfrom
spec/081-executor-docs-tests
Mar 11, 2026
Merged

Spec 081: Executor docs, tests, and rename cleanup#70
mrmaxsteel merged 23 commits intomainfrom
spec/081-executor-docs-tests

Conversation

@mrmaxsteel
Copy link
Owner

Summary

  • Rename GitExecutorMindspecExecutor (including file rename git.gomindspec_executor.go)
  • Rename internal/specinit/internal/spec/ to match domain conventions
  • Purge legacy gitops terminology from codebase and docs
  • Architecture documentation overhaul for the two-layer design (workflow enforcement + execution engine)
  • LLM test scenario audit (18 scenarios reviewed, findings in HISTORY.md)
  • Two new LLM test scenarios: StopAfterComplete and StopDoesNotBlockApproveImpl
  • Harden phase-transition stop behavior in instruct templates and CLI output
  • Remove dead --no-next flag

Test plan

  • make build passes
  • go vet ./... clean
  • TestLLM_StopAfterComplete passes (Opus)
  • TestLLM_StopDoesNotBlockApproveImpl passes (Opus)
  • TestLLM_SingleBead passes (no regression)

🤖 Generated with Claude Code

mrmaxsteel and others added 23 commits March 10, 2026 20:59
…th package spec, update all import paths and comments
Bug mindspec-ogzs: WorktreeRemove now always passes --force to
bd worktree remove, since mindspec merges bead work into the spec
branch before removal (unpushed-commits check is a false positive).

Bug mindspec-7i8q: complete.Run now resolves the spec from the
bead's parent epic when multiple specs are active, eliminating
the need for --spec when the bead ID is provided.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
CompleteBead now checks that the bead branch is an ancestor of the
spec branch before proceeding with worktree removal and branch
deletion. If the merge failed, cleanup is aborted to prevent data loss.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…GENTS.md architecture section with two-layer model (workflow layer + execution engine), update all execution/workflow domain docs to reference MindspecExecutor and internal/spec/, add plan quality responsibility section to workflow architecture
Reposition MindSpec as a planning & governance layer upstream of agent
orchestrators. Add Architecture: Two Layers section explaining the
separation between planning (specs, decomposition, quality gates) and
execution (bead dispatch, merge topology, finalization). Reference
arXiv:2512.08296 on task decomposition quality.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Beads isn't just a state store — it's the contract between the two
layers. Each bead is a self-contained work packet (requirements, context,
dependencies, acceptance criteria) that a fresh agent can pick up without
session history. This is what makes pluggable orchestration possible.

Updated: README.md, AGENTS.md, workflow/architecture.md,
execution/architecture.md.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Drop "Two Layers" since beads as a third subsection made it misleading.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…dings in HISTORY.md, verify no outdated assumptions or broken expectations, SingleBead smoke test passes
The implement.md template says "STOP" after mindspec complete, but
SpecToIdle expects the agent to continue to approve impl. This is
the likely root cause of Haiku's consistent SpecToIdle failures —
Haiku interprets "STOP" literally while Opus reasons past it.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…StopDoesNotBlockApproveImpl), fix instruct templates (remove stale auto-claims text), strengthen CLI STOP message, remove dead --no-next flag, update HISTORY.md
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@mrmaxsteel mrmaxsteel merged commit 9d9505a into main Mar 11, 2026
6 checks passed
@mrmaxsteel mrmaxsteel deleted the spec/081-executor-docs-tests branch March 11, 2026 06:30
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