Harden RRI handoff app-status invariants - #519
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR hardens release-readiness validation by adding per-evidence checks for app-status snapshots within handoff JSON. The validation enforces schema compliance, engine state authority, /move write intent, and optional build SHA matching, with supporting test infrastructure updates and three new contract test cases. ChangesApp-status handoff validation
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Comment |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
Summary
/app-statuscontract, not just the manifest summary.worldos.app-status.v1,state_authority=engine,write_lane=/move, and matching build SHA./movewrite lane, and app-status build mismatch.Why
The release objective depends on the engine remaining the sole campaign-state writer while the GUI/native app only reads state and submits
/moveintents. RRI should not accept split Mac handoff evidence unless the captured app-status snapshots prove that invariant directly.Validation
python3 -m pytest qa/test_release_readiness.py -qpython3 -m pytest qa/test_release_readiness.py qa/test_app_handoff_gate.py qa/test_export_app_evidence.py -qpython3 -m py_compile qa/release_readiness.pygit diff --checkvalid=True,gaps=0.Release note
This is release-gate hardening only. It is not a release verdict.
Summary by CodeRabbit