Document organic OpenClaw routing layer

docs/current-state.md

@@ -145,6 +145,11 @@ It is important to read this staged area correctly:
   - register-project
   - update-project
   - refresh-project
+- the helper now also supports the first organic routing layer:
+  - `detect-project "<prompt>"`
+  - `auto-context "<prompt>" [budget] [project]`
+- OpenClaw can now default to AtoCore for project-knowledge questions without
+  requiring explicit helper commands from the human every time
 
 ## What Exists In Memory vs Corpus
 
@@ -217,12 +222,15 @@ This separation is healthy:
 
 ## Immediate Next Focus
 
-1. Use the new T420-side AtoCore skill and registration flow in real OpenClaw workflows
-2. Keep the new engineering-knowledge architecture docs as implementation guidance while avoiding premature schema work
-3. Tighten retrieval quality for the newly seeded active projects
-4. Define the first broader AtoVault/AtoDrive ingestion batches
-5. Add backup/export strategy for Dalidou machine state
-6. Only later consider deeper automatic OpenClaw integration or write-back
+1. Use the new T420-side organic routing layer in real OpenClaw workflows
+2. Keep tightening retrieval quality for the newly seeded active projects
+3. Define the first broader AtoVault/AtoDrive ingestion batches
+4. Keep the new engineering-knowledge architecture docs as implementation guidance while avoiding premature schema work
+5. Expand the boring operations baseline:
+   - restore validation
+   - Chroma rebuild / backup policy
+   - retention
+6. Only later consider write-back, reflection, or deeper autonomous behaviors
 
 See also: