Loom 1.8.19

Loom 1.8.19

Loom 1.8.19 removes false planning blockers found during real project use and prepares the current public main source as an immutable signed release.

What changed

• Explicit plan-only requests remain planning requests even when they describe a substantial application.
• Workspace inspection uses bounded classification instead of treating every ignored root as unresolved by default.
• Large repositories can return a safe partial planning contract instead of failing only because a complete workspace hash exceeds its time bound.
• Read-only planning keeps implementation changes prohibited while disclosing the bounded project-local plan artifacts Loom creates.
• Signed updates preserve the active owner-vault schema and convert incompatible activation state into a bounded error instead of terminating the MCP transport.

Verification

• Exact source commit: c09e99d2d0794e72e2a2226e28fc6c0d44518e65
• Quality CI: 26/26 jobs passed on Windows, Linux, and macOS with Python 3.10 through 3.14.
• Native compatibility: 21/21 jobs passed across x64 and ARM helper targets.
• Current test inventory: 1,296 tests.
• Exact public-cut SHA-256: 3808ed2b61fa63e507ac1e3c8ebde788c425bb1029b2dea23e98a9dd9ebeaf85
• Canonical plugin SHA-256: d14d7ab133ea3341a55af17bd53400528982470de36a6946fcbe977ac5b027b9
• Release subject: b36522612788da214ffad721d62eb416e3bea5ad8d96911b1af64eab9b18eac2
• Final package firewall: clean across 484 files and four private-path token classes.

The release remains local-first and contains no owner vault, telemetry, personal project state, or private planning material.