Move the issue pipeline's pages to the ecosystem wiki
Reimagined pipeline: publish the rewrite's target design
Add the target design for the reimagined issue pipeline (four stages,
three model roles, a deterministic merge) as its own page, marked as not
installed. Link it from Home and the sidebar, and add a notice to Issue
pipeline, Running the issue pipeline and Pipeline roles that they describe
the installed version until cutover.
#425: name src/job/runner.ts as the role runner; registry.ts says which stages run a role
Bring the pipeline pages in line with the built role split (#425)
Pipeline-Roles: the roles table, the hand-offs and the seams follow
the stage-to-role table and the built PRs; deferred items stay marked.
Issue-Pipeline: the Design sections keep their decisions and reasons
and link to the role pages for the details.
Running-the-Issue-Pipeline: stage jobs that run roles, their printed
end, and a link to the orchestrator's roles.
Agent-Labels: each stop label names the role and stage that set it.
Rules now live in AGENTS.md: rewrite the practices digest and record agents-md-holds-the-rules
Pipeline roles: triage and the spec writer size issues in two implementer sessions (#413)
Pipeline-Agent: spec writer
Pipeline-Session: i413-spec-4@2026-10-17T21:04:56.395Z
Pipeline roles: roles-6-10-scope also defers back-to-spec and the spec-test re-run in verify
Pipeline roles: roles-6-10-scope, defer the final security review and re-check cost (Axlog, 2026-10-17)
Wiki: review-keeps-on-clean-rebase (#394)
Pipeline-Agent: spec writer
Pipeline-Roles, Implementor, Issue-Pipeline: specs and split parts name no files; wikiOnly hand-off (#391)
Pipeline-Agent: spec writer
Wiki: security-skip-unchanged (#387)
Records Axlog's decision to skip the security review when the head's
tree equals the tree that last passed, applies it to the planned final
security review, and replaces the finalizer's open question about the
first security review.
Pipeline-Agent: spec writer
Dropped changes saved as patches: Running the Issue Pipeline, Pipeline-Roles-Shared, Pipeline-Roles and Issue-Pipeline (#369)
Hand-made wiki updates for #369's spec, which predates #334: no stage after spec writes the wiki.
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.