reports/_template.md Omits Five Dimensions Section 4 Requires and Carries One Nothing Declares #1593

AUDIT.md section 8 says to write reports/<repo>/audit.md from reports/_template.md, and the template's Dimensions table does not match what section 4 requires. It says only "Remove rows that are N/A", so an author working from it removes rows and never adds absent ones.

Rows the template omits that AUDIT.md section 4 names as dimensions: carried-scope, runtime-secrets, dotnet-publish, hugo, verbatim-tree. The first four are declared in spec/project-types.json (carried-scope and runtime-secrets under crossCutting, dotnet-publish and hugo under types). The fifth, verbatim-tree, is bolded as a dimension in AUDIT.md section 4 but appears in neither types nor crossCutting, which is its own inconsistency worth settling in the same pass.

A row the template carries that nothing declares: console is neither a type nor a cross-cutting dimension in spec/project-types.json.

The effect is worst on carried-scope, whose remedy is a deletion. A dimension that never appears in the table is never judged, never reported, and produces no finding, so the report reads complete while the one dimension whose output is "delete these files" is silently absent from every report written from this template.

Fix belongs in reports/_template.md. Whether the table should be generated from spec/project-types.json rather than hand-maintained is the larger question behind it, since a hand-kept list of dimensions drifts from the spec exactly this way.

Surfaced by a carried-content review pass on feature/blocked-upstream-issue-rule reading AUDIT.md section 8 whole.