feat(memory): add graph runtime import store

workplans/KONT-WP-0017-agentic-memory-graph-runtime.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Agentic Memory Graph Runtime And Operational State"
 domain: markitect
 repo: kontextual-engine
-status: todo
+status: active
 owner: codex
 topic_slug: markitect
 planning_priority: medium
@@ -59,11 +59,32 @@ Disallowed responsibilities:
 - Do not require any one graph database, vector store, LLM provider, or
   enterprise policy system in the core implementation.
 
+## Implementation Update - 2026-05-15
+
+The first runtime-contract slice is implemented. `kontextual-engine` can now
+map `markitect.memory.graph.v1` and `markitect.memory.profile.v1` envelopes
+into stable runtime records, persist them through a `MemoryGraphRepository`
+port, and use `InMemoryMemoryGraphRepository` as the deterministic local
+implementation for tests.
+
+The implementation deliberately does not validate Markitect's node/edge
+vocabulary. It checks runtime compatibility concerns only: schema version,
+required ids, edge endpoint integrity, stable runtime id mapping, source-span
+preservation, and append-only event identity.
+
+Primary files:
+
+- `src/kontextual_engine/core/memory.py`
+- `src/kontextual_engine/ports/memory.py`
+- `src/kontextual_engine/adapters/memory/graph_store.py`
+- `src/kontextual_engine/services/memory_service.py`
+- `docs/memory-graph-runtime.md`
+
 ## P17.1 - Import and map Markitect memory contracts
 
 ```task
 id: KONT-WP-0017-T001
-status: todo
+status: done
 priority: high
 state_hub_task_id: "1b1f8904-3a3b-4d23-9d00-176633578801"
 ```
@@ -86,7 +107,7 @@ Output: contract import design, mapping tests, and compatibility fixtures.
 
 ```task
 id: KONT-WP-0017-T002
-status: todo
+status: done
 priority: high
 state_hub_task_id: "dc3557e3-d425-46b0-8acc-9ac0230a385c"
 ```