/* tools/corporation-tax/index.html's own CSS, extracted from its inline
 * <style> (Task 11). This page's article shell (main, h1, h2, .byline,
 * .faq, .faq h3, footer, .footer-wordmark-link, .footer-wordmark) matches
 * the insights-family template rather than tools/_shared/flow.css's own
 * shell, so it stays here rather than in either shared file. .tool-form,
 * #tool-output and .capture-form are this page's own calculator and email
 * capture.
 *
 * The font-weight:600 pin on h1/h2/.faq h3 is this page's own hand-written
 * copy of the same pin insights pages get from assets/insights.css: see the
 * comment inline below for why it is written per-rule rather than as a
 * blanket selector (this page's .pp-title and .tool-what also use
 * Newsreader with no weight and land on 400, where a blanket pin would move
 * them rather than preserve them).
 *
 * This page now also links tools/_shared/flow.css, which it did not before:
 * *{box-sizing:border-box}, body and the tool-top:css:start/end block were
 * dropped here rather than kept as a second copy.
 *
 * CORRECTED 2026-09-02, and the correction is the reason the .tool-back rule
 * below exists. The claim this comment used to carry, that the whole
 * tool-top:css:start/end block was BYTE-IDENTICAL to flow.css, was measured
 * against the WORKING-TREE copy of flow.css, which carries an unstaged hunk
 * belonging to another session. Against the COMMITTED file, read with
 * `git show HEAD:tools/_shared/flow.css`, exactly one line of that block
 * differs: committed flow.css paints the back button's hover and keyboard
 * focus as a solid orange fill with paper-coloured text, where this page has
 * always painted a translucent orange wash with ink-coloured text. Dropping
 * the block therefore repainted two states the 1280px static harness cannot
 * see. Restored below, and restored as background and colour ONLY, with no
 * transform: flow.css sets transform:translateX(-2px) on the same selector and
 * nulls it again inside @media (prefers-reduced-motion:reduce), and this file
 * loads after both, so repeating the transform here would resurrect it for a
 * reader who has asked for no motion. Measured with a real mouse hover in
 * Chromium against the pre-Task-11 tree, which reported
 * background rgba(223,89,17,0.18) and color rgb(20,20,20) before against
 * rgb(223,89,17) and rgb(240,233,220) after.
 *
 * The :root block below is the same class of leak in the token layer.
 * flow.css declares its own :root, and it loads AFTER /assets/tokens.css on
 * this page, so linking it silently repainted --font-mono (dropping
 * SFMono-Regular and Menlo from the fallback stack, which moved the computed
 * font-family on 187 elements) and --ease-ink (a different easing curve,
 * carried in flow.css under its own documented exemption). Neither was this
 * page's value before, so both are put back to canon here rather than left to
 * whichever file happens to load last.
 *
 * letter-spacing:normal on h1 below undoes a leak this same extraction
 * introduced: this file's own h1 rule already overrode font-size and
 * line-height from flow.css's h1, but never mentioned letter-spacing, so
 * CSS resolves that ONE property from whichever rule sets it, not from
 * whichever rule "wins" as a whole; flow.css's -.02em was the only
 * declaration for it and painted through unopposed. Caught by a pixel diff
 * confined to the heading (4308px, 0.16% of the page) after the two
 * pages otherwise matched exactly, not by reasoning about it in advance.
 * min-height:0 on main undoes the same class of leak (flow.css's main also
 * sets min-height:60vh, which this page's own main override never
 * mentioned); left unconfirmed by a pixel diff, since the page is already
 * taller than 60vh, but corrected on the same principle regardless.
 */
:root{--font-mono:"IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, monospace;--ease-ink:cubic-bezier(0.22, 1, 0.36, 1)}
.tool-back:hover,.tool-back:focus-visible{background:var(--orange-wash,rgba(223,89,17,0.18));color:var(--ink,#141414)}
h1{letter-spacing:normal}
main{min-height:0}
main{max-width:46rem;margin:0 auto;padding:4rem 1.5rem}/* font-weight:600 is PINNED on the three heading rules below. It is the weight these headings already painted, back when this page loaded a Newsreader that stopped at 600 and the browser resolved bold down to it. The shared font URL now carries 700 for the tool results screens, so without the pin these headings would silently get heavier. The rules are named one by one rather than pinned as a group, because .pp-title and .tool-what on this page set the same family with no weight and land on body text computing 400, where the same pin would MOVE the page rather than preserve it. */h1{font-family:Newsreader,Georgia,serif;font-weight:600;font-size:2.4rem;line-height:1.15;margin:0 0 1rem}h2{font-family:Newsreader,Georgia,serif;font-weight:600;font-size:1.5rem;margin:2.5rem 0 .75rem}a{color:var(--orange)}.byline{color:var(--ink-muted);font-size:.95rem;margin:0 0 2.5rem}.faq{border-top:1px solid #B3A887;padding-top:1.25rem;margin-top:1.25rem}.faq h3{font-family:Newsreader,Georgia,serif;font-weight:600;font-size:1.15rem;margin:0 0 .4rem}footer{max-width:46rem;margin:3rem auto 0;padding:2rem 1.5rem;border-top:1px solid #B3A887;color:var(--ink-muted);font-size:.9rem}.footer-wordmark-link{display:inline-flex;margin-bottom:.75rem}.footer-wordmark{height:22px;width:auto}.tool-form{background:var(--paper-2);border-radius:6px;padding:1.5rem;margin:2rem 0}.tool-form label{display:block;font-size:.95rem;font-weight:500;margin-bottom:.25rem}.tool-form input[type=number]{width:100%;padding:.5rem .75rem;border:1px solid #B3A887;border-radius:4px;background:var(--paper);font-size:1rem;margin-bottom:1rem}#tool-output{font-size:1.25rem;font-weight:600;color:var(--orange);padding:1rem 0}.capture-form{margin-top:1.5rem;display:flex;gap:.5rem;flex-wrap:wrap}.capture-form input[type=email]{flex:1;min-width:200px;padding:.5rem .75rem;border:1px solid #B3A887;border-radius:4px;background:var(--paper);font-size:.95rem}/* drawn: .btn-drawn in the markup */ .capture-form button{flex:none;white-space:nowrap}