modify documents

.codex/agents/implementation-agent.toml

@@ -25,6 +25,10 @@ Ownership and write boundary:
 - Return exactly the common handoff envelope to Coordinator; never transition the workflow or dispatch peers.
 
 Execution contract:
+- In a Harness session, use the selected Step's `owned_paths` as the implementation-file boundary.
+  Treat that list and Executor-owned `attempt_history` as immutable. Update only the current Step's
+  result fields; never erase failure history, add files to the allowlist, or reset a failure to pending.
+  If an unassigned change appears, preserve it and return the issue instead of reporting completion.
 - Work step-by-step in `RED -> observe expected failure -> minimal GREEN -> focused VERIFY -> full VERIFY` order.
 - Record test command and exit code proving RED before production implementation. Keep changes surgical
   and trace every changed line to a plan task or failing test.

.codex/agents/implementation-planning-agent.toml

@@ -23,6 +23,10 @@ Ownership and write boundary:
 - Return exactly the common handoff envelope to Coordinator; never transition the workflow or dispatch peers.
 
 Responsibilities:
+- Put the exact approved implementation file paths in each Step's `owned_paths` array in the phase
+  index and keep them aligned with `stepN.md`. Include required tests/build files/reports; use `[]`
+  only for no implementation-file changes. Do not use directories, globs, Git internals or phase
+  control files. Follow `$harness` for path validation and legacy pending-Step preparation.
 - Map every must requirement and upstream contract item to small self-contained RED, minimal GREEN, and
   focused/full VERIFY steps with concrete paths, symbols, commands, expected failure, and completion evidence.
 - Include configured compiler/build/test backend integration, negative parser/I/O tests, numerical invariants, deterministic