Sheaft v0.2.1 technical preview

Sheaft v0.2.1

v0.2.1 is a technical-preview patch release for the v0.2.0 line.

What changed

• clarified README wording around dual-line Bering support so it is described as alternative accepted upstream contract lines, not simultaneous artifact dependencies
• restored the release-dry-run workflow as a real main branch signal and returned its README badge
• fixed CI template convention checks to match the shipped configs/analysis.v1.1.example.yaml handoff path
• fixed default config pack validation for absolute temporary output paths used during CI release validation

Stable within 0.2.1

• strict acceptance of io.mb3r.bering.model@1.0.0
• strict acceptance of io.mb3r.bering.snapshot@1.0.0
• strict acceptance of io.mb3r.bering.model@1.1.0
• strict acceptance of io.mb3r.bering.snapshot@1.1.0
• deterministic analysis and baseline comparison for a fixed artifact, config, and seed
• the dual-line semantics and advanced analysis behavior shipped in v0.2.0

Experimental within 0.2.1

• long-running serve / watch service mode
• local discover helper
• OCI image and Helm chart operational conventions

Compatibility with Bering artifacts

Sheaft v0.2.1 remains compatible with these upstream contracts:

• io.mb3r.bering.model@1.0.0
• io.mb3r.bering.snapshot@1.0.0
• io.mb3r.bering.model@1.1.0
• io.mb3r.bering.snapshot@1.1.0

Compatibility remains strict. Unsupported schemas, URI mismatches, or digest mismatches are rejected instead of being auto-coerced.

Known limitations

• no live chaos execution, traffic generation, or new discovery pipeline is introduced in this release
• explicit legacy predicates remain service-based unless explicit path/journey information exists
• advanced metrics remain unavailable instead of guessed when the artifact or external contract does not provide the required metadata
• serve / watch are included for evaluation, not yet as a stable long-term operational contract