core

v2.43.0 (2026-07-28) - REMOVED: the H-Sutra header Stop enforcement layer. hooks/h-sutra-enforce.sh is deleted and its Stop registration is gone. Nothing blocks or forces a redo for a missing or malformed header on any profile. The header itself survives as a convention: /core:start still documents the format, per-turn-discipline-prompt.sh still asks for it every turn, and the 9-cell classification log rail (holding/state/interaction/log.jsonl or \u002esutra/h-sutra.jsonl) is untouched -- it was always written by per-turn-discipline-prompt.sh, not by the enforcer. What dies with the hook: the .enforcement/h-sutra-audit.jsonl enforcement telemetry and the SUTRA_HSUTRA_ENFORCE_DISABLED / ~/.h-sutra-enforce-disabled kill-switches (nothing left to disable). Stop floors that REMAIN hard: per-turn-hard-gate.sh (Input Routing, Depth, BLUEPRINT) and flow-stop-check.sh (Flow, profile-gated). sutra-defaults.json now records per_turn_blocks.human_sutra_header.enforcement = convention_only, and the /core:start CLAUDE.md template no longer claims the header is hard-enforced. Founder direction 2026-07-28. + v2.42.0 (2026-07-28) - Two Stop-layer fixes reach the fleet. (1) blueprint-check.sh v3 is TEXT-FIRST (#81): it validates the BLUEPRINT block in the turn's response text -- the block the user actually sees -- instead of the .claude/blueprint-registered marker. Emitting a correct block now unblocks Edit/Write; the marker becomes a per-turn cache the hook writes for itself. PreToolUse enforcement narrows to FOUNDATIONAL paths (now configurable via per_turn_blocks.blueprint.foundational_paths in sutra-defaults.json, overridable per repo with blueprint_foundational_paths[] in .claude/sutra-project.json); ordinary files are floored at Stop by per-turn-hard-gate.sh on any turn that mutated a governed file. Closes the divergence behind #68, the 2026-07-08 Testlify incident and its 2026-07-27 repeat. (2) h-sutra-enforce.sh v8/v9 + flow-stop-check.sh honor .profile (#72): DIRECTION-VERB