Releases · foundryside-dev/warpline

24 Jun 06:16

v1.2.0

6024fed

Latest

Minor release: the snapshot spine is now correct-by-construction and every enrichment dimension carries an explanatory weft-reason. Frozen warpline.<contract>.v1 MCP contracts are unchanged; the success envelope gains one additive top-level key (enrichment_reasons). Merged after a release-grade multi-agent quality review (verdict: ship; 0 blockers, 0 majors; every frozen-contract invariant verified to hold).

Added

enrichment_reasons — a new additive top-level envelope key carrying the {reason_class, cause, fix} weft-reason triple per dimension, so every absence reads as explained absence (the closed six-key enrichment vocab is unchanged). sei, governance, and reserved requirements now carry triples.
Conformance — 4 new golden vectors (GV-LW-6, GV-HON-SEI/GOV/REQ; 18 total) lock the atomic-capture and honesty invariants; the golden-vector fixture is now portable for the GS-7 5th-producer oracle, with a hub handover package under docs/integration/.

Changed

Snapshot edge-capture is correct-by-construction — a single BEGIN IMMEDIATE transaction (capture_snapshot_atomic) replaces the prior multi-step write. A snapshot is never visible until all its edges are committed, and a mid-capture failure leaves the prior good snapshot intact (fail-closed, locked by a regression test + GV-LW-6).

🤖 Generated with Claude Code

Assets 4

24 Jun 05:23

tachyon-beep

v1.1.3

a8a2c2f

warpline 1.1.3 — version metadata fix

Patch release fixing stale self-reported version metadata. Frozen warpline.<contract>.v1 MCP contracts remain unchanged.

Fixed

warpline.__version__ now derives from the installed package metadata (importlib.metadata) instead of a hand-maintained literal. That literal went stale at 1.1.2, so warpline --version, the MCP serverInfo.version, and every response envelope's meta.producer.version reported 1.1.1 on the 1.1.2 build. The version is now single-sourced from pyproject and cannot drift; the package-version test asserts that property rather than pinning a literal.

If you deployed 1.1.2, upgrade to 1.1.3 so warpline reports its own version correctly (the 1.1.2 hook-hang fix is included).

🤖 Generated with Claude Code

Assets 4

24 Jun 02:37

tachyon-beep

v1.1.2

dc945cd

warpline 1.1.2 — post-commit hook hang fix

Patch release fixing a post-commit hook hang. Frozen warpline.<contract>.v1 MCP contracts remain unchanged.

Fixed

LoomweaveMcpClient now enforces a single per-request deadline instead of a per-select() timeout. The 10s timeout was reset on every read, so a loomweave serve that emitted any output within each window (notifications, log lines, partial frames, unmatched envelopes) while never completing the matching response made call_tool loop forever — hanging the post-commit hook (the fail-soft try/except never fired because nothing raised). The read loop now bounds the whole request: select() gets the remaining time and the deadline is checked each iteration, so a stalled Loomweave surfaces as a TimeoutError the hook's fail-soft path catches.