chore(memory): close P0 in TODO after merge
ci / rust (push) Canceled after 0s
ci / check (push) Canceled after 0s
ci / docker (push) Canceled after 0s
ci / supabase (push) Canceled after 0s
ci / rust (push) Canceled after 0s
ci / check (push) Canceled after 0s
ci / docker (push) Canceled after 0s
ci / supabase (push) Canceled after 0s
This commit is contained in:
1 parent
dae74e00dc
commit
5502617193
1 file changed
+2
-2
@@ -369,14 +369,14 @@ feat/findings-tree-v2 merged (FindingsTreePicker tracked in HEAD); all work belo
|
||||
|
||||
## Product roadmap V1 (owner 2026-10-25 « Validation de l'inventaire et cadrage P0 / V1-1 »)
|
||||
Order (BDR-071): P0 docs + decisions → V1-1 clients and animals → V1-2 sheets served from Supabase → V1-3 cloud bilans + history → V1-4 stored PDF + authorised sharing → V1-5 cross-cutting mobile + a11y pass (a11y and security apply at every step). C4/C5/C6 and the V1-1 orientations (owner brief « P0 : arbitrages documentaires et finalisation du contrat V1-1 ») = proposed, awaiting ratification. No migration, component, API or table before the owner ratifies the V1-1 contract; no merge into main, no release/0.2.0 change, no deploy, no Supabase DEV change; equine draft stays unpublished.
|
||||
- [ ] P0 docs realignment (docs only; branch `chore/p0-doc-realignment` created by the owner off develop, the working-tree edits carried over; merge into develop on the owner's go only)
|
||||
- [x] P0 docs realignment (docs only; branch `chore/p0-doc-realignment` created by the owner off develop, the working-tree edits carried over; merge into develop on the owner's go only)
|
||||
- [x] census of stale text in active docs (worker Node / Edge Functions, step numbers, roles, Step 13 "published", deleted tools, OPEN_QUESTIONS statuses)
|
||||
- [x] IMPLEMENTATION_PLAN: roadmap V1 section, step statuses, D-R9 in Steps 8/15/19/21/23/24/26, Step 13 DoD draft-only, deleted tools, Step 22 D-R8
|
||||
- [x] BACKEND_ARCHITECTURE §1/§5/§6/§7/§9, DOMAIN_MAP §1/§6/§7/§12/§18, design README owners, snapshot notices (FRONTEND_ARCHITECTURE, MIGRATION_STRATEGY, REPOSITORY_MIGRATION_MAP, TEST_STRATEGY), PDF_IMPORT_HARDENING step numbers, README DEV origin, CLAUDE.md roadmap line
|
||||
- [x] OPEN_QUESTIONS: status per item with the deciding BDR / D-R, C4/C5/C6 owner hypotheses, real conflicts listed for arbitration
|
||||
- [x] owner arbitration 2026-10-25: README separates public 0.1.0 / develop / DEV-only / planned; CHANGELOG Unreleased note (nothing deployed, 0.2.0 section on its branch); DEPLOY status notice (historical, unverified, would-break, security prerequisites) + CSP examples marked not production-ready (fixes stay RR-5); OPEN_QUESTIONS conflicts 1-4 resolved (curation-only path until Step 17 confirmed); BDR-071, BDR-072 (BDR-041 step number), EVAL-034
|
||||
- [x] commit on the branch, push
|
||||
- [ ] merge into develop on the owner's go
|
||||
- [x] merged into develop 2026-10-25 (no-ff dae74e0, owner go); V1-1 waits for ratification of contract §9
|
||||
- [x] V1-1 functional contract `docs/development/V1-1_OWNERS_ANIMALS.md` (no code); correction: inventory criterion 4 (validation in crates/core) contradicted D-R7 → form constraints TS + SQL CHECK + parity test (EVAL-034)
|
||||
- [x] owner orientations D1-D9, D16, C4-C6 integrated as proposals (§9.1, SQL / permission impact marked); sub-choices D4a, D6a, D6b, D7a, D9a (§9.2); D10-D15, D17 kept open (§9.3); legal basis, client information, retention framed before public exposure (§9.4)
|
||||
- [ ] owner ratification of §9.1, answers to §9.2 and D15 → first migration on a `feature/` branch
|
||||
|
||||
Reference in new issue
Block a user