Financial Report Layout (Proforma / Projection Dashboard) — token consolidation rationale

This component's CSS was extracted verbatim from a real, delivered WCP V2 proforma report — print-tested, genuinely production-grounded. Its companion wcp.finance.* token bundle is a separate concern: BRIEF-bencal-proforma-engine-recapitalization.md states the underlying Rust engine work (forecast_statements.rs's classic statement theme) is "planned but deliberately not yet implemented," so the statement-theme's specific values are provisional, not equally final to the dashboard theme's extracted CSS.

Why this is a separate recipe, not a variant of financial-statement-yearend

The operator's "one recipe per document family" rule keys on genuine document family, not just tone. This family and financial-statement-yearend disagree on:

• Page geometry: this family is letter landscape (1.5cm 2cm 1.5cm 1.5cm asymmetric margins); the yearend statement is letter portrait (1in symmetric). This is the sharpest divergence — they do not share a page-geometry primitive.
• Density: up to 11 period columns (label 22-25%) vs. 3 value columns (label 55%).
• Tone: tinted 3-saturation blue semantic-row fills + navy section-banner text vs. pure black-on-white, zero fills.
• Nil glyph and page-number placement: em-dash — / @bottom-right here, vs. en-dash – / @bottom-center Notes-only for the yearend statement — both deliberate per-family choices, confirmed not to be drift to reconcile.

What genuinely is shared with financial-statement-yearend

Print-first single self-contained HTML + inline <style> (no framework/build), WeasyPrint as the render target, table-layout: fixed, parenthetical negative formatting, tabular-nums, and the single-rule-then-double-rule subtotal/total convention (this family's statement theme: 0.75pt then 1pt+3pt-double; the yearend statement: 0.5pt then 1pt+3pt-double) — modeled as the shared paper.primitive.rule.* group both families draw from.

Open items

The line-number gutter (32px, Courier New, JS-injected) is a dashboard/screen-only feature — it does not render in WeasyPrint output and is entirely absent from the statement theme; it is not a print-domain token, kept as a documented recipe variant only. The statement theme's exact serif stack and column split remain provisional until the proforma engine work referenced above actually lands.