@thomasminh1995/depverdict 0.6.0-alpha.1

package/docs/RR02-FIX-05-Materialize-Persisted-Qualification.md

@@ -0,0 +1,207 @@
+# RR02-FIX-05 — Materialize Persisted Real-provider Qualification
+
+## 1. Executive Verdict
+
+**`QUALIFICATION_MATERIALIZED_AND_RELEASE_GATES_PASS`**
+
+v0.5.0 readiness: **`GO_V0_5_0_WITH_NON_BLOCKING_UX_FOLLOWUPS`**.
+Migration Checklist default enablement: **`KEEP_EXPERIMENTAL`**.
+
+## 2. Why Materialization Was Required
+
+RR02-RERUN proved the packaged FIX-04 heartbeat, cancellation, package and UX
+gates, but stopped at `BLOCKED_BY_QUALIFICATION_INPUT`. Markdown evidence was
+correctly rejected as runtime input. FIX-05 located the original structured
+RR-01-RERUN evaluation and projected its unchanged qualification through the
+supported atomic writer.
+
+## 3. Source Search and Provenance
+
+Search was limited to repository artifacts, report-referenced RR-01 outputs
+and scoped temporary RR-01 acceptance locations that were not retained.
+
+| Candidate source | Machine-readable | Runtime mode | Identity match | Verdict | Selected |
+| --- | --- | --- | --- | --- | --- |
+| `rr01-real-migration-evaluation.json` | Full v1 report | real | No, v1 task | `NOT_QUALIFIED` | No |
+| `upgradelens-rr01-rerun-real-evaluation.json` | Full v2 report | real | Exact | `QUALIFIED` | Yes |
+| RR-01 controlled/VinGrade result JSON files | ID/transcript only | real | Not independently validatable | N/A | No |
+| RR-01 Markdown reports | Prose only | N/A | Rejected | N/A | No |
+
+Selected source provenance:
+
+- artifact ID: `upgradelens-rr01-rerun-real-evaluation.json`;
+- source bytes: 118,466;
+- source SHA-256:
+  `09fa990a934135ca94efc5ff4387c286fd52ad2d9199285f135ddb24810aa376`;
+- qualification-object canonical SHA-256:
+  `05613e763f7a972942761ad68a10ed976ce9e7cd5a9a296fc8a2abc94fc57b68`;
+- generatedAt: `2026-07-17T03:32:16.710Z`;
+- original provider requests: 7;
+- source mutated before writer projection: **NO**.
+
+Only the selected file contained the complete strict qualification object.
+Other files containing the same ID were pipeline observations, not competing
+qualification sources.
+
+## 4. Current Identity
+
+- task: `migration-planning.v2`;
+- dataset: `migration-planning-golden@2.0.0`;
+- dataset digest: `sha256:c15089381612671c62c3b565d93ad4f5dff1705317ee9622d9ee12a68028d407`;
+- criteria: `migration-action-evaluation@1.0.0`;
+- criteria digest: `sha256:3e2d7c3e32794d2acb59fb834609806e7700cc6888780ffd3d26d1f106078ccc`;
+- comparator/normalization: `2.0.0` / `1.0.0`;
+- policy: `3.0.0`,
+  `sha256:b463a30d8044aed5aa8565fc08824b9f430145527da35142e452c3dad544c747`;
+- prompt: `2`,
+  `sha256:68c227c7951cd9ad6e60283fc9d54416f7c7e76ebaaa85ce17acfe30252cfdd2`;
+- candidate schema:
+  `sha256:6ac9e1477e206ab082ac38cdb263254c996ee4684e04c80af6b9a08ceae0375d`;
+- trust: `migration-checklist-trust.extractive.v2`;
+- presentation: `migration-checklist-extractive-presentation.v1`;
+- runtime: real / `openai-compatible` / `openai/gpt-5.5` /
+  `openai-compatible`;
+- qualification identity:
+  `sha256:4fa4954d6f254d94859bce17aec6209394d380e4635155a6f3ce23a7e9b70765`.
+
+## 5. Original Qualification Validation
+
+Current authoritative code recomputed the qualification from the full
+structured dataset, metrics and runtime report. The recomputed qualification
+was canonically identical to the source object:
+
+- strict v2 schema: pass;
+- real runtime and observed identity: pass;
+- 19/19 thresholds: pass;
+- 15/15 critical gates: pass;
+- coverage/verdict invariants: pass;
+- failed thresholds/gates: 0/0;
+- source limitations: 0;
+- secret/raw-payload prohibited keys: 0;
+- verdict: `QUALIFIED`.
+
+No provider was called and no field, digest, policy or verdict was edited.
+
+## 6. Persisted Record Materialization
+
+The public `writeMigrationPlanningQualificationRecord` API wrote:
+
+`.upgradelens/migration-planning-qualification.json`
+
+- permissions: `0600`;
+- bytes: 9,622;
+- record digest:
+  `sha256:e55b2d6f2f82091f5ce321e3e6b3a36cab8a34ea7608464ccd08b8ef49813847`;
+- file SHA-256:
+  `7891afabc6979ab3f362cbdd7c312daacf84595e12a49150c709eda8e477aa69`;
+- qualification ID preserved exactly;
+- writer serialization/read-back exact;
+- destination is ignored by `.gitignore`.
+
+## 7. Record Integrity and Resolution
+
+Production loader, resolver and guard confirmed:
+
+- strict envelope and record digest;
+- embedded qualification identity digest;
+- default path relative to target root;
+- `status: QUALIFIED`;
+- `executionAllowed: true`;
+- `experimentalOverrideUsed: false`;
+- immutable decision;
+- default and explicit source remain single-source decisions.
+
+Focused coverage proves once-per-run resolution, writer determinism,
+idempotence, invalid-source non-overwrite, manual-mutation corruption,
+default analyze isolation and presentation consistency.
+
+## 8. Qualification-dependent Scenario Matrix
+
+| Scenario | Source | Status | Execution | Provider calls | Exit | Surface consistency | Capture |
+| --- | --- | --- | --- | ---: | ---: | --- | --- |
+| RERUN-006 | default path | `QUALIFIED` | Allowed, 0/0 contexts | 0 | 0 | Guard/progress/console/Markdown pass | `003-*` |
+| RERUN-007 | `config/qualification.json` | `QUALIFIED` | Allowed, no fallback | 0 | 0 | Pass | `004-*` |
+| RERUN-008 | absent | `MISSING` | Experimental only | 0 | 0 | No qualified claim | `005-*` |
+| RERUN-009 | explicit valid mismatch | `IDENTITY_MISMATCH` | Blocked | 0 | 1 | Constrained | `006-*` |
+| RERUN-010 | tampered digest | `CORRUPTED` | Blocked | 0 | 1 | Constrained | `007-*` |
+| RERUN-011 | matching strict fixture | `NOT_QUALIFIED` | Blocked | 0 | 1 | Override did not bypass | `008-*` |
+
+Negative fixtures were generated with authoritative qualification/writer APIs;
+only the corruption scenario intentionally mutated its isolated temporary
+record.
+
+## 9. Provider Request Counts
+
+New provider requests: **0**. Qualified runs had zero eligible contexts and
+preserved lazy provider initialization. All negative scenarios blocked before
+context/provider construction. No requalification occurred.
+
+## 10. CLI Capture Evidence
+
+`docs/rr02-fix-05-cli-captures/manifest.json` contains eight invocations and
+11 screenshots. Every invocation has command, environment, raw/clean
+transcript, metadata, exit code and final screen. RERUN-006 additionally has
+start/progress/final evidence.
+
+## 11. Regression and Package Results
+
+- focused qualification/progress/cooperative/orchestration: 68/68 pass;
+- MP-01–MP-05 and Extractive regressions: 74/74 pass;
+- canonical parallel attempt 1: 544 pass, 1 lifecycle `SIGKILL` flake,
+  1 sandbox-only skip;
+- isolated lifecycle reproduction: 1/1 pass;
+- canonical parallel attempt 2: 545 pass, 0 fail, 1 sandbox-only skip;
+- serial suite: 545 pass, 0 fail, 1 sandbox-only skip;
+- package guard before report: 207 files, 0 captures, 15/15 required assets;
+- final dry-run/package guard after report: 208 files, 0 captures, 15/15
+  required assets;
+- fresh tarball: `upgradelens@0.4.0`, SHA-256
+  `c3a5648a15ddcddb752b930b2d581163964cd2c26af51c418fb9ca7906411919`;
+- offline clean install: 12 packages; public version/help/import pass.
+
+The first canonical failure is retained and is not replaced silently by the
+retry or serial pass. No timeout or test infrastructure changed.
+
+## 12. Privacy and Repository Policy
+
+The persisted record contains no key, token, authorization header, raw
+provider request/response, raw candidate/error payload, endpoint or private
+reasoning. It is generated output, ignored by Git, not committed and excluded
+from npm. The package retains only the public record schema/docs. Capture
+trees and helpers are absent from the tarball.
+
+## 13. Files Changed
+
+- generated, Git-ignored:
+  `.upgradelens/migration-planning-qualification.json`;
+- added: this report;
+- added: `docs/rr02-fix-05-cli-captures/**`;
+- canonical RR02-RERUN report receives a qualification-completion attempt
+  note.
+
+Pre-existing RR02-RERUN evidence changes were preserved.
+
+## 14. Remaining Limitations
+
+- Migration Checklist remains experimental and requires human review.
+- The known narrow-terminal detail truncation is a non-blocking UX follow-up.
+- Parallel lifecycle timing remains load-sensitive; isolated, canonical retry
+  and serial runs passed.
+- The sandbox-only local-loopback case is not counted as a pass.
+
+## 15. Release Decision
+
+v0.5.0: **`GO_V0_5_0_WITH_NON_BLOCKING_UX_FOLLOWUPS`**.
+
+Migration Checklist: **`KEEP_EXPERIMENTAL`**.
+
+The only next task is **v0.5.0 Release Execution Checklist**. This task did
+not release, tag, publish or bump the package.
+
+## 16. Scope Confirmation
+
+No production/test/fixture/package source, evaluation identity, dataset,
+criteria, comparator, normalization, policy, prompt, schema, trust,
+generator, progress, scheduler, timeout or version changed. The source was
+not reconstructed from Markdown and no provider requalification ran. Nothing
+was staged, committed, pushed, tagged or published.

