not-found-classify: down-tier sourcemap (*.js.map/*.css.map) 404s to silent - /sw.js.map flooding warn x294

applog-pluto 2026-07-04 07:20: 294 warn page_not_found in one digest, single signature /sw.js.map. INVESTIGATED: Pluto serves public/sw.js (5-line service worker, registered navigator.serviceWorker.register in src/app/layout.tsx:75). sw.js has NO sourceMappingURL comment and there is NO public/sw.js.map file -> the 404 is browser/devtools (or a sourcemap-harvesting client) speculatively fetching the SW sourcemap, not a broken app reference. Harmless (correct 404) but 294 warn events = heavy noise on the zero-noise baseline. FIX: in src/lib/not-found-classify.ts add a sourcemap classifier that down-tiers compiled-asset sourcemap 404s warn/page -> silent info/security. Anchor the ext family at path-end, boundary-terminated same style as block M: suggest ((\.(?:js|mjs|cjs|css)\.map)(?:$|[?#])). Covers /sw.js.map + any future chunk .map. Collision-proof: Pluto serves ZERO .map assets (public/ has none) and no Next route ends in .map -> zero false-silence risk. Verify 0/66-template + zero-public-asset like block M. Not Class-A (telemetry). PTD via audit-pluto-cc keyed to sha (version signal cosmetic). mem: pluto-scanner-probe-canonical. NOTE: a sourcemap 404 is generically never a user nav error, so this is a correct classification, not just noise suppression - fleet-portable to mars/venus.