Inventory legacy tenant runtime routes

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02b6f-7db1-7222-918b-e813a6bda38d

workplans/HARNESS-WP-0003-governed-runtime-integrity.md

@@ -109,6 +109,9 @@ and T02–T06 can cite stable decisions rather than infer ownership from code.
   (`7fd35fd4-b0e1-42f0-bb56-a983a3e25c78`), and llm-connect
   (`c5d1dc62-3dca-4ac8-b3b5-d570d723ceda`). T01 remains `progress` and
   downstream tasks remain `wait` until those reviews are reconciled.
+- Glas approved the proposed boundary without edits in message
+  `006fa46f-9419-4f61-90ff-0c3b6bc294c1`. Activity Core, sand-boxer, and
+  llm-connect acknowledgements remain pending.
 
 ## Make each repository run a lease-bound transaction
 
@@ -207,6 +210,14 @@ production runs through generic selectors; tenant modules and hard-coded event,
 path, and prompt conventions are removed or moved to their owning packages;
 and the compatibility flag is disabled before deletion.
 
+### Preparation — 2026-08-23
+
+`docs/legacy-runtime-inventory.md` records the four profile-absent scheduled
+definitions and the direct/issue-core compatibility surfaces from current code
+and owner files. It identifies inputs, outputs, credentials, completion events,
+commit/push behavior, retry posture, rollback material, and migration gates.
+This is read-only preparation; T04 remains `wait` until T01 accepts ADR-002.
+
 ## Align deployment, recovery, and conformance with the supported runtime
 
 ```task