RR-20: retain complete graph serial staged qualification

[michaeljgrimm]

Retain the complete 0.19 source graph, six staged artifact manifests and the serial packed, installed, global/npm-exec and browser qualification logs. The evidence records the packed-smoke rebuild race and its reviewed repair, preserving the failed attempt as diagnostic evidence.

All five serial consumers passed, and the supervisor independently verified that all six artifact hashes and sizes were unchanged. Registry adoption, release metadata, cross-platform and engines-range checks, and native PowerPoint acceptance remain separate.

Validation: after integrating main at 080da598, pnpm check:changed and full pnpm test passed, including all 36 root checks. The 17 evidence files are byte-identical to the previously reviewed evidence head. This PR targets main after prerequisite #604 merged; it changes no runtime code, dependencies, versions, locks, goldens or tolerances.

---

Note

Low Risk
Documentation and qualification logs only; no application code, dependencies, versions, or test baselines change in this PR.

Overview
Adds RR-20 complete-graph serial staged qualification under docs/evidence/rr20-complete-graph-serial/: a README, pinned source/replay SHAs (result.json), per-package commit/scope notes, and full logs for corrected build/stage plus the five serial packed consumers (core smoke, CLI standalone, CLI peers, ecosystem, browser).

The bundle documents that all consumers exited 0 against the shared six-package candidate graph, with unchanged six-tarball SHA256/size versus the prior complete-graph stage, and explicitly scopes out registry install, native Windows acceptance, version bumps, and runtime changes.

It also retains superseded-initial-enoent.log and narrative tying the parallel packed-smoke/CLI dist race to the separate #604 fix (validate candidateArtifacts before rebuilding); the corrected serial logs are marked authoritative.

^{Reviewed by Cursor Bugbot for commit e984d43. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 6ab8ee9b-af45-43c7-a437-175e45dfe94a)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 5c4d67b6-965a-45c0-bb5d-3a74df46f657)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: b0c2fefa-e4c6-4f1b-8893-204bf9ff84b8)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 5d90046f-a606-4092-a84b-54ddf3c6ebdf)