How we got here
The hooks SDK was moving from source-tree development into installed binary usage. That exposed a packaging edge: the compiled binary needed the same workspace and install behavior as the source checkout, but the error-clearing path for SDK hooks was not surviving that environment. The release range is one focused fix across `apps/axctl/src/hooks/cli.ts`, `sdk-install.ts`, and `sdk-workspace.ts`, backed by a new end-to-end SDK CLI test.
This was not a feature expansion. It was the release that made the previous hook work safe for people using the actual distributed binary instead of a development checkout.
What changed
SDK hook install resolves the compiled workspace (#565): the workspace helper now understands the compiled binary case and can locate the embedded or installed hook assets it needs. The install path gained explicit coverage for that mode.
Hook errors are cleared correctly: the CLI path now clears SDK hook errors when the compiled binary repairs or reinstalls hooks, instead of preserving an old error after the underlying problem has been fixed.
The regression is covered end to end: `sdk-cli.e2e.test.ts` exercises the CLI shape that previously only showed up after compilation, while the workspace/install tests cover the lower-level resolution branches.
ax hooks status
ax hooks install --allWhy it matters
Hooks are trust and workflow infrastructure. If the installed binary reports a stale hook error after the repair path has done its job, users cannot tell whether the guardrail is broken or the diagnostic is wrong. v0.34.2 keeps that status surface honest for binary installs.