Add project registry update flow

docs/project-registration-policy.md

@@ -2,7 +2,8 @@
 
 ## Purpose
 
-This document defines the normal path for adding a new project to AtoCore.
+This document defines the normal path for adding a new project to AtoCore and
+for safely updating an existing registration later.
 
 The goal is to make `register + refresh` the standard workflow instead of
 relying on long custom ingestion prompts every time.
@@ -18,6 +19,13 @@ Registration means:
 - the staged source roots for that project are defined
 - AtoCore and OpenClaw can later refresh that project consistently
 
+Updating a project means:
+
+- aliases can be corrected or expanded
+- the short registry description can be improved
+- ingest roots can be adjusted deliberately
+- the canonical project id remains stable
+
 ## Required Fields
 
 Each project registry entry must include:
@@ -82,6 +90,17 @@ For a new project:
 7. verify retrieval and context quality
 8. only later promote stable facts into Trusted Project State
 
+For an existing registered project:
+
+1. inspect the current entry with:
+   - `GET /projects`
+   - or `atocore.sh projects`
+2. update the registration if aliases, description, or roots need refinement:
+   - `PUT /projects/{id}`
+3. verify the updated entry
+4. refresh the project again
+5. verify retrieval and context quality did not regress
+
 ## What Not To Do
 
 Do not:
@@ -106,4 +125,5 @@ Other lifecycle endpoints:
 
 - `POST /projects/proposal`
 - `POST /projects/register`
+- `PUT /projects/{id}`
 - `POST /projects/{id}/refresh`