v0.6.0 — Fog Gate

0.2 gated proof; 0.3 gated the seam; 0.4 metered the depth; 0.5 gave it a cockpit. 0.6 gates the fog — high-uncertainty work maps its unknowns before it builds: no map → no confident build.

Added

• /ratchet:map — the pre-build fog gate. Walks the task through the four unknown-quadrants — known knowns (settled ground with file:line evidence), known unknowns (one blast-radius-ordered question at a time), unknown knowns (tacit taste surfaced by putting concrete options in front of the user), unknown unknowns (a swept landmine field) — and hands over one durable four-quadrant map, a build plan, and a copy-paste implementation prompt before any code is written. CLI-backed (artifact kind:"unknown-map", decisions, assumptions, open loops); its open items drain ratchet score confidence until closed.
• Aperture routes through the map. ratchet score aperture folds /ratchet:map into the A3–A4 metered sequences (before build) and returns a mapRequired flag — true at A3+, or when a single dimension the summed score under-weights demands it (taste = 2, or terrain = 2 with any ambiguity). /ratchet:ignite routes high-uncertainty work through the fog gate instead of relying on the operator to remember. A4 still builds nothing.
• The map lives through the build. New templates/unknowns-map.md (four-quadrant file shape + a Deviations during build section) and templates/deviation-note.md (map said X → code revealed Y → call made). /ratchet:build builds against an existing unknown-map artifact and records deviations as decisions/open-loops/defects instead of silently absorbing them; /ratchet:handoff surfaces them so the receiver never re-litigates what the build discovered.

Notes

• Method grafted from dzhng/skills explore-unknowns, expressed in ratchet's own vocabulary — no prose copied.
• Zero new runtime dependencies. npm test green across Node 18/20/22 on Ubuntu and Windows.

Full changelog: v0.5.0...v0.6.0