hrt-dark-mode-routing

dark.md existing is the only signal dark mode is active (created by hrt-dark-mode-opt-in). This skill holds the routing rules that were previously copied into every phase instruction. A phase instruction points here with one line; the rules live here.

If dark.md does not exist, this skill does nothing — every finding follows its normal path to the user.

The rule, by calling phase

A finding that would normally escalate to the user is routed as below. Everything that auto-resolves outside dark mode still auto-resolves — dark mode never changes the auto-resolve rule, only where the non-auto-resolved findings go.

Phase	Routes to `hrt-dark-mode-decision-gate`	Still goes to the user	`dark.md` section
`proposal` (`hrt-adversarial-authoring`, artifact: proposal)	a single-reviewer UNANCHORED finding	everything the security skills decided; the `hrt-change-size-gate` "one change or several?" question	Proposal
`specs` (`hrt-adversarial-authoring`, artifact: specs)	a single-reviewer UNANCHORED finding	everything the security skills decided	Specs
`design` (`hrt-adversarial-authoring`, artifact: design)	a single-reviewer UNANCHORED finding	everything the security skills decided	Design
`align` (`hrt-align-consistency-review`)	every ALIGN DECISION and HIGH finding	nothing extra — but VERIFY and WALKTHROUGH are unchanged, and WALKTHROUGH stays the mandatory closing review; the user is also shown `dark.md`	Align (tag each entry with its cycle number)
`apply` Phase 1 (`tdd` loop)	a seam-mismatch blocker (the gate can weigh an alternative seam against code, design, and specs)	any other Phase 1 blocker	Apply
`apply` Phase 2 (`hrt-apply-code-review`)	every finding that would otherwise surface to the user	nothing extra	Apply