docs: close Phase 0 acceptance gate

This commit is contained in:
chick
2026-07-16 08:07:58 +08:00
parent c7da857aff
commit 43a69d8617
10 changed files with 473 additions and 23 deletions
+1 -1
View File
@@ -9,7 +9,7 @@
- **Sensitive fields:** every item carries snapshot-rebuildable evidence (file/range/SHA-256/symbol/model field), with explicit container model chains for array paths and exact handler slices for dynamic keys.
- **Boundary / semanticBindingReview:** structural checks prove source/model/field relationships, not semantic payload intent. Each registry operation is marked `semanticBindingReview: 'reviewed-phase-0.2'`; manual review fixes the method/path/handler/payload-symbol tuple, especially high-value response bindings.
- **Policy:** every R2 requires at least explicit confirmation; every R3 requires strong confirmation. Auth/session-sensitive operations use dedicated flow/replay protections.
- **Phase 0.3 仅负责采集真实响应样本** (`responseFixtureStatus=pending-phase-0.3`); static evidence is not a runtime fixture.
- **Phase 0.3 真实响应样本 disposition:** the per-operation `responseFixtureStatus=pending-phase-0.3` value is retained as a frozen Phase 0.2 claim and is deprecated for current coverage decisions. The authoritative current value is `runtimeFixtureStatus` in `packages/operation-registry/src/acceptance-58e2204.ts`, derived from the collector selection and real fixture manifest. Static evidence is not a runtime fixture.
## Whole-file snapshot SHA-256