Implement the governed Git change-set workflow and repository fixture

[JohnStrunk]

Plan ID

EM-07

Purpose

Exercise the approved ears-manager behavior through the governed single-player Git workflow.

Scope

• Create change-set branches using the documented naming and base-commit rules.
• Stage only registered specification paths, manifests, project configuration, and manager-owned projection entries.
• Prepare deterministic commits and pull-request summaries from compare and impact.
• Reject direct specification edits, unregistered paths, forbidden branches, force pushes, and default-branch pushes.
• Implement the local bare-repository fixture covering initialization, proposal, refresh, merge, and registration evidence.

Dependencies

Depends on EM-05 and EM-06. The Git contract in #34 is complete.

Acceptance criteria

• The fixture demonstrates a complete initialize, propose, validate, branch, commit, refresh, and merge flow.
• Every failure leaves the repository unchanged or provides a deterministic retry path.
• Only explicitly owned paths are staged.
• Approved change-set manifests are immutable.
• The fixture proves registration is idempotent by change-set and merge commit.

Out of scope

WMS lifecycle transitions and Job Site execution remain outside this issue.

[fullsend-ai-triage]

This issue (EM-07) declares dependencies on EM-05 and EM-06, which correspond to issues #112 (change-set comparison and deterministic impact analysis) and #113 (project/artifact-registry initialization). Both are still open, so implementation work here cannot meaningfully start until they land -- the governed Git workflow relies on compare/impact output from EM-05 and on the project bootstrap and registration primitives from EM-06.

The other referenced dependency, the single-player Git contract in #34, is already closed, so it is not a blocker.

No open pull request currently references or closes #112, #113, or this issue, so this is a pure prerequisite situation rather than work already in flight. The existing blocked label on this issue is consistent with this finding.

Once #112 and #113 merge, the scope and acceptance criteria described here are clear enough to proceed directly to implementation without further clarification.

Blocked by:

• Implement change-set comparison and deterministic impact analysis #112
• Initialize .protobot projects and the artifact registry #113

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 6:03 PM UTC · Completed 6:07 PM UTC

Commit: 98c117c · View workflow run →

Runtime: claude · Model: sonnet → claude-sonnet-5 · Effort: high · Cost: $0.38