# Theme 1.0.1 acceptance **Published and delivery-verified, 2026-11-13. Current common adoption target:1.0.1.** 1.0.0 remains immutable and its accepted G1 pilot is historical evidence. The final package input tree matches source commit `d8d633ddb21f899bab1c958b0c62f55a98ef6d27`. Concurrent agents' unrelated changes were excluded; build/pack explicitly pin SourceRevisionId and RepositoryCommit. The earlier 5d2d953/075cf47 candidates were unpublished and superseded. Their retained logs/hashes do not identify the delivered artifacts. | Delivered artifact | SHA256 | | --- | --- | | Theme 1.0.1 nupkg | `995b117b0245577598c91404ed7957c071ebe3413696c8be48b419c9deb1bd5d` | | Technical-Light 1.0.1 static export | `ad52323416e5096e30e4b7624004274689bc2b72e1437f9e9e5d7db9f9e656e0` | The final source includes three bounded shared corrections: card-grid minimum shrinks within its column; KPI grid becomes one column below 320 px effective width; semantic `th[scope=row]` avoids column-only sticky/uppercase treatment. All 47 root token values, fonts, palette, component APIs and normal-width grid geometry remain unchanged from 1.0.0. Overview's long leader-chip wrapping stays application-owned. Observed final checks: - Theme 105/105; exporter 15/15; Overview 224/224. Zero failures/skips. - Final build 0warnings/errors. All five CSS/font payloads equal exact nupkg and Git object; all manifest hashes/provenance verified independently (`review.md`). - Actual Overview runtime serves exact package CSS and assembly1.0.1.0. Semantic row/column computed-style proof is in `actual-runtime.json`. - Actual Overview matrix: 30 state/width combinations 1440/1024/390/320/195 plus real 200%720 CSS px/DPR 2; no document overflow or page errors. Complete locally scrolling diagnostic contents intentionally extend inside their bounded region. Filter/fleet totals/clear focus, paused aging/held publication/resume latest, keyboard escaped diagnostic disclosure and reduced motion pass. See neighboring `overview-ui/browser-confirmation/results.json`, scripts and screenshots. - Exact NuGet push and generic export upload201, fresh independent GET hashes, and an isolated official-feed consumer restore all pass. No local candidate source was used for that restore; resolved library identities are unchanged. `publication.json` and `independent-feed-restore.json` substantiate delivery. No fleet-wide consumer acceptance, application deployment, G2 extraction decision or G3 completion is claimed. Every consumer adopts this exact common patch and performs its chapter checks. Human screen-reader listening and additional browser engines are separately recorded runtime limits, not fabricated passes. ## Default-cache correction A later consumer's exact HTTP CSS check detected the first unpublished candidate in the default NuGet1.0.1 cache. Root had created it during initial local canaries. Final accepted runtime/tests used isolated final-package caches and independent published-feed restore, so their bytes are unaffected. Root removed only the recognized superseded hash and refilled from the official feed; both new default package hash and source metadata match the delivered artifact. See `default-cache-correction.json`. Consumers still establish exact restored hashes; assembly version alone cannot distinguish unpublished candidates of one version.