decision: gate SR-04 behind V1R4C4 reliability freeze

2026-07-10 09:14:40 +08:00
1 changed files with 116 additions and 0 deletions
@@ -0,0 +1,116 @@
+# V1R4C4 Reliability Freeze Before SR-04
+
+Status: accepted
+
+Decision date: 2026-07-10
+
+Current baseline: V1R4C3
+
+## Decision
+
+V1R4C4 will complete reliability freeze before merging Portal AIOS Integration.
+
+SR-04 remains `activation-ready`, but it must not be merged or deployed before SR-01 and SR-02 are complete and accepted.
+
+## Scope Ordering
+
+```text
+SR-01 Gitea Branch Sync Fix
+        ↓
+SR-02 Watcher State Cleanup
+        ↓
+SR-04 Portal AIOS Integration Merge
+```
+
+## SR-01 Gate
+
+SR-01 must complete the P0 reliability work for Gitea branch sync and metadata drift.
+
+Required outcomes:
+
+1. branch_sync remains independent of Gitea branch API pagination.
+2. bare repository refs, Gitea DB branch metadata, and Gitea API visible state are checked for consistency.
+3. branch metadata drift triggers autonomous safe mode.
+4. recovery procedure favors minimal repair over default restart.
+5. runtime acceptance passes.
+
+Acceptance sequence:
+
+```text
+getRuntimeStatus
+    ->
+getBaseline
+    ->
+createBranch
+    ->
+createPatch
+```
+
+## SR-02 Gate
+
+SR-02 must complete watcher state cleanup integration.
+
+Current known test signal:
+
+```text
+11 / 11 tests pass
+```
+
+Required outcomes:
+
+1. stuck command detection reads parsed timestamps correctly.
+2. `.json` command state files are handled correctly.
+3. `.md` command state files are handled correctly.
+4. file mtime semantics are aligned with stored stuck timestamps in tests.
+5. watcher cleanup is integrated behind the reliability assumptions introduced by SR-01.
+
+## SR-04 Status
+
+SR-04 remains:
+
+```text
+activation-ready
+```
+
+But SR-04 is explicitly blocked from merge/deploy until SR-01 and SR-02 gates are green.
+
+SR-04 may continue with planning, diff review, and acceptance design, but may not perform production portal deployment.
+
+## Reason
+
+The user-visible portal feature gap is real, but the system recently experienced a stop-the-line reliability incident involving Gitea branch metadata drift. Reliability freeze must complete first to avoid combining production portal changes with unresolved GitOps/Gitea consistency risk.
+
+## Allowed During Freeze
+
+Allowed:
+
+- SR-04 planning;
+- SR-04 diff review;
+- frontend/backend contract review;
+- RBAC acceptance design;
+- non-production validation;
+- documentation updates.
+
+Not allowed before SR-01/SR-02 acceptance:
+
+- merging SR-04 to main;
+- deploying SR-04 to production;
+- bypassing RBAC to expose modules;
+- combining portal integration with Gitea DB repair;
+- bulk merging old portal branches.
+
+## SR-04 Release Gate
+
+SR-04 may enter merge/deploy only after:
+
+1. SR-01 acceptance is green.
+2. SR-02 acceptance is green.
+3. GitOps runtime acceptance is green.
+4. Gitea consistency sentinel is deployed or explicitly deferred with owner approval.
+5. Portal RBAC acceptance plan is approved.
+
+## Final Rule
+
+V1R4C4 is reliability-first.
+
+Portal AIOS Integration remains prepared but gated until reliability freeze is complete.