v0.4.0 — Trust Layer

v0.4.0 — Trust Layer

This release strengthens Stemma’s safety guarantees: reviewed plans cannot bypass ownership checks, independent outputs cannot silently overwrite each other, and retired files remain visible until their removal is resolved.

Safer planning and application

• Saved plans are validated against the current project and profile before application. Tampered or stale plans are rejected without writing files.
• Independent entities keep distinct output destinations. Conflicting paths—including case-equivalent names and file/directory conflicts—are blocked before writing.
• Import records ownership only for source files verified by a byte-identical same-provider round trip. You can then edit the canonical project and apply those changes without a preliminary apply.
• Replacing the canonical project through import revokes ownership that belongs to the previous project. Later applications cannot silently reuse that authority.

More reliable checks

• check reports pending deletions as unresolved output instead of claiming the target is up to date.
• apply preserves tracking for retired files until they are removed manually.
• Inspection errors for retired files block the operation instead of being treated as missing files.
• Targets with no remaining output reconcile their manifest after manual cleanup.
• apply preserves the plan’s warnings and informational diagnostics, including in JSON output.

More faithful imports and exports

• Brace-expansion globs survive provider conversions without being corrupted by Copilot’s comma-separated applyTo.
• Recognized metadata with invalid types is rejected with blocking diagnostics rather than silently discarded.
• Malformed canonical Markdown produces actionable diagnostics instead of panicking.

Updating

Update Stemma using your usual installation method, then regenerate any saved plans with the new version before applying them.

Review pending deletions reported by check. Stemma continues to leave file removal to you.

Known limitation

Matching output beneath a symlinked ancestor directory can still be accepted and recorded as owned. No external overwrite was demonstrated in the audited case. This is tracked in #53 for v0.5.0.

Maintenance

The regression suite now uses smaller, explicitly selected fixtures, reducing redundant snapshots while retaining coverage of provider output, round trips, and safety guarantees.

v0.3.0

What's Changed

• Develop by @alexvinola in #13

New Contributors

• @alexvinola made their first contribution in #13

Full Changelog: v0.2.0...v0.3.0

v0.2.0

Full Changelog: latest...v0.2.0

Latest build (master @ b8006497f868ac960e374f24742006a7ce75d0e5)

Automatic build from the tip of master. Not a versioned release —
replaced on every push. For a stable version, use a tagged release
once one exists.

Commit: b800649