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
Wiki: a claim adopts a stage job's push from checks and sends it back to review (#447)
Pipeline-Agent: spec writer
Pipeline-Session: i447-spec-4@2026-10-18T04:52:43.201Z
Issue pipeline: document the orchestrator's failing-claim stop (#430)
Pipeline-Agent: spec writer
Pipeline-Session: i430-spec-4@2026-10-17T22:21:52.728Z
Agent-Labels: the spec-files check reads the new interfaces' stubs, not a Files list (#408)
Pipeline-Agent: spec writer
Pipeline-Session: i408-spec-7@2026-10-17T17:59:43.305Z
Agent-Labels, Spec writer: the restart's spec-files check counts the spec head's files as present (#408)
Pipeline-Agent: spec writer
Pipeline-Session: i408-spec-4@2026-10-17T17:59:43.305Z
Wiki: review-keeps-on-clean-rebase (#394)
Pipeline-Agent: spec writer
unrelated-fixes-allowed: writers may fix and improve beyond the issue's scope (#405)
Wiki: the orchestrator schedules lifted issues (#381)
Pipeline-Agent: implementer
Wiki: the spec writer is held to the context limits, hands off and continues, and is a writer-budget role, in Issue-Pipeline, Running-the-Issue-Pipeline, Agent-Labels and the sandbox-ready-jobs decision (#335)
Pipeline-Agent: implementer
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
Issue pipeline: a restart's spec-files check leaves out wiki pages, which the code checkout never tracks (#334)
Pipeline-Agent: fixer round 1
Restarts resume at the stage that stopped; agent:stopped-spec-files for a spec writer's missing tests and stubs
File holds: a restart keeps the spec's files; an issue without them takes its body's Files line (#321)
Issue pipeline: budgets bound context only (budgets-bound-context); writers commit often; rate limit off by default
Issue pipeline: writers-only context limits and watchdog max, a context log, no cache reads in reportedTokens (#314)
- The watchdog's over-budget kill and the job's context watch (soft steer,
hard stop) hold writer sessions only: implementer, fixer, CI fixer and
conflict resolver. Other sessions record a null tokenBudget.
- #272's reader retry (<key>.retry, the read-in-parts line) is gone; an
older job.json's retry record still reads.
- job.json gains firstContext and turns; contextStop is {"context":N}.
- New: runs/<slug>/issue-N/context.jsonl, one line per ended session, its
fields, and a jq line for peak context per role and stage.
- reportedTokens counts input, output and cache writes, as the rate limit
does; both pools are still charged the role budgets up front.
(Axlog, 2026-10-16)
Name the owner Axlog across the wiki
Issue pipeline: the spec writer splits large issues, triage only suggests it (#267)
Pipeline-Agent: implementer
Issue pipeline: where an implementer's unpushed work goes on a stop (#283)
Pipeline-Agent: implementer
Wiki: the watchdog's budget rule, its context-size threshold and SIGTERM-then-stop order (#281)
Pipeline-Agent: implementer
Document the code and wiki flows (#217)
Pipeline-Agent: implementer
Issue pipeline: every writer stage hands off, up to maxContinuations (#269)
contextLimits.hard (175k) replaces the 150k rule in the writer prompts;
the fixer, CI fixer and conflict resolver get continuations like the
implementer, and a handoff past the cap stops as too-large, including a
conflict resolver's.
Pipeline-Agent: implementer
Issue pipeline: the orchestrator's watchdog (#235)
Documents the watchdog's dead-job and silent-session rules, their
thresholds (maxResumes, silentMinutes), its log actions and memory file,
the agent:stopped-job label, and the decision orchestrator-watchdog.
Pipeline-Agent: implementer
Issue pipeline: a failed acceptance goes to fix (#266)
Record that a failed acceptance becomes a blocking acceptance-lens
finding and sends the issue to fix, stopping only when the fix rounds run
out or the fixer disputes it, and the bounded-fix-loop exception for that
dispute.
Pipeline-Agent: implementer
Push retry before push-rejected; second failure stops as error (#263)
Pipeline-Agent: implementer
Agent-Labels: labels.test.mjs pins label names and stop order (#256)
Pipeline-Agent: implementer
Named and pinned runs leave a stopped issue alone unless takeStopped (#251)
Pipeline-Agent: implementer
Document the wiki's agent/issue-<n> branch (#213)
Pipeline-Agent: implementer
Document that named runs wait for answers and stale worktrees reset to the base (#243)
Pipeline-Agent: implementer
Document the rebase token pool (#201)
Pipeline-Agent: implementer
The ops CLI's labels, stops and claims live in src/*.ts modules (#166)
Point the pages at src/labels.ts, src/stops.ts and src/claims.ts, and
record the pipeline's scoped Biome overrides under best-practice-over-lint.
Pipeline-Agent: implementer