Research stage: platform REST merge support + idempotent shipping workflow #211

New issue

david · 2026-08-16T21:52:03Z

david commented

2026-08-16 21:52:03 +00:00

Add the deterministic research shipping workflow (git + platform REST, mirroring runMrStage) and the REST merge support it needs:

REST merge support — add a merge method to the platform REST clients (Forgejo, GitLab, GitHub) behind the existing seams; unit tests per platform.
Shipping workflow (runResearchShipping.ts) — deterministic: branch research/issue-{no}/{issue-title-as-slug} → commit docs/reference/ → push → open PR (targeting the repo's default branch) → merge (squash by default) → return to the default branch.
Idempotent on resume — skip when the research PR is already merged; reference an existing open PR instead of duplicating.
Hard-fail policy — ALL shipping failures (branch/commit/push/PR/merge/auth/network) abort the run with error.json; no non-fatal merge-blocked path. research.enabled: false is the escape hatch for protected repos.
The docs PR references the existing issue but must never close it.

Unit tests use a fake git runner + fake REST client covering every step and every failure path. References: ADR-014, DESIGN.md §4 (Stage R shipping), AGENTS.md commit model footnote.

Add the deterministic research **shipping workflow** (git + platform REST, mirroring runMrStage) and the REST merge support it needs: - **REST merge support** — add a `merge` method to the platform REST clients (Forgejo, GitLab, GitHub) behind the existing seams; unit tests per platform. - **Shipping workflow** (`runResearchShipping.ts`) — deterministic: branch `research/issue-{no}/{issue-title-as-slug}` → commit `docs/reference/` → push → open PR (targeting the repo's default branch) → merge (squash by default) → return to the default branch. - **Idempotent on resume** — skip when the research PR is already merged; reference an existing open PR instead of duplicating. - **Hard-fail policy** — ALL shipping failures (branch/commit/push/PR/merge/auth/network) abort the run with `error.json`; no non-fatal merge-blocked path. `research.enabled: false` is the escape hatch for protected repos. - The docs PR references the existing issue but must **never close it**. Unit tests use a fake git runner + fake REST client covering every step and every failure path. References: ADR-014, DESIGN.md §4 (Stage R shipping), AGENTS.md commit model footnote.

david added the

pi-loop

label

2026-08-16 21:52:32 +00:00

Sign in to join this conversation.