docs(p5-13): record grounding qualification blockers and evidence

docs/redesign/phase-5/OPEN_BLOCKERS.md

@@ -53,6 +53,8 @@ Reconciled against [P4-06](../phase-4/p4-06/README.md#opendeferred-issue-reconci
 
 **P5-13 — AI Model Semantic Qualification / AI Review UI: DEFERRED — BLOCKED / NOT QUALIFIED.** This records Connor's explicit deferral at source checkpoint `9c9157507937b3e084a7ca1e79a2ebd77d0b0928`; it does not complete P5-13 or remove its [approved requirements](PHASE5_PLAN.md#p5-13--cv-ai-review-presentation).
 
+**Latest qualification checkpoint / sequencing — 2026-10-08:** [The bounded qualification record](p5-13-qualification/README.md) retains **NO-GO for P5-13 UI**, 0/366 real calls, 0 human reviews and unmeasured factuality. Fresh 108 focused AI / 5 revision / 2 native HTTP cases pass separately, including stale/tampered/foreign-owner safeguards and isolated Production withholding; they do not qualify a model. The Linux-engine pipe remains unavailable and optional loopback health/inventory probes timed out; no new Docker recovery was attempted or deployed target established. The candidate's Production block remains active. Connor's latest instruction schedules deployment for the **release-candidate decision after P5-15**, superseding the historical release-first ordering below. No later slice, production merge or deployment begins in this checkpoint; F04/current backup-restore/configuration/rollback/protected-CI proof remains separately required.
+
 Local configuration selects Ollama `qwen2.5:7b`; actual deployed provider/model/digest/settings remain unverified. Docker Desktop is blocked while starting its inference manager by an AF_UNIX socket reparse-point (`IO_REPARSE_TAG_AF_UNIX`) that cannot be removed/opened normally (Windows error 1920). The deeper filesystem cause remains unknown. No destructive recovery was attempted; the failed bounded rename and supported Model Runner disable/start attempts remain documented. Do not spend another checkpoint retrying Docker recovery or repeat recovery attempts during unrelated phases.
 
 The frozen qualification corpus contains **32 synthetic cases**. Required calls remain **366**; completed calls **0**, human reviews **0**, and critical factuality failures **unmeasured**. Zero runs cannot establish factuality. Deterministic grounding/proposal, ownership, source freshness and revision/history protections are implemented and passing independently; [fresh release-candidate regression results](release-readiness/README.md#local-validation-and-preservation) remain separate from configured-model semantic qualification. **The P5-13 AI review UI remains unimplemented.** Retain the frozen [corpus](p5-13-semantic-qualification/corpus.json), [rubric](p5-13-semantic-qualification/RUBRIC.md), [qualification results](p5-13-semantic-qualification/qualification-results.json), [initial environment evidence](p5-13-semantic-qualification/environment-checkpoint.json) and [recovery evidence](p5-13-semantic-qualification/environment-recovery-checkpoint.json), including failed observations.
@@ -67,7 +69,7 @@ Before marking P5-13 complete:
 6. Implement and validate the P5-13 AI review UI against its retained source/target, compare/edit/accept/reject/regenerate/error/locked, keyboard, theme/locale and mobile requirements.
 7. Repeat relevant regression testing, preserving deterministic AI protections, ownership/privacy, revision/history, source isolation, rendering/PDF and affected workflow/accessibility contracts.
 
-**Authorized continuation scope:** prepare and verify the completed redesign's release to the actual production branch, **`main`**, first, subject to every production/release gate. Repository inspection identifies [the configured `main` CI/deployment workflow](../../../.gitea/workflows/ci-deploy.yml); a `main` push triggers automatic production deployment, so merge/push remains **NO-GO pending production safety proof**, including F04 ingress and backup/restore/rollback evidence. The requested `master` wording does not override the instruction to determine the actual configured branch. Only after successful release verification may a new development branch from updated `main` continue **P5-14 for currently implemented CV capabilities**: desktop/tablet/mobile editor-preview switching, section editing/navigation, Career Profile source/override clarity, save/conflict recovery, keyboard/pointer/touch, document controls, preview scroll/zoom, PDF fidelity, accessibility and localisation. This is a conditional scope clarification; the [historical P5-14 requirement](PHASE5_PLAN.md#p5-14--responsive-cv-workflow-checkpoint) for accepted 09–13 and a complete AI-review journey remains recorded. Do not fabricate an AI-review workflow, claim deferred P5-13-specific responsiveness passed, or remove the existing automated AI protection tests. Carry that missing coverage into P5-14 acceptance explicitly.
+**Historical continuation scope, superseded by the latest qualification instruction above:** prepare and verify the completed redesign's release to the actual production branch, **`main`**, first, subject to every production/release gate. Repository inspection identifies [the configured `main` CI/deployment workflow](../../../.gitea/workflows/ci-deploy.yml); a `main` push triggers automatic production deployment, so merge/push remains **NO-GO pending production safety proof**, including F04 ingress and backup/restore/rollback evidence. The requested `master` wording does not override the instruction to determine the actual configured branch. Only after successful release verification may a new development branch from updated `main` continue **P5-14 for currently implemented CV capabilities**: desktop/tablet/mobile editor-preview switching, section editing/navigation, Career Profile source/override clarity, save/conflict recovery, keyboard/pointer/touch, document controls, preview scroll/zoom, PDF fidelity, accessibility and localisation. This is a conditional scope clarification; the [historical P5-14 requirement](PHASE5_PLAN.md#p5-14--responsive-cv-workflow-checkpoint) for accepted 09–13 and a complete AI-review journey remains recorded. Do not fabricate an AI-review workflow, claim deferred P5-13-specific responsiveness passed, or remove the existing automated AI protection tests. Carry that missing coverage into P5-14 acceptance explicitly.
 
 P5-15 must carry this debt and distinguish completed/verified capabilities, explicitly deferred capabilities, production-release blockers and non-blocking limitations. Full Phase 5 acceptance remains conditional/partial while mandatory retained requirements are unmet; no unconditional GO without an explicit documented authorization revising the full acceptance scope. The release/P5-14 clarification does not waive F04, release safety, human accessibility acceptance or unrelated debt. Preserve Connor's requirement to **push every individual P5-15 change/checkpoint**; outside P5-15, commit and push at each phase end. No release or deployment success is asserted by this register update.