enzyme v0.7.2

Enzyme release notes - v0.7.2

Short version

Enzyme now reads a single growing log file — a journal, a running draft file, a
day-sectioned transcript — as the timeline it actually is, instead of one note
pinned to one date. Recognized logs are recorded as log: lines in
config.toml, where you can see what Enzyme noticed and correct it by editing
one line; a recorded log becomes its own retrieval anchor with catalysts drawn
from across its real date span. Date detection now handles weekday-prefixed
headers (Monday, February 16, 2026), the standard export style. The release
also carries the v0.7.1-cycle fixes: symlinked .enzyme dirs survive setup,
the web UI note-save 422 is fixed, and failed background epoch builds surface
in enzyme status.

What shipped

Append-log timelines (range: v0.7.1..v0.7.2, 56c4296)

• Per-entry chunk dates - chunks cut from a dated log entry carry that
  entry's date (chunks.entry_date), and catalyst context selection uses them,
  so one long journal spreads across its real eras instead of collapsing onto
  its file date. A one-time backfill upgrades already-indexed logs, rewriting
  legacy paragraph-chunked ones and re-queuing them for embedding.
• Config-declared log entities - enzyme scan --write-config records each
  recognized log as a sorted, deterministic log: line in the vault's
  config.toml entities list. Indexing promotes exactly the recorded logs to
  first-class entities with one occurrence per dated entry (replace semantics —
  re-indexing never inflates frequency). Removing a line removes the entity on
  the next refresh; adding a line promotes an unchanged, already-indexed file.
• Broader log detection - date headers may be ISO, numeric, prose
  month-name, or weekday-prefixed (Monday, February 16, 2026 /
  Tue 2026-02-17); an arbitrary leading word still correctly blocks
  detection. Validated on a 6,791-doc vault: 17 logs recognized (4 journals,
  13 day-sectioned transcripts), zero false positives — metrics tables,
  backlink scaffolds, and date-citing essays all correctly rejected by the
  entries-with-real-bodies gate.

Workspace-setup skill (ed15ab3)

• Anchors reveal - setup conversation now leads with what Enzyme anchored
  on in the user's vault (their folders, tags, logs, in their vocabulary),
  paired with questions each anchor makes answerable; health verdicts are the
  footnote, not the headline.
• Log recognition is a settings edit, never a note edit - the skill no
  longer instructs type: log frontmatter stamping; recognition lives in the
  log: config lines the user can read, narrate, and delete. (This lands the
  wiring the 2026-07-30 skill reviews required before documenting config-based
  log labeling.)
• Capture coaching - a new bounded section for vaults whose retrieval
  handles do not exist yet: at most two future-capture habits, each tied to a
  concrete finding and the question it would unlock.

v0.7.1-cycle fixes included in this range

• Symlinked .enzyme dirs preserved and repaired during setup (issue #6,
  3b488e9) - re-setup no longer destroys an iCloud/symlink arrangement.
• Web UI note save no longer 422s (issue #7, 49145c9) - UI payload
  aligned with the API; legacy shape still accepted.
• Failed background epoch builds are visible (issue #11, 54f0c1a) -
  enzyme status surfaces a failed background refresh instead of silently
  reporting the stale epoch.

Why this matters

A vault's healthiest capture habit — many dated notes — was always legible to
Enzyme, but its second-most-common shape, the single file that grows by dated
entries, was invisible as a timeline: retrieval saw one blob on one date.
Rather than asking users (or agents) to stamp metadata into their notes, the
recognition is written where the user already curates Enzyme's attention:
config.toml. Detection decides how a file is parsed; only the visible,
user-editable config decides what becomes a retrieval anchor. That split is
also why detection improvements are now low-risk to ship — a wrong recognition
is one deletable line, not silent behavior.

Measured improvements

• Log timeline coverage: 4 docs / 98 dated chunks -> 18 docs / 565 dated
  chunks on the 6,791-doc development vault after weekday parsing + backfill
  (sqlite counts, 2026-08-06). Caveat: single vault; shape-dependent.
• False positives: 0 across 6,791 docs; 14 near-miss files (metrics lists,
  dated scaffolds) correctly gated (detection sweep, 2026-08-06). Caveat:
  single vault.

Feedback we responded to

• Feedback: Recording a log in config did nothing (log_paths was inert),
  so skill guidance was blocked in review.
  Response: The log: entity grammar ships wired end-to-end: scan writes
  it, indexing consumes it, catalysts generate from it.
  Status: shipped

Upgrade / how to try it

curl -fsSL https://enzyme.garden/install.sh | sh
enzyme -p <vault> status        # applies the entry-date backfill on open
enzyme -p <vault> scan --write-config   # records recognized logs as log: lines
enzyme -p <vault> refresh

Then check ~/.enzyme/config.toml for log: lines and remove any you
disagree with. If an older enzyme binary also runs against the same vault
(automations, watchers), upgrade it too — pre-0.7.2 binaries rewrite log
chunks without entry dates when a log file changes.

Maintainer review checklist

• Git range and release channel are correct (v0.7.1..v0.7.2, master).
• Every feature claim maps to a commit (56c4296, ed15ab3, 3b488e9,
  49145c9, 54f0c1a).
• Every metric has before/after/source/caveat.
• Private feedback is anonymized (internal review threads paraphrased).
• No unsupported security, privacy, customer, or benchmark claims.