Add project registry update flow

docs/current-state.md

@@ -43,6 +43,7 @@ now includes a first curated ingestion batch for the active projects.
   - template
   - proposal preview
   - approved registration
+  - safe update of existing project registrations
   - refresh
 - env-driven storage and deployment paths
 - Dalidou Docker deployment foundation
@@ -98,9 +99,9 @@ The Dalidou instance already contains:
 Current live stats after the latest documentation sync and active-project ingest
 passes:
 
-- `source_documents`: 35
-- `source_chunks`: 560
-- `vectors`: 560
+- `source_documents`: 36
+- `source_chunks`: 568
+- `vectors`: 568
 
 The broader long-term corpus is still not fully populated yet. Wider project and
 vault ingestion remains a deliberate next step rather than something already
@@ -162,10 +163,19 @@ The source refresh model now has a concrete foundation in code:
 - the API can return a registration template
 - the API can preview a registration without mutating state
 - the API can persist an approved registration
+- the API can update an existing registered project without changing its canonical id
 - the API can refresh one registered project at a time
 
 This lifecycle is now coherent end to end for normal use.
 
+The first live update pass on an existing registered project has also now been
+verified against `p04-gigabit`:
+
+- the registration description can be updated safely
+- the canonical project id remains unchanged
+- refresh still behaves cleanly after the update
+- `context/build` still returns useful project-specific context afterward
+
 ## Reliability Baseline
 
 The runtime has now been hardened in a few practical ways: