Update current state and next steps docs

docs/openclaw-integration-contract.md

@@ -8,6 +8,23 @@ AtoCore.
 The goal is to let OpenClaw consume AtoCore as an external context service
 without degrading OpenClaw's existing baseline behavior.
 
+## Current Implemented State
+
+The first safe integration foundation now exists on the T420 workspace:
+
+- OpenClaw's own memory system is unchanged
+- a local read-only helper skill exists at:
+  - `/home/papa/clawd/skills/atocore-context/`
+- the helper currently talks to the canonical Dalidou instance
+- the helper has verified:
+  - `health`
+  - `project-state`
+  - `query`
+  - fail-open fallback when AtoCore is unavailable
+
+This means the network and workflow foundation is working, even though deeper
+automatic integration into OpenClaw runtime behavior is still deferred.
+
 ## Integration Principles
 
 - OpenClaw remains the runtime and orchestration layer
@@ -50,6 +67,18 @@ OpenClaw should treat these as the initial contract:
 Additional project-state inspection can be added if needed, but the first
 integration should stay small and resilient.
 
+## Current Helper Surface
+
+The current helper script exposes:
+
+- `health`
+- `sources`
+- `stats`
+- `project-state <project>`
+- `query <prompt> [top_k]`
+- `context-build <prompt> [project] [budget]`
+- `ingest-sources`
+
 ## Failure Behavior
 
 OpenClaw must treat AtoCore as additive.
@@ -86,6 +115,7 @@ Recommended first behavior:
 
 ## Deferred Work
 
+- deeper automatic runtime wiring inside OpenClaw itself
 - memory promotion rules
 - identity and preference write flows
 - reflection loop