fix(loop-memory): recover exact R4 activation

[Abiorh001]

PR Trust Bundle: WS-ENG-007-00R5

Intent

Reconcile exact merged R4 and activate its authority-projection repair without
restoring mutable check authority or starting any successor.

Scope

• Pin signed basis a3eecadc….
• Recover only PR fix(loop-memory): isolate cross-initiative authority evidence #191 / R4 / 9bf16d47….
• Activate only R5.
• Require merge-bound agent-gates and test evidence for both records.
• Consume both exemptions before signed publication.

Reviewed Revision

10159497b3f3ca3464cbbbfd10f16945ade1879a

CI Integrity

• 297 focused tests pass.
• Updater branch coverage is 90.46 percent.
• Independent-checker branch coverage is 90.40 percent.
• No workflow, threshold, permission, required check, signed start, or human
  merge checkpoint is weakened.

Reviewer Result

All nine required internal tracks passed after rejecting the initial schema-v3
approach. No Critical, High, or Medium finding remains open.

Human Review Focus

• Confirm schema v5 requires exactly one recovered predecessor and exact signed
  basis.
• Confirm CodeRabbit is supplementary and mutable reruns are not authority.
• Confirm exemptions are exact, adjacent, consumed, and non-replayable.
• Confirm R5 stops and starts neither ENG-006 nor ENG-007-01.

Remaining Risk

An intervening protected-main merge invalidates adjacency and must require a new
reviewed certificate rather than reinterpretation.

Summary by CodeRabbit

• New Features

  • Added recovery handling for the R4 activation scenario, including exact predecessor and merge evidence validation.
  • Added schema version 5 support for signed recovery policies and merge-bound recovery records.
  • Added safeguards to consume recovery exemptions exactly once and reject mismatched recovery bases.
  • Added configuration for the next recovery step, requiring explicit activation.

• Documentation

  • Updated recovery plans, status tracking, review evidence, trust documentation, and acceptance criteria.

• Tests

  • Added regression coverage for schema validation, evidence matching, exemption consumption, and replay protection.

[coderabbitai]

Warning

Review limit reached

@Abiorh001, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 31a3817b-54ab-44b8-945b-b8cf5e00ea0c

📥 Commits

Reviewing files that changed from the base of the PR and between 91eb244 and 2d47a5b.

📒 Files selected for processing (2)

• .agent-loop/initiatives/WS-ENG-007-concurrent-pr-review-reconciliation/reviews/WS-ENG-007-00R5-external-review-response.md
• .agent-loop/initiatives/WS-ENG-007-concurrent-pr-review-reconciliation/reviews/WS-ENG-007-00R5-internal-review-evidence.md

📝 Walkthrough

Walkthrough

The PR adds the WS-ENG-007 R5 activation-recovery contract, updates loop-memory recovery state to schema v5, extends validation and exemption preparation, and adds regression tests plus internal review evidence for exact R4 merge reconciliation.

Changes

WS-ENG-007 R5 activation recovery

Layer / File(s)	Summary
Define R5 recovery contract .agent-loop/initiatives/WS-ENG-007-concurrent-pr-review-reconciliation/*, .agent-loop/merge-intents/*, .agent-loop/policies/*	R4 is recorded as merged, R5 becomes the active recovery chunk, and schema-v5 state binds recovery to the exact predecessor, signed basis, merge evidence, and explicit successor-start rules.
Validate merge-bound recovery scripts/update_post_merge_memory.py	Recovery-policy validation and exemption preparation now support schema version 5, including signed-basis consistency and recovered-merge sequence handling.
Prove recovery behavior scripts/test_*.py, .agent-loop/initiatives/.../reviews/*	Tests verify exact policy pinning, merge-bound R4-to-R5 exemptions, consumption, and signed-basis failures; review documents record verification results, risks, and stop conditions.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

• Flow-Research/workstream#190: Introduced the merge-bound evidence handling extended here for schema-v5 recovery.
• Flow-Research/workstream#191: Provides the R4 merge consumed by this R5 activation-recovery flow.
• Flow-Research/workstream#189: Added preceding recovery-policy and protected-check handling in the same implementation paths.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers intent and risk, but it omits many required template sections like Chunk, Goal, Evidence, Test Delta, and reviewer tables.	Add the missing template sections and fill in Chunk, Goal, What Changed, Evidence, Acceptance Criteria Proof, Test Delta, and reviewer tables.
Docstring Coverage	⚠️ Warning	Docstring coverage is 37.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and matches the main change: exact R4 activation recovery.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/ws-eng-007-00r5-r4-activation

---

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: 1

🤖 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-ENG-007-concurrent-pr-review-reconciliation/reviews/WS-ENG-007-00R5-internal-review-evidence.md:
- Around line 67-70: Update the “Stop Condition” section to state that ENG-006
and WS-ENG-007-01 are inactive while the R5 recovery chunk within ENG-007
remains active, replacing the incorrect claim that ENG-007 is inactive.

🪄 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: e4411762-d012-42f3-ad87-3eb355aac839

📥 Commits

Reviewing files that changed from the base of the PR and between 9bf16d4 and 91eb244.

📒 Files selected for processing (10)

• .agent-loop/initiatives/WS-ENG-007-concurrent-pr-review-reconciliation/CHUNK_MAP.md
• .agent-loop/initiatives/WS-ENG-007-concurrent-pr-review-reconciliation/STATUS.md
• .agent-loop/initiatives/WS-ENG-007-concurrent-pr-review-reconciliation/chunks/WS-ENG-007-00R5-r4-activation-recovery.md
• .agent-loop/initiatives/WS-ENG-007-concurrent-pr-review-reconciliation/reviews/WS-ENG-007-00R5-internal-review-evidence.md
• .agent-loop/initiatives/WS-ENG-007-concurrent-pr-review-reconciliation/reviews/WS-ENG-007-00R5-pr-trust-bundle.md
• .agent-loop/merge-intents/WS-ENG-007-00R5.json
• .agent-loop/policies/loop-memory-recovery.json
• scripts/test_agent_gates.py
• scripts/test_update_post_merge_memory.py
• scripts/update_post_merge_memory.py