#422: Finalizer page: the outputs of a merge job's rebase and retest
#422: Finalizer and Issue-Pipeline pages: the finalizer rebases and retests before merging Settled by the operating session in automatic mode.
#416: Finalizer test plan row for merge as the finalizer role Pipeline-Agent: spec writer Pipeline-Session: i416-spec-10@2026-10-17T21:53:22.091Z
#416: Finalizer and Issue-Pipeline pages: merge runs as the finalizer role Pipeline-Agent: spec writer Pipeline-Session: i416-spec-7@2026-10-17T21:53:22.091Z
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
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
Wiki: the orchestrator closes split parents each tick (#378) Document the split-parent pass, its log and escalation lines, the stricter close-parent test and its new order, and record the decision orchestrator-closes-parents. Parents leave the orchestrator's open questions; cleanup stays open. Pipeline-Agent: implementer
Wiki: merge-order amended, a merge waits only for issues at accept, security or merge (#358) 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: budgets bound context only (budgets-bound-context); writers commit often; rate limit off by default
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.