Plan safe migrate-once backend CI acceleration

[Abiorh001]

PR Trust Bundle

Chunk

WS-CI-001-02 — Safe Routing, Cache, and Timing Refinement

Merge intent: .agent-loop/merge-intents/WS-CI-001-02.json

Goal

Turn measured CI evidence and contributor PR #180 into prospective, bounded
implementation contracts without retroactively authorizing its code.

Human-approved intent

The user directed the orchestrator to preserve strict zero-trust loop
engineering, review PR #180, and make the contributor work adoptable through
the normal plan, chunk, evidence, and PR process.

What changed

• Recorded PR Cut backend CI runtime 66%: 16m → 5m with isolated semantic test lanes #180 measurements and review gaps as discovery.
• Decided not to implement routing, caching, sampling, or durable timing now.
• Defined reset-safety chunk 02A as the only declared successor.
• Defined later exact-custody semantic-lane chunk 02B after 02A evidence.
• Reserved routing/cache/timing reassessment for future planning chunk 03.

Why it changed

PR #180 demonstrates a promising migrate-once direction, but its original diff
crosses destructive database reset and workflow-topology boundaries and lacked
prospective signed scope and complete exact-execution evidence.

Design chosen

First prove runner-owned destructive reset containment under the existing CI
topology. Then, under a separate signed chunk, change to dependency-based lanes
with independent node, coverage, PostgreSQL, and MinIO custody.

Alternatives rejected

• Merging PR Cut backend CI runtime 66%: 16m → 5m with isolated semantic test lanes #180 as-is was rejected because chat and retrospective artifacts
  cannot authorize implementation.
• One large reset-plus-workflow chunk was rejected as unreviewable L1/P0 scope.
• More arbitrary infrastructure shards were rejected because they add cost and
  do not address repeated migrations.
• Routing or sampling was rejected because it could suppress required proof.

Scope control

Only WS-CI-001 planning, decision, risk, status, chunk-contract, review, and one
merge-intent file change. No workflow, backend, test, dependency, coverage, or
product runtime file changes.

Product behavior

• No Workstream product behavior changed.

Acceptance criteria proof

• Original routing/cache/timing options received an evidence-backed decision.
• 02A and 02B have exact prospective file scope and immutable source commits.
• Reset ownership, node custody, service isolation, coverage, and timing are explicit.
• Only same-initiative 02A is declared and still requires a signed start.

Tests/checks run

python3 scripts/update_post_merge_memory.py validate-merge-intent --repository-root . --base-ref origin/main
python3 scripts/test_agent_gates.py
python3 scripts/check_loop_memory_state.py
python3 scripts/check_markdown_links.py
python3 scripts/check_stale_workstream_wording.py
python3 scripts/check_stale_authorization_docs.py
python3 scripts/check_stale_artifact_contracts.py
git diff --check origin/main...HEAD

All passed; 95 Agent Gate tests passed.

Test delta

No executable tests changed. Future contracts prohibit removed, skipped,
deselected, or weakened tests and require exact collection/completion proof.

CI integrity

• No workflow or package script changed
• Full suite remains required
• Global 78% and all protected 90% floors remain blocking
• No cache, routing, sampling, or timing authority introduced

Reviewer results

Reviewed code SHA: c10f084

Reviewed at: 2026-07-22T11:12:00Z

Reviewer run IDs: eng006_senior_arch_docs, eng006_qa_ci_tests, eng006_security_ops_reuse

All nine required tracks passed after the documented repairs, with no remaining
condition or blocker.

External review

PR #180 supplied discovery and contributor measurements. Its review findings
were incorporated into prospective contracts; it remains unauthorized for
merge under this planning chunk. Fresh GitHub and CodeRabbit review will run on
this planning PR.

Remaining risks

02A must prove destructive reset safety, and 02B must prove hosted exact-node,
coverage, isolation, and timing custody. Neither implementation is authorized
by this PR alone.

Follow-up work

After this PR merges and automation reconciles it, dispatch a signed start for
02A only. Do not start 02B or 03 automatically.

Human review focus

• Prospective authorization rather than retroactive adoption.
• 02A/02B boundary and exact file scope.
• Destructive reset containment and independent node custody.
• Preservation of Konan's authorship.

Human merge ownership

• I can explain what changed.
• I can explain why it changed.
• I know what could break.
• I accept the remaining risks.
• The user explicitly approved this specific PR for merge.

Summary by CodeRabbit

