Update current state and next steps docs

docs/current-state.md

@@ -3,8 +3,9 @@
 ## Status Summary
 
 AtoCore is no longer just a proof of concept. The local engine exists, the
-correctness pass is complete, and Dalidou now hosts the canonical runtime and
-machine-storage location.
+correctness pass is complete, Dalidou now hosts the canonical runtime and
+machine-storage location, and the T420/OpenClaw side now has a safe read-only
+path to consume AtoCore.
 
 ## Phase Assessment
 
@@ -38,6 +39,8 @@ machine-storage location.
 - API routes for query, context, health, and source status
 - env-driven storage and deployment paths
 - Dalidou Docker deployment foundation
+- initial AtoCore self-knowledge corpus ingested on Dalidou
+- T420/OpenClaw read-only AtoCore helper skill
 
 ## What Is True On Dalidou
 
@@ -55,16 +58,37 @@ The service and storage foundation are live on Dalidou.
 
 The machine-data host is real and canonical.
 
-The content corpus is not fully populated yet. A fresh or near-fresh live DB is
-running there until the ingestion pipeline loads the ecosystem docs and project
-content.
+The content corpus is partially populated now.
+
+The Dalidou instance already contains:
+
+- AtoCore ecosystem and hosting docs
+- current-state and OpenClaw integration docs
+- Master Plan V3
+- Build Spec V1
+- trusted project-state entries for `atocore`
+
+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
+completed.
+
+## What Is True On The T420
+
+- SSH access is working
+- OpenClaw workspace inspected at `/home/papa/clawd`
+- OpenClaw's own memory system remains unchanged
+- a read-only AtoCore integration skill exists in the workspace:
+  - `/home/papa/clawd/skills/atocore-context/`
+- the T420 can successfully reach Dalidou AtoCore over network/Tailscale
+- fail-open behavior has been verified for the helper path
 
 ## Immediate Next Focus
 
-1. Ingest AtoCore ecosystem and planning docs into the Dalidou instance
-2. Define the OpenClaw integration contract clearly
-3. Wire OpenClaw to consume AtoCore read-only over network
-4. Ingest selected project content in a controlled way
+1. Use the new T420-side AtoCore skill in real OpenClaw workflows
+2. Ingest selected active project sources in a controlled way
+3. Define the first broader AtoVault/AtoDrive ingestion batches
+4. Add backup/export strategy for Dalidou machine state
+5. Only later consider deeper automatic OpenClaw integration or write-back
 
 ## Guiding Constraints