fix: complete state-contract naming cleanup

docs/report/2026-10-06-t704-validation.md

@@ -1,5 +1,7 @@
 # T-704 implementation and validation ledger
 
+Editorial note (2026-10-10): obsolete state terminology is summarized by purpose below; cited IDs, commits and validation results still describe the original investigation, not new executions.
+
 Base: `6f9621ca` (clean detached assigned checkout). Parent created
 `work/t-704-backend-subjektiv-jobs` without replacing a branch or discarding changes.
 Parent owns Backend/Profile/Subject authorization, cutover, documentation and
@@ -24,7 +26,7 @@ Independent MR review is separate from implementation delegation.
 - Synchronous bounded clean-context surface generation before result submission.
   Preparation reports an already-current snapshot to avoid needless conflicting
   regeneration. Job failure acknowledgements are `failed_confirmed` only after
-  checking the actual failed marker/reason/revision and generation provenance.
+  checking the actual failed marker/reason/then-current store condition and generation provenance.
   Subject feature migration 6 adds immutable generation Job/attempt provenance,
   without changing Subject/Memory/candidate content.
 - Durable results contain actual candidate dispositions and a separate verified
@@ -99,7 +101,7 @@ resolution records for a 100-ID batch could exceed the common 16 KiB result boun
 even when candidate decisions and surface generation had actually completed.
 That pending old-source review was stopped rather than treated as approval.
 
-The follow-up keeps full immutable receipts/reasons/revision/source edges in their
+The follow-up keeps full immutable receipts/reasons/immutable history references/source edges in their
 existing store and persists only verified `{candidate_id, action}` summaries in
 the Job result. Batch selection conservatively budgets the complete result,
 including JSON-escaped IDs in both claim and outcome, plus a reserved bounded