enzyme v0.6.1

Enzyme release notes - v0.6.1

Short version

This patch release hardens Enzyme's setup and retrieval path for real agent work: provider-compatible LLM requests, delayed catalyst credential gates, clearer hosted LLM failures, and vector rebuilds when the embedding backend changes. It also adds enzyme doctor, a read-only diagnostic command for explaining what Enzyme sees in a vault, and ships the new Enzyme-native workspace setup skill through both the canonical skill and the Claude/Codex plugin mirror. The plugin release removes stale lifecycle hook claims and adds a release guard so hook files cannot silently reappear in the public sync.

What shipped

More tolerant LLM and catalyst setup

• LLM provider compatibility policy now normalizes configured URLs and sanitizes request payloads for Anthropic-compatible endpoints, reducing provider-specific request failures in hosted and BYOK setups (b1739e0).
• Catalyst credential checks are deferred until catalyst work actually needs them, while local --use-env-llm preflights still fail before destructive init or detached refresh work begins (435de5b, f80c1cf).
• Hosted LLM failures preserve returned detail instead of collapsing them into generic messages, so credit, auth, or provider errors remain actionable (ae48bbe).
• BYOK and index-only init paths no longer require an Enzyme login before work that does not consume hosted Enzyme credits (c32b3f9).

Safer indexing and refresh behavior

• Enzyme records the embedding backend used to generate vectors and rebuilds generated vectors when the backend changes, avoiding mixed-backend similarity state (505f2c2).
• Catalyst similarity recompute now skips the delete-and-recompute cycle when indexing, embeddings, and the catalyst fingerprint are unchanged (ee363c8, c32b3f9).
• MCP vault freshness now degrades to serving existing catalysts when catalyst refresh fails after local index work succeeds, instead of failing petri/catalyze outright (f80c1cf).
• ESE model fetches use rustls, removing the system OpenSSL headers requirement from that build path (92e8731).

Diagnostics for vault setup

• enzyme doctor is now available as a read-only diagnostic command with human and JSON output. It reports coverage, files absent from the DB, frontmatter anomalies, undated docs, embedding-window dropouts, stale index state, duplicate sets, and folder date coverage (b965ce1, 150f6c3, 3a92c56).
• The abandoned standalone structure command was folded into doctor so structural facts live in one diagnostic surface instead of adding another top-level command (b079ca9, 150f6c3).

Workspace setup and plugin sync

• The canonical workspace setup skill is now Enzyme-native and validated against dump, healthy-big-inbox, and malformed-YAML fixtures, with enzyme doctor as the factual inspection tool (a8c40d1, 151e1da).
• The Claude/Codex plugin now ships a byte-identical mirror of plugin/skills/enzyme-workspace-setup/SKILL.md, enforced by make check-workspace-skill / scripts/sync-workspace-setup-skill.py --check (aa63eaf, 985a302).
• The MCP server now embeds the mirrored workspace setup skill path instead of the deleted legacy plugin skill path, preserving the in-server instructions after the mirror rename.
• Claude/Codex lifecycle hook claims were removed from plugin metadata, and the release workflow now fails if hook files reappear in the synced plugin payload (29fcdac).
• Both installers remove the legacy local embedding model cache on install so stale cached model artifacts do not survive upgrades (693b3f2).

Why this matters

The release focuses on making Enzyme less brittle at the boundaries users hit first: provider APIs, login state, install state, and vault diagnosis. The guiding pattern is to make local-only work local, delay hosted-service checks until hosted work is needed, and expose facts instead of judgment when the vault shape is the thing under inspection. The plugin sync changes close a packaging gap where stale hook files could remain in the public marketplace even after the source plugin stopped claiming hook support.

Measured improvements

• Warm catalyst target recompute: 0.23s -> 0.05s on a 638-file warm run after skipping unchanged similarity recompute (ee363c8). Caveat: commit-recorded local run; not a cross-platform benchmark suite.

Feedback we responded to

• Feedback: Login and credit checks were blocking local setup modes that do not actually use hosted Enzyme inference.
  Response: BYOK, index-only init, and catalyst refresh now defer or soften hosted credential checks according to the work being performed.
  Status: shipped
• Feedback: Provider-compatible LLM endpoints could reject requests because Enzyme sent fields or URLs that were acceptable for one provider but not another.
  Response: Enzyme now normalizes provider URLs and sanitizes Anthropic-compatible requests before sending them.
  Status: shipped
• Feedback: Plugin metadata claimed lifecycle hook behavior that Claude/Codex plugin surfaces do not support.
  Response: The claims were removed and release sync now guards against hook files coming back.
  Status: shipped
• Feedback: Workspace setup agents needed a factual way to inspect vault health without turning a skill into an over-prescriptive rulebook.
  Response: enzyme doctor now provides the facts, and the workspace setup skill uses those facts for a narrower setup workflow.
  Status: shipped

Upgrade / how to try it

Update through the normal Enzyme install path, then run:

enzyme --version
enzyme doctor --json
enzyme refresh

For Claude/Codex plugin installs, use the v0.6.1 marketplace tag once the release sync finishes. Maintainers should verify that the public jshph/enzyme tag no longer contains hooks/hooks.json or .claude-plugin/hooks/hooks.json.

Maintainer review checklist

• Git range and release channel are correct: v0.6.0..HEAD from the enzyme-rust source-of-truth repo.
• Every feature claim maps to a commit, PR, or note in the release range.
• Every metric has before/after/source/caveat.
• Private feedback is anonymized.
• No unsupported security, privacy, customer, or benchmark claims.