chore(spec-drift): regenerate the SAK dashboard after the promotion branch advanced its lineage coverage map

`Validate specs and docs` failed on this branch with
"render-sak-dashboard --check: STALE". The dashboard is a DERIVED view whose
inputs include specs/lineage/coverage-map.json, and this branch's tier-2
promotions advanced that map — so the committed dashboard no longer matched a
fresh derivation. The gate did exactly its job.

Regenerated with --now 2026-07-23T00:18:54Z rather than wall-clock, matching the
evaluated_at already used for detector-health in the previous commit, so both
derived dashboards on this branch carry the same run's timestamp instead of
"whenever a human happened to rebuild them".

Delta is the generated_at stamp plus the coverage-map input hash; disposition is
unchanged at CONTINUE (0/12 indicators firing).

Verified: render-sak-dashboard --check OK; --self-test sound (disposition matrix,
coverage derivation, determinism, freshness failure modes); detector-health
--check still OK; audit-harness verify OK.

Author: jeremylongshore

SAK-DASHBOARD.md

@@ -1,6 +1,6 @@
 <!-- GENERATED-DO-NOT-EDIT — SAK dashboard derived from committed state (SAK-STATE.json + leading-indicators registry + lineage coverage map). Regenerate: python3 scripts/render-sak-dashboard.py. Normative spec: 000-docs/033-PP-PLAN-skill-refiner-sak-amendment-v7-2026-05-28.md § 14.13.1 -->
 
-# SAK Dashboard — generated 2026-07-07T05:10:25Z
+# SAK Dashboard — generated 2026-07-23T00:18:54Z
 
 State as of 2026-06-20. This file is DERIVED — never hand-edit it.
 

specs/sak-dashboard.json

@@ -188,11 +188,11 @@
     "surfaces_total": 16
   },
   "dashboard_version": "sak-dashboard/v1",
-  "generated_at": "2026-07-07T05:10:25Z",
+  "generated_at": "2026-07-23T00:18:54Z",
   "inputs": {
     "SAK-STATE.json": "8f0c009bb43b7175fcc97521095a2f887df72232ed203156fbeb6a496f32b27d",
     "specs/leading-indicators.v1.json": "4bcb1549ded6bf02d043a81d122c02d36538221e508340bdc1d061994cef4f67",
-    "specs/lineage/coverage-map.json": "d416ae6cc04f55b9cc10fc44641e9cd71210fca977f378c513df5bed518a1aee"
+    "specs/lineage/coverage-map.json": "51b0a816961ed34b3b97676dbb07be40dd4ab19adad921b531129a0d78c40498"
   },
   "leading_indicators": {
     "action": "Continue per plan",