Structured Coding 0.1.1

Patch release. One user-facing fix.

Fixed

--check-hooks reported a healthy registration on a Codex project that had never been trusted, while Codex was loading zero hooks — a silent failure where you wait for a hook that will never fire.

It now says so, and names the file to add the entry to:

… Codex has not been told to trust /path/to/project: add a
[projects."/path/to/project"] entry with trust_level to ~/.codex/config.toml,
or trust it through the host. Until then it loads no project-local hooks at all.

It reports and changes nothing: no trust is granted, no configuration is written, nothing is blocked.

Claude Code has no equivalent level and is never shown this.

Also since 0.1.0

PostToolUse delivery, listed as unverified in the 0.1.0 notes, has been observed on Claude Code with a real agent-run git commit reaching the handler. No code changed for that; only what was known about it.

Upgrading

There is no automatic upgrade. Compare or back up an existing installation, then reinstall; --check-hooks reports the installed release. An existing hook registration keeps working and is rewritten only by --upgrade-registration.

Still not implemented, deliberately

merge-guard is not implemented and will not be. A guard that actually blocks would take away something you can do today, and a guard you can work around is a reminder — which the prompts already provide. Everything in this toolkit should stay something you can bypass.

The continuity compact validation debt remains open: triggering compact needs an interactive session, and manufacturing a substitute path would produce evidence about the substitute rather than about compact.

Full 0.1.0 notes, including what this toolkit deliberately does not do: https://github.com/yuema137/structured-coding/releases/tag/v0.1.0