sync-only-at-merge: a cleared review or fix round goes straight to checks; sync runs after implementation only when merge asks (#340)
Pipeline-Agent: implementer
Pipeline roles: the spec writer on the runner is built, and the wiki bridge is gone (#334)
Recovered from implement round 3 (session i334-implement-6), whose wiki edits
were finished and staged but never committed: pipeline_commit refused them with
"this session has no commit scope", because the job's pre-#338 runner set the
scope in the old shape. This commit replays that session's python edit calls,
in order, onto the wiki base the job used, 72af2b3.
Pages: Pipeline-Roles-Spec-Writer, Pipeline-Roles-Triage, Pipeline-Roles-Shared,
Pipeline-Roles-Implementor, Pipeline-Roles, Issue-Pipeline,
Running-the-Issue-Pipeline and Decisions-Code-and-tooling.
stacked-branches: hold a waiting issue stacked-on-behind:#P while P's branch lacks another merged prerequisite's merge commit (#328)
Pipeline-Agent: implementer
Docs: stage jobs hold repo/ and docs/ side by side, every stage reads the wiki, and pipeline_commit needs write access (#338)
Pipeline-Agent: implementer
sync-at-edges: a checks job back from a CI wait doesn't sync; only returns to finalize count toward maxSyncs; a start-sync cannot-fix retries at the next job's start, as conflicts-never-stop has it
sync-at-edges: a branch syncs only at the start of each implementor entry, before any edit, and in finalize; no sync while an entry runs, between continuations, or after a review clears
Issue pipeline: pipeline_commit, the job's push, the pre-commit hook, wiki access and no session token are built (#303)
sandbox-ready-jobs changes: no session gets a token, only jobs hold one, and
tokenEnv only names a variable hidden from sessions. The wiki-access table
lives in src/job/roles.ts rather than in each role's module.
Pipeline-Agent: implementer
Issue pipeline: budgets bound context only (budgets-bound-context); writers commit often; rate limit off by default
Pipeline roles: name the self-build ticket, #300
Pipeline roles: credit the owner's decisions to Axlog
Add the Pipeline roles specs: the design for splitting the issue pipeline into roles
New pages: Pipeline-Roles (index), and one per role: Triage, Spec writer,
Implementor, Reviewer, Finalizer, Orchestrator, plus Shared (pipeline_commit,
role machines, restarts, the usage log and wiki provisioning). Linked from
Issue-Pipeline and the sidebar.