• Documentation
  • Updated backend CI acceleration plans and status to reflect completed work and newly defined successor phases.
  • Added detailed contracts for safer database resets and exact-custody semantic test lanes.
  • Documented evidence requirements, risks, review outcomes, verification steps, and stop conditions.
  • Deferred routing, dependency caching, and timing optimizations for future reassessment pending additional evidence.

[coderabbitai]

📝 Walkthrough

Walkthrough

WS-CI-001 planning records were amended to classify PR #180 as discovery-only, split follow-on work into reset and semantic-lane contracts, defer routing/cache/timing changes, add governance evidence, and require explicit activation of successor chunk 02A.

Changes

WS-CI-001 planning and successor contracts

Layer / File(s)	Summary
Evidence and amended execution plan .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/{CHUNK_MAP,DECISIONS,DISCOVERY,PLAN}.md	Planning status, discovery evidence, execution sequencing, and proof gates now distinguish 02A reset work from later 02B lane changes.
Reset and semantic-lane contracts .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/chunks/WS-CI-CI-001-02{A,B}-*.md	New contracts define safe database reset containment, exact node custody, isolated service namespaces, coverage binding, validation, and stop conditions.
Governance and deferred optimization scope .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/{RISKS,STATUS}.md, .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/chunks/WS-CI-001-02-safe-routing-cache-timing.md, .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/chunks/WS-CI-001-03-safe-routing-cache-timing-reassessment.md	Status and risk records were updated, while routing, caching, and durable timing changes remain deferred.
Review evidence and next-step metadata .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/reviews/*, .agent-loop/merge-intents/WS-CI-001-02.json	Internal review evidence and trust boundaries were recorded, and chunk 02 now points to 02A with explicit-start routing metadata.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: abiorh-claw

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title is concise and accurately summarizes the main planning change for safe migrate-once backend CI acceleration.
Description check	✅ Passed	The description covers the required trust-bundle sections, validation evidence, risks, and reviewer status, with only minor template-heading differences.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/ws-ci-001-02-semantic-lane-plan

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
@.agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/chunks/WS-CI-001-02A-safe-migrate-once-database-reset.md:
- Around line 33-51: Replace the broad status, review, and evidence categories
in WS-CI-001-02A-safe-migrate-once-database-reset.md (lines 33-51) with every
exact permitted path; apply the same explicit-path allowlist to
WS-CI-001-02B-exact-custody-semantic-test-lanes.md (lines 27-41). In PLAN.md
(lines 162-169), retain the exact-scope claim only after both contracts enforce
these enumerated paths.

In
@.agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/chunks/WS-CI-001-02B-exact-custody-semantic-test-lanes.md:
- Around line 12-17: Update the Preconditions section to state that contributor
source is limited to the two listed immutable SHAs; later commits are ineligible
unless a subsequent contract explicitly names their immutable SHAs and file
scope.

In
@.agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/reviews/WS-CI-001-02-internal-review-evidence.md:
- Around line 81-84: Update the custody wording in the PR `#180` evidence bullets
to state that adoption requires 02A custody to be signed, or equivalently
requires a signed 02A start; preserve the surrounding discovery-source and
future-evidence statements unchanged.

In
@.agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/reviews/WS-CI-001-02-pr-trust-bundle.md:
- Around line 3-7: Rename the trust-bundle title in the `WS-CI-001-02` chunk to
describe the planning amendment and its 02A reset-safety successor instead of
deferred routing, cache, and timing work. Update the corresponding title or
summary field in the `WS-CI-001-02` merge-intent metadata so both declarations
remain synchronized.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d47ca20d-c959-4a3e-919a-823ee7b0bfdc

📥 Commits

Reviewing files that changed from the base of the PR and between d7dfd73 and 8391a7c.

📒 Files selected for processing (13)

• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/CHUNK_MAP.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/DECISIONS.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/DISCOVERY.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/PLAN.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/RISKS.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/STATUS.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/chunks/WS-CI-001-02-safe-routing-cache-timing.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/chunks/WS-CI-001-02A-safe-migrate-once-database-reset.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/chunks/WS-CI-001-02B-exact-custody-semantic-test-lanes.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/chunks/WS-CI-001-03-safe-routing-cache-timing-reassessment.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/reviews/WS-CI-001-02-internal-review-evidence.md
• .agent-loop/initiatives/WS-CI-001-backend-ci-acceleration/reviews/WS-CI-001-02-pr-trust-bundle.md
• .agent-loop/merge-intents/WS-CI-001-02.json