CC[100]'s command audit (AUDIT-COMMANDS-08-21-26.md, referenced via FINAL_CLOSE msg 1119) found that PLATFORM_CHECK.php's gov-file-freshness check (##6) built handoff file paths from a hand-rolled $sys_dirs map pairing each real directory with its OLD, RETIRED single-digit code (00-admin=>00, 10-master=>01, 20-builder=>02 ... 95-travel=>10) instead of the decade suffix every real handoff file has used since the platform-wide migration. Concretely this meant the check was reading handoff-01.md for Master, handoff-02.md for Builder, etc -- the deprecated code-suffixed stub files explicitly marked DO NOT WRITE HERE -- not the real, actively-updated decade-suffix handoff files. Only 00-admin worked, because its retired code and decade code are both 00 by coincidence. This is the platform's only 72h handoff-staleness alarm and it had been silently checking 1 of 11 systems since whenever this map was written. Same root-cause class CHECKPOINT.php already fixed on 08/07/26 (K274) per SOP-COMMAND-BUILD.md's rule 1 (never hand-roll system identity, always use roster_lib.php's build_roster()) -- used that exact pattern here. Also note the old map contained '95-travel'=>'10' -- the exact 10 trap SOP-COMMAND-BUILD.md warns about (retired code 10 was Travel, a dangerous collision with decade 10/Master if it ever leaked into anything keyed by decade). SEPARATE BUG FOUND AND FIXED IN THE SAME FILE, SAME SESSION: a few lines later, the AUTO DASHBOARD PING block read $decade (a variable left over from the now-fixed foreach loop above it -- after the loop ends $decade holds whatever the LAST roster entry happened to be, e.g. Travel or CC, not the actual caller) instead of $caller_decade (the real request parameter already parsed at the top of the file). This meant PLATFORM_CHECK's own dashboard ping was silently misreporting which system it ran for, every single call, regardless of who called it. Fixed to use $caller_decade/$caller_system, the variables the file itself already defines for this exact purpose.