Clarify postmerge wiki integration guards and regression coverage Pipeline-Session: reviewer-1@2026-10-19T23:38:29.401Z
Fix postmerge wiki integration head comparison Pipeline-Session: implementor-1@2026-10-19T20:42:19.337Z
Persist sanitized verified runtime policy on each model launch Pipeline-Session: implementor-1@2026-10-20T14:55:57.933Z
Classify stale code rebase stops before sync cleanup Pipeline-Session: reviewer-1@2026-10-20T15:07:43.234Z
Clarify code versus wiki continuation and retained conflict recovery Pipeline-Session: implementor-1@2026-10-20T14:51:22.224Z
Harden Git review submodule isolation and preserve predicate evidence Pipeline-Session: reviewer-1@2026-10-19T22:22:23.536Z
Document Git reviewer authority, paging and supervisor coverage checks Pipeline-Session: implementor-1@2026-10-19T21:53:06.542Z
Clarify recovery manifests are created only for saved patches Pipeline-Session: reviewer-1@2026-10-19T22:30:07.227Z
Direct hardening writers to targeted tests and scoped recovery Pipeline-Session: implementor-1@2026-10-19T20:42:17.587Z
Test both closed-issue recovery authorities against durable merge evidence Pipeline-Session: reviewer-1@2026-10-20T14:30:28.794Z
Recover auto-closed issues with confirmed incomplete Merge authority Pipeline-Session: implementor-1@2026-10-19T20:42:20.918Z
Document bounded post-merge confirmation and evidence-preserving recovery Pipeline-Session: reviewer-1@2026-10-19T22:05:23.590Z
Describe the separate development and review/merge accounts
Restore pipeline rules that still apply to the current source
Document only the caller-assigned pipeline and prune obsolete history
Split canonical ecosystem pipeline wiki from project-buddy
Preserve accepted project-buddy wiki provenance in ecosystem
Initial Home page
Align target pipeline prompts with explicit-target merge verification
Publish wiki-owned prompts for hardening, integration and postmerge security
Security review after the smart merge; caller assigns issue and branch; prompts from the wiki
Make the final post-hardening review security only
Target Reviewer hardening and final smart integration
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.
Spec draft and wiki: list names Projects and Chats (#471) Pipeline-Agent: spec writer Pipeline-Session: i471-spec-4@2026-10-18T12:13:54.982Z
#425: Agent-Labels: a failed step a role doesn't handle itself posts no stop label
#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.
docs: condense wiki decisions and repair their index
#474: tests and their helpers live in test/ (test-code-in-test); paths updated