protocol-456listed

# The 456 Protocol Skill (v2.0) ## Purpose A lightweight sibling of Protocol 123 with a streamlined 6-phase lifecycle (Phases 0-5) designed for 80% of everyday engineering tasks (bugfixes, targeted features, AST adjustments, or pre-scoped tracks). Slashes token consumption and latency by 80-85% compared to Protocol 123 by eliminating multi-agent debate, removing review-arbiter bureaucracy, bounding web searches to high-quality official sources, and relying on a single specialized domain reviewer. Backed by deterministic runner `scripts/protocol-456.mjs`. ## Precondition & Fast-Track Intake (Phase 0) Protocol 456 handles both general fast-track tasks and pre-scoped plan tracks: 1. **Pre-Scoped Track (Fast-Track Branch)**: If input already names exact target files, step-by-step edits, and a runnable test verification command (e.g. from an SDD remediation spec), Phase 0 verifies the baseline and fast-tracks directly to Phase 3 (In-Session TDD), skipping planning Phases 1 and 2 while strictly retaining Phase 4 (Single-Reviewer Risk Audit). 2. **Standard Fast-Track Task**: If input is an arbitrary request (e.g. "исправь баг в CLI по 456"), Phase 0 verifies working tree cleanliness, Phase 1 formulates a compact SDD plan with on-demand web research, and Phase 2 secures fast human approval before TDD. ## Activation Rules & Trigger Phrases - **Strict Trigger Rule (Explicit Activation Only)**: Activated STRICTLY AND ONLY when the user explicitly invokes it via `456`, `по 456`, `