package/docs/RR02-RERUN-CLI-Qualification-Progress-UX-and-Package-Validation.md

@@ -0,0 +1,342 @@
+# RR02-RERUN — After FIX-04 CLI Qualification, Progress and Package Validation
+
+## 1. Executive Verdict
+
+Final v0.5.0 verdict: **`BLOCKED_BY_QUALIFICATION_INPUT`**.
+
+The committed FIX-04 snapshot passed focused preflight, fresh packaging,
+offline clean installation, public import/version/help, default TTY/plain/CI
+workflows, the production CPU-bound heartbeat gate, cancellation, controlled
+failure, normalized artifact equivalence, canonical parallel regression, and
+the separately executed serial suite.
+
+A persisted real-provider Migration Planning qualification record was not
+available through either supported source. The validation did not synthesize,
+copy, repair, or reconstruct one from prose. RERUN-006 and RERUN-007 therefore
+could not establish the required exact identity and integrity evidence, and a
+release GO is not permitted.
+
+Migration Checklist default-enablement decision: **`KEEP_EXPERIMENTAL`**.
+
+## 2. Committed Snapshot Precondition
+
+- Branch: `feat/mvp-05-evidence-migration-checklist`
+- HEAD: `44eb942e21ea78550700990a00bd74635ce48bcc`
+- Subject: `fix: event-loop starvation`
+- Expected pre-FIX-04 baseline: `a24899dee1714c8b6f7c20cd9a129e9e80a97261`
+- Initial index: clean
+- Initial worktree: clean
+- Initial untracked files: none
+
+Committed-tree inspection confirmed:
+
+- `src/cooperative-scheduler.js` is present;
+- Discovery and Usage import and call the scheduler at safe boundaries;
+- abort checks are part of the committed scheduler integration;
+- `test/cooperative-scheduling.test.js` is present;
+- the package contains the scheduler module;
+- `package.json` retains `!docs/*-cli-captures`.
+
+All post-preflight product evidence used this exact committed HEAD.
+
+## 3. Why This Rerun Was Required
+
+The prior RR02-RERUN on `a24899d` stopped at RERUN-005 with
+`NO_GO_QUALIFICATION_OR_PROGRESS`: a CPU-bound Usage stage was quiet for 8.4
+seconds and did not allow the five-second heartbeat timer to run. FIX-04 added
+event-loop-safe cooperative scheduling. Its remediation evidence was not
+itself a release verdict, so this run restarted with a new tarball at
+RERUN-001.
+
+Historical evidence remains in capture sequences 001–007 and retains the old
+no-go verdict. The current attempt is sequences 008–018.
+
+## 4. Environment and Fresh Package Identity
+
+- Package: `upgradelens@0.4.0`
+- Platform: macOS arm64
+- Node: `v26.0.0`
+- Fresh isolated validation root: yes
+- Fresh UpgradeLens tarball: yes; no prior UpgradeLens tarball reused
+- Clean install: offline, isolated consumer, exact local dependency tarballs
+- Installed packages: 12
+- Public package import: passed; 408 exports observed
+- Provider requests: 0
+
+Installed/exercised tarball:
+
+- file count: 207;
+- compressed size: 491,143 bytes;
+- unpacked size: 1,940,721 bytes;
+- npm SHA-1: `c8277090a5d8996b3a46c1ef4284cbee3e1534d4`;
+- SHA-256:
+  `72ee68a2d06c8a2b9f226a006a73851ac3c595db68783abaccd889924b74cb1c`.
+
+The first isolated-cache install correctly returned `ENOTCACHED`. A new
+consumer was then installed offline with the exact local dependency tarballs;
+the UpgradeLens tarball itself remained the newly packed HEAD artifact.
+
+## 5. Qualification Input and Identity Check
+
+No `migration-planning-qualification.json` exists in the repository default
+location, under the available Desktop repositories, or under the available
+temporary validation roots. No supported relative override was supplied.
+
+Consequences:
+
+- strict schema, record integrity, and exact real-provider identity could not
+  be established for RERUN-006;
+- the relative override path could not be exercised with a real persisted
+  record in RERUN-007;
+- identity mismatch/corruption/`NOT_QUALIFIED` product scenarios were not
+  manufactured from test data;
+- no provider was constructed or called.
+
+RERUN-008 independently confirmed that an actually missing default record is
+presented as `MISSING`, source `defaultPath`, qualification ID `none`, and
+experimental override `YES`. It was never presented as qualified.
+
+## 6. Preflight Results
+
+| Gate | Result |
+| --- | --- |
+| Scheduler, Discovery, Usage, progress, orchestration and CLI | 45 passed, 0 failed |
+| Qualification resolver/guard and Migration Checklist runtime | 75 passed, 0 failed |
+| MP, duplicate occurrence, governance and Extractive Contract v2 | 75 passed, 0 failed |
+| Package content guard before matrix | 207 files, 0 captures, 15/15 required assets |
+| Committed snapshot | Clean and newer than `a24899d` |
+
+No focused non-sandbox failure occurred.
+
+## 7. Scenario Matrix
+
+| Scenario | Packaged CLI | Qualification | Mode | Duration | Heartbeats | Exit | Provider calls | Result | Capture |
+| --- | --- | --- | --- | ---: | ---: | ---: | ---: | --- | --- |
+| RERUN-001 version | Yes | N/A | non-TTY | 1.1s | 0 | 0 | 0 | Pass | `008-...-version` |
+| RERUN-001 help | Yes | N/A | non-TTY | 0.6s | 0 | 0 | 0 | Pass | `009-...-help` |
+| RERUN-002 default auto | Yes | Not resolved by design | TTY interactive | 0.8s | 0 | 0 | 0 | Pass, seven stages | `010-...-default-tty-auto` |
+| RERUN-003 default auto | Yes | Not resolved by design | non-TTY plain | 1.4s | 0 | 0 | 0 | Pass | `011-...-default-nontty-auto` |
+| RERUN-004 explicit plain | Yes | Not resolved by design | 80-column PTY | 0.8s | 0 | 0 | 0 | Pass | `012-...-plain-tty` |
+| RERUN-005 CPU heartbeat | Yes | Not resolved | TTY interactive | 22.1s total; Usage 16.0s | 3 | 0 | 0 | **Pass** | `013-...-cpu-heartbeat` |
+| RERUN-006 persisted qualified | No | Record unavailable | N/A | N/A | N/A | N/A | 0 | Blocked by input | manifest |
+| RERUN-007 relative override | No | Record unavailable | N/A | N/A | N/A | N/A | 0 | Blocked by input | manifest |
+| RERUN-008 missing | Yes | `MISSING` | non-TTY plain | 1.0s | 0 | 0 | 0 | Pass | `014-...-missing-qualification` |
+| RERUN-009 mismatch | No | No persisted fixture authorized | N/A | N/A | N/A | N/A | 0 | Not manufactured | manifest |
+| RERUN-010 corrupted | No | No persisted fixture authorized | N/A | N/A | N/A | N/A | 0 | Not manufactured | manifest |
+| RERUN-011 `NOT_QUALIFIED` | No | No persisted fixture authorized | N/A | N/A | N/A | N/A | 0 | Not manufactured | manifest |
+| RERUN-012 cancellation | Yes | N/A | non-TTY plain | 5.8s total | 0 | 130 | 0 | Pass | `015-...-usage-cancellation` |
+| RERUN-013 fatal failure | Yes | N/A | non-TTY plain | 0.6s | 0 | 1 | 0 | Pass | `016-...-fatal-stage-failure` |
+| RERUN-014 CI-like | Yes | Not resolved by design | non-TTY/no color | 0.7s | 0 | 0 | 0 | Pass | `017-...-ci-like` |
+| Artifact repeat | Yes | Not resolved by design | non-TTY plain | 0.8s | 0 | 0 | 0 | Pass | `018-artifact-determinism-repeat` |
+| RERUN-015 final package | Tar inspection | N/A | N/A | N/A | N/A | N/A | 0 | Pass | this report |
+
+## 8. CPU-bound Heartbeat Evidence
+
+The clean-installed public binary ran the controlled 60,000-file workload
+using the production five-second threshold:
+
+```text
+Repository Usage Discovery — Scanning supported source files [0.0s]
+Repository Usage Discovery — Scanning supported source files [5.0s]
+Repository Usage Discovery — Scanning supported source files [10.0s]
+Repository Usage Discovery — Scanning supported source files [15.0s]
+Repository Usage Discovery — Writing Repository Usage Index [16.0s]
+Repository Usage Discovery completed [16.0s]
+```
+
+The three heartbeat records occur after the quiet threshold and before the
+terminal record. Elapsed values are monotonic. There is no percentage, ETA,
+token stream, model-thinking claim, scanner-forged heartbeat, or heartbeat
+after terminal state.
+
+## 9. Qualification Consistency Results
+
+- Default analysis ran seven stages and did not resolve qualification.
+- Default analysis did not schedule Migration Checklist.
+- Missing qualification was resolved once for the experimental run and was
+  consistently shown as `MISSING`.
+- Console output reported source, path, ID and override state without claiming
+  qualification.
+- The experimental missing-record policy completed with mandatory review and
+  zero eligible contexts/provider calls.
+- Focused tests passed persisted `QUALIFIED`, mismatch, corruption,
+  `NOT_QUALIFIED`, one-source, immutable-decision and zero-provider-call
+  contracts.
+
+Focused tests are not substituted for the missing packaged real-provider
+record. That distinction is the release blocker.
+
+## 10. Cancellation and Failure Results
+
+RERUN-012 sent the first `SIGINT` after Usage emitted
+`SCAN_SUPPORTED_SOURCE`. Usage reached `STAGE CANCELLED` at 0.1 seconds of that
+stage, the run exited 130, later stages were absent, no success summary was
+printed, and `.upgradelens/usage-index.json` was absent.
+
+RERUN-013 passed a file where a repository directory was required. Project
+Discovery emitted one constrained `STAGE FAILED`, the run emitted
+`completed=0/7 next=REVIEW_FAILURE_DETAILS`, exited 1, and did not schedule
+later stages or print a success summary. No raw stack was exposed.
+
+## 11. Artifact Determinism
+
+The same packaged command was repeated against the same target. Project
+Manifest, Usage Index, Repository Impact and Repository Impact Evidence were
+equivalent after removing only runtime timestamps and the exact-byte lineage
+digests that necessarily change when those timestamps change. All dependency,
+symbol, file, finding, evidence, ordering, IDs, statuses and presentation data
+were identical.
+
+The committed cooperative test independently proves exact-byte equality with
+fixed clocks for yield-disabled, yield-enabled and alternate batch policies.
+
+## 12. CLI Capture Inventory
+
+- Historical invocations retained: 7
+- Current attempt invocations: 11
+- Total manifest entries: 18
+- Current sequences: 008–018
+- Current final screens: 11/11
+- Current additional progress screens: 9
+- Missing final screens: 0
+- Raw transcripts: 18
+- Clean transcripts: 18
+- Real-provider requests: 0
+- Sanitization failures: 0
+
+The stable-sorted manifest is
+`docs/rr02-rerun-cli-captures/manifest.json`. Every new UpgradeLens CLI
+invocation has command, environment, raw/clean transcript, metadata, exit
+code, and final screen. TTY scenarios used a real PTY; non-TTY images were
+rendered from their actual transcripts.
+
+## 13. UX Scorecard
+
+| Criterion | Score | Evidence |
+| --- | ---: | --- |
+| Current activity | 2 | RERUN-002 and RERUN-005 |
+| Meaningful detail | 2 | Stable stage/activity labels |
+| Elapsed time | 2 | 5/10/15-second production heartbeats |
+| Completed history | 2 | Interactive and plain lifecycle trails |
+| Warnings in context | 1 | Missing qualification is contextual; limited warning variety |
+| Final summary | 2 | Default TTY, plain and CI |
+| Visual stability | 2 | Append-only; no cursor rewrite |
+| TTY awareness | 2 | Auto interactive versus auto plain |
+| Honest progress | 2 | No invented percentage, ETA, retry or thinking |
+| Failure recovery | 2 | Cancellation and fatal failure captures |
+| **Total** | **19/20** | UX release target met |
+
+The historical Medium 80-column detail-truncation limitation remains a
+non-blocking follow-up. It was not changed or used to alter this validation.
+
+## 14. Package Contents and Clean Install
+
+The exercised tarball contained the committed scheduler and all 15
+authoritative runtime/schema/dataset/documentation assets. Inspection and the
+package guard found:
+
+- 207 files;
+- zero `docs/*-cli-captures` entries;
+- zero capture helper entries;
+- all 15 required assets;
+- executable CLI and public runtime present;
+- clean offline install and public import passed.
+- `npm pack --dry-run --json` passed with the isolated validation cache.
+
+An initial dry-run without the isolated-cache argument hit the host's
+root-owned default npm cache (`EPERM`). The required rerun with the isolated
+validation cache passed; this was an environment permission issue, not a
+package-content failure.
+
+RERUN capture trees, FIX-04 capture trees, PNGs, transcripts and temporary
+capture helpers are absent from the package.
+
+Fresh RERUN-015 tarball created after the report/capture tree existed:
+
+- file count: 207;
+- compressed size: 491,159 bytes;
+- unpacked size: 1,940,925 bytes;
+- npm SHA-1: `97fca29e73ee63d806857deca9c3d38a8e5b31c0`;
+- SHA-256:
+  `dff64ad860a346e3d5c5db76c9102941779c50fd6e2c07df3d18dbc438f43746`.
+
+## 15. Canonical and Serial Regression Results
+
+Canonical parallel `npm run check`:
+
+- 546 tests;
+- 545 passed;
+- 0 failed;
+- 1 known sandbox-only local-loopback skip;
+- package guard passed with 207 files, zero captures and 15/15 assets.
+
+Separate serial `npm test -- --test-concurrency=1`:
+
+- 546 tests;
+- 545 passed;
+- 0 failed;
+- 1 known sandbox-only local-loopback skip.
+
+The serial pass is reported separately and is not a replacement for the
+canonical result. The canonical parallel run passed on its first attempt.
+
+## 16. Defects and Remaining Limitations
+
+### Release blocker — persisted qualification input unavailable
+
+The exact real-provider qualification record required by RERUN-006/007 is not
+available. This is an evidence-input blocker, not an inferred
+`NOT_QUALIFIED` result and not identity drift.
+
+### Non-blocking technical debt
+
+1. Migration Checklist remains experimental and requires a separate
+   default-enablement review.
+2. Narrow 80-column activity detail may truncate while stage and elapsed
+   identity remain readable.
+3. The local-loopback lifecycle case is skipped by this sandbox and is not
+   counted as a pass.
+4. Runtime-generated timestamps intentionally alter exact bytes and downstream
+   exact-byte lineage between separate CLI runs; fixed-clock tests retain the
+   exact deterministic contract.
+
+## 17. Release Decision
+
+**v0.5.0 readiness: `BLOCKED_BY_QUALIFICATION_INPUT`.**
+
+The FIX-04 heartbeat remediation is release-ready on the observed packaged
+workflows. Package, progress, cancellation, failure, deterministic contract,
+and regressions do not block this candidate. Release GO remains prohibited
+until the existing real-provider qualification record is materialized through
+the supported persisted contract and exact identity/integrity can be checked.
+
+**Migration Checklist default enablement: `KEEP_EXPERIMENTAL`.**
+
+Next task: materialize/persist the existing qualified record without
+reconstructing it from prose, then rerun only the qualification-dependent
+release gates before a v0.5.0 Release Execution Checklist.
+
+## 18. Scope Confirmation
+
+- No production, test, fixture, package, qualification, dataset, policy,
+  prompt, schema, trust, generator, or VinGrade file was changed.
+- No lifecycle timeout, heartbeat interval, yield policy, expected transcript,
+  or test infrastructure was changed.
+- No record was synthesized, repaired or requalified.
+- No old UpgradeLens tarball was reused.
+- No network or real-provider call occurred.
+- No file was staged or committed.
+- No push, tag, publish or release occurred.
+- Only this canonical report and new canonical capture evidence changed.
+- Migration Checklist remains experimental.
+
+## FIX-05 Qualification Completion Attempt
+
+FIX-05 located the original machine-readable RR-01-RERUN real-provider
+evaluation, validated its complete v2 qualification against current identity,
+and materialized the unchanged `QUALIFIED` object through the supported atomic
+writer. Packaged RERUN-006 through RERUN-011 passed with zero new provider
+requests. Final decision is now
+`GO_V0_5_0_WITH_NON_BLOCKING_UX_FOLLOWUPS`; Migration Checklist remains
+`KEEP_EXPERIMENTAL`. Full evidence is in
+`RR02-FIX-05-Materialize-Persisted-Qualification.md`.