chore(memory): BDR-097 V1-2.5 start decisions, TODO plan

This commit is contained in:
bchanot committed 2026-11-02 16:06:55 +01:00
1 parent 3d80812cdb
commit a701b04210
2 files changed
+21

No files matched your search

+9
View File
@@ -745,3 +745,12 @@ Also: G1/G2 corrections validated, conformance 8/8 acknowledged; UX decisions 2-
7. V1-2.5 authorised once §16.6 dependencies VERIFIED, existing contract only. Kept: no merge develop/main/release, no Supabase DEV op without own authorisation, no DEV worker, tests + independent review fit for step, commits + pushes on V1-2 branch, STOP at V1-2.5 checkpoint. Design not reopened without demonstrated defect or new owner decision.
**Rationale**: four review rounds (G1/G2, final corrections, arbitrations, verifier CONFORME 21/21) closed every graphic finding; remaining messages are integration-time checks against code.
**Alternatives**: regenerate board 12 with final wordings (rejected by brief: design not modified); hold approval until every message settled (rejected: owner closes graphics, messages at integration).
## BDR-097 — V1-2.5 start: M7 admin read migration, working-copy action in V1-2.5, EN Permission for Habilitation (2026-11-02)
- **Status**: accepted
**Decision**: V1-2.5 started 2026-11-02 under brief « Validation propriétaire V1-2.4 » after prerequisite check on 994b04e: V1-2.1 VERIFIED at ac71c5b (M4/M5 unchanged since), V1-2.2 VERIFIED (BDR-092), V1-2.4 approved (BDR-096), V1-2.3 VERIFIED (BDR-093). Owner answers (AskUserQuestion, 2026-11-02) to three gaps found at start:
1. Admin reads: admin list needs working-copy badge + round counts; `working_copy_source_version_id` excluded from table grants (§5.3), no admin read RPC existed, §16.6 said « SQL changes: none ». Chosen: one read migration M7 `sheet_admin_reads` (list + overview RPCs, capability holders at aal2, no write path, no policy/rule change), sandbox only, DEV untouched. Contract §12.3, §16.6, §17.10.
2. Working copy: « Créer une copie de travail » built in V1-2.5 (board 10) on existing `create_sheet_working_copy`, lands on copy's overview; editor link with V1-2.6. A1 new sheet also lands on overview until V1-2.6.
3. EN term: « Habilitation » = « Permission » in English UI; `capability` stays technical term. Contract §3 amended.
**Rationale**: board 10 (approved) shows badge, counts and working-copy action; column grant widening would expose the column to readers (§5.3); a read RPC keeps reader grants narrow. « Permission » follows L14 « Access and permissions ».
**Alternatives**: drop badge in V1-2.5 (deviates from §11.1 + board 10); widen column grant (rejected, §5.3); defer working-copy action to V1-2.6; keep EN « Capability » (§3 old).