What's new in HYTHE 0.2.0

Get the release · npm package

A current checkpoint you can name

A scope's current pointer chooses its accepted checkpoint. A newer revision on an ordinary stale branch does not displace it. Reconciliation explicitly selects the result and retains the history.

Facts and loops follow that choice

Opt into resultVersion: 3 to receive values from the accepted lineage, provenance, competing heads, and coverage. Legacy and divergent values are separate. Old scopes may need reconciliation to adopt the model; requesting v3 alone does not perform a migration.

Smaller checkpoint changes

Use v3 record for facts and loops without resending working state, and patch for a merge patch. Both require the pointed parent and return a conflict if it has changed. Existing v1/v2 result shapes remain compatible.

Installation correction

The 0.2.0 package has two executables. Use npx -y -p @hythe/mcp@0.2.0 hythe-mcp outside a matching source checkout. The released wizard's generated bare npm command needs the correction in our quickstart, including absolute Node/bridge paths for clients launched from arbitrary directories.

Evidence

Implementation and contracts · client checks. This release does not establish universal compaction recovery or guaranteed model behavior.