docs: mark coherence rules as target contract

Co-Authored-By: Paperclip <noreply@paperclip.ing>

doc/SPEC-implementation.md

@@ -1043,10 +1043,11 @@ The current app also exposes V1-supporting surfaces for:
   derive `deliveryState` as `merged_via_pr | merged_by_ancestry | unmerged | unknown`; terminal issue trees with a
   merged delivery and no active checkout run become cleanup-eligible with reason `issue_terminal` and are archived
   through the workspace cleanup path. Reopening the source issue records activity but does not restore that workspace.
-  A code-fix completion claim must register an inspectable branch, commit, or pull-request work product appropriate to
-  the requested handoff and prove that the cited change is on that delivery path. Managed runtime command postconditions,
-  bounded isolated-workspace port allocation, desired-versus-actual state, and delivery-evidence semantics are defined
-  under adapter-backed workspace coherence in `doc/execution-semantics.md`.
+  The accepted target contract for remaining adapter-backed workspace coherence work requires a code-fix completion claim
+  to register an inspectable branch, commit, or pull-request work product appropriate to the requested handoff and prove
+  that the cited change is on that delivery path. It also requires coherent managed runtime command postconditions, bounded
+  isolated-workspace port allocation, and separate desired and actual state. Not every current runtime or completion path
+  enforces these target requirements yet; their normative details are in `doc/execution-semantics.md`.
 - task watchdog configuration and reusable watchdog issue orchestration for explicitly watched issue subtrees
 - routines and scheduled/API/webhook triggers
 - plugin installation, configuration, state, jobs, logs, webhooks, and plugin database namespace migration

doc/execution-semantics.md

@@ -412,6 +412,8 @@ Task and execution-workspace UI must render inherited and local effective runtim
 
 #### Delivery evidence for claimed fixes
 
+This subsection continues the target contract above; it does not claim that every current completion path enforces delivery evidence yet.
+
 An issue that claims a code fix is complete must register inspectable delivery evidence appropriate to the requested handoff: the branch, commit, or pull-request work product that contains the fix, plus ancestry or pull-request-head evidence that the cited change is actually on that delivery path. A local commit proves implementation but does not prove upstream delivery when the requested outcome is a pull request or merged change. Tests, screenshots, comments, and runtime logs remain verification evidence; they do not replace branch/commit/pull-request delivery evidence.
 
 ### Explicit recovery actions