Build `pipeline_decision(test_passed, lint_passed, coverage_pct)` returning one of `"deploy"`, `"warn"`, or `"block"`: 1. `not test_passed` → `"block"` (red tests never ship — full stop). 2. `not lint_passed` → `"block"` (style violations are a tip-of-iceberg signal; gate them). 3. `coverage_pct < 60` → `"block"` (below the floor — would mask real regressions). 4. `60 <= coverage_pct < 80` → `"warn"` (ships, but the dashboard flags the risk). 5. Otherwise → `"deploy"`. This is the canonical CI gate stack — order matters.