diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/superpowers/plans/2026-07-09-root-completion-follows-arbitration.md | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/docs/superpowers/plans/2026-07-09-root-completion-follows-arbitration.md b/docs/superpowers/plans/2026-07-09-root-completion-follows-arbitration.md index 04c43a7..1cdefb6 100644 --- a/docs/superpowers/plans/2026-07-09-root-completion-follows-arbitration.md +++ b/docs/superpowers/plans/2026-07-09-root-completion-follows-arbitration.md @@ -683,17 +683,15 @@ Run: `go build ./...` then `go test ./...` (the entire repo). Both must pass — Also run `gofmt -l internal/scheduler/story_orchestrator.go internal/scheduler/story_orchestrator_test.go` before committing, and `gofmt -w` any file it flags that wasn't already gofmt-dirty before your changes (check with `git show HEAD:<path> | gofmt -l -` if unsure). -- [ ] **Step 14: Commit and push** +- [ ] **Step 14: Commit (do NOT attempt to push — see note below)** Run these exact commands, in order, confirming each succeeds: ```bash -git remote -v git add -A git commit -m "refactor(scheduler): promote story root to COMPLETED only after arbitration approves it, not eagerly on READY" -git push origin main -git rev-parse HEAD -git ls-remote origin main +git status +git log --oneline -1 ``` -Do this commit+push step immediately after Step 11 (all edits done) if you are running under time/turn pressure — do not wait until Steps 12/13's verification is fully done to make your first commit attempt; verify locally first if you can, but a working local commit that's pushed is more valuable than a perfect but unpushed one. If `git ls-remote origin main`'s SHA doesn't match `git rev-parse HEAD`, the push did not really land — this container may not have this repository mounted at `origin`; if so, note that in your summary rather than treating it as your own error (a prior task in this same repo discovered that pushes are handled externally by claudomator's ContainerRunner after your run completes successfully — see this repo's own CLAUDE.md, "After a successful run, new commits are pushed from the workspace"). Run `git status` and `git log --oneline -1` and paste that output regardless. +**Do not run `git push`.** This repo's own bare git remote is not mounted inside this container — a `git push origin main` here will either fail outright or silently no-op; do not treat that as an error and do not spend turns retrying it. Per this repo's own CLAUDE.md ("After a successful run, new commits are pushed from the workspace"), claudomator's ContainerRunner pushes your commits externally once this run finishes successfully with a clean working tree. Your only job is to commit locally and end your turn with `git status` showing a clean tree — do this as soon as all edits (Steps 1-11) are done, before spending time on Steps 12/13's verification, so your work is safe even if you run low on turns during verification. Paste the `git status`/`git log` output in your summary regardless. |