{
  "profileId": "sudx-shadcn-tailwind-v4",
  "status": "pending",
  "normativeHashes": {
    "shadcn.css": "429bbb01bc9ba5cea83069df0ed94010c2923b43578a10d1c32aaa990bd5c1bb",
    "shadcn.json": "eab36c8b93686caa8f10a1c59772352e9cca99514b63da3c2094f765d870815c",
    "sudx-tokens.css": "90dd2735036eaac7d0a76e98dd3cf91457d6bc13aa0b7de1014c8045877c7398"
  },
  "consumers": [],
  "note": "The 4.8.0 dark theme changed nine dark neutrals and the dark Clay accent, which changed sudx-tokens.css and therefore its normative hash. The drift-lp and cma-tracker proofs recorded in 4.7.0 were taken against the 4.7.0 token file and prove that release only, so this profile returns to pending rather than carrying them forward: a consumer proof is bound to the exact bytes it was taken against, and re-pointing it at bytes the consumer never rendered would be a false receipt. Those proofs remain addressable and unaltered in the frozen release at design/releases/4.7.0/assets/compatibility/shadcn-evidence.json (drift-lp@d541d324, cma-tracker@c7c7a6bd). Restoring candidate-proved requires re-rendering both consumers against the 4.8.0 foundation, regenerating their consumer-owned evidence files, and recording the new proof commits and hashes here. Until that happens no compatibility family is claimed verified for 4.8.0."
}