GOVERNANCE_HARD_CUT_PROGRESS.md

Governance Hard Cut Progress (2026-04-19 Revalidation)

Branch: codex/governance-terminology-hard-cut-exec

Current Status

• Unit 1 (boundary scaffold): partial
• Unit 2 (auth policy boundary cutover): partial
• Unit 3 (canonical contract + workflow secret baseline): done
• Unit 4 (single-window consumer contract cutover): partial
• Unit 5 (docs/gate closeout): partial

Multi-Agent Audit Summary

1. Three parallel lanes executed for status revalidation:
   • Lane A: Unit 1 + Unit 2
   • Lane B: Unit 3 + Unit 4
   • Lane C: Unit 5 + Gate traceability
2. Unit 3 is technically complete and test-covered.
3. Unit 1/2/4/5 are behavior-mostly-green but not fully plan-file-parity-complete.
4. A gate-trace mismatch remains between plan naming (G0/G1/G2/G3) and execution log naming (Gate A/B/C).

Fresh Verification Snapshot

• pnpm run backend:capability-boundary:check pass
• pnpm --filter @text2sql/backend exec jest --runInBand test/unit/capability-boundary-check.spec.ts test/integration/policy-evaluator.spec.ts test/e2e/workspace-datasource-authz.spec.ts test/e2e/user-workspace-authz.spec.ts pass
• pnpm --filter @text2sql/backend exec jest --runInBand test/e2e/datasource-workflow-api.spec.ts test/e2e/workspace-datasource-api.spec.ts test/e2e/chat-table-permissions-policy.spec.ts test/integration/datasource-service.spec.ts pass
• pnpm run governance:terminology:check pass (legacy module list line marked with governance-terminology:allow-legacy)

Open Items

1. Complete Unit 2 governance access guard ownership landing.
2. Reconcile Unit 4 plan-listed declaration file expectation (api.d.ts) with actual shared-types generation/runtime path.
3. Align and close gate records (G0/G1/G2/G3) with owner sign-off evidence.

Detailed Log

• Full execution notes: docs/plans/2026-04-18-004-refactor-governance-domain-terminology-hard-cut-execution-log.md
• Working tracker: docs/plans/2026-04-18-004-refactor-governance-domain-terminology-hard-cut-progress-tracker.md