Move the issue pipeline's pages to the ecosystem wiki
#424: Implementor tests table names the one-job tests; Shared page: fix → checks is built, and a rate limit puts counts back to the last move
Issue pipeline #459: issue.md test, spec draft and wiki: usage comments never answer and stay out of issue.md
Also puts the wiki submodule pointer back at integration's commit; the
previous spec commit moved it through git add -A.
Pipeline-Agent: spec writer
Pipeline-Session: i459-spec-3@2026-10-18T09:00:47.843Z
Issue pipeline #457: a saved end may name an after op; a stop after the end's save saves nothing more
Pipeline-Agent: spec writer
Pipeline-Session: i457-spec-4@2026-10-18T08:30:02.882Z
Wiki: the runner owns a session's transient error, and puts back the counts a rate-limited run took (#446)
Pipeline-Agent: spec writer
Pipeline-Session: i446-spec-4@2026-10-18T04:34:35.126Z
Reviewer: the machine and its review entry, and the sessions effect (#421)
Pipeline-Agent: spec writer
Pipeline-Session: i421-spec-7@2026-10-17T22:57:37.557Z
Spec writer: checks in the session, looser coverage, and zod schema changes in a spec (#436)
Wiki: review-keeps-on-clean-rebase (#394)
Pipeline-Agent: spec writer
Token-Spend: trace a commit to its spend from GitHub alone (session records, Pipeline-Session trailer, pushes and jobs logs)
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.
Token spend: every place development work spends tokens, its records, and how to trace a commit to its spend
New page Token-Spend: the pipeline's sessions with their agents and model
keys, the escalation agent and lanes, the tooling that spends nothing, the
records each writes (local or on GitHub, tokens or cost), the steps from a
commit to its sessions and cost, the #381 / PR #384 example, and the gaps
not yet recorded. The usage report moves there from Running the issue
pipeline, which links to it, as do Home and the sidebar.
Spec writer and Shared: a lifted stop clears the role's attempts too, keeping only the start heads (#392)
Issue pipeline: sessions' env goes back to hiding only the token variables; the job test kit drops an inherited commit scope instead (#334)
Hiding an inherited ISSUE_PIPELINE_COMMIT_SCOPE in agentEnvOf was a runtime change neither the issue nor the spec asks for. The job tests' env leaves out the scope of a pipeline session the suite may run inside, so the reader test stays hermetic.
Pipeline-Agent: fixer round 1
Pipeline-Roles-Shared: no session inherits the job's own commit scope (#334)
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.
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
Pipeline roles: start-pr given a body sets the found PR's body (#332)
Pipeline-Agent: implementer
Issue pipeline: implement, fix and checks keep wiki write as a bridge until the spec writer commits the spec's wiki updates (#300 part 5d removes 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
Triage runs as its own role (#304): lifecycle, locate and tests as built; the runner's after op, role context, step recovery and keyed comments; role stages restart without --resume
Pipeline-Agent: implementer
Restarts resume at the stage that stopped; agent:stopped-spec-files for a spec writer's missing tests and stubs
Usage log and report.mjs usage built (#302): the usage op, name grammar, nearest-rank percentiles, --since on records; a Usage report section
Pipeline-Agent: implementer
Issue pipeline: budgets bound context only (budgets-bound-context); writers commit often; rate limit off by default
Role runner built: Test interfaces statuses, job.json steps and the --resume refusal (#301)
Pipeline-Agent: fixer round 1
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.