Skip to content

chore: release v0.9.0#176

Merged
avrabe merged 1 commit into
mainfrom
chore/release-v0.9.0
May 21, 2026
Merged

chore: release v0.9.0#176
avrabe merged 1 commit into
mainfrom
chore/release-v0.9.0

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 20, 2026

Summary

Cuts v0.9.0 — the P3 cross-component stream-pair detection foundation plus a now-fully-operational Mythos delta-pass auto-runner. 12 commits since v0.8.1.

Area PRs
Cross-component stream<T> pairing detection (#141, ADR-3) #173
Mythos delta-pass auto-runner — 5 plumbing fixes to working state #162, #164, #170, #173, #175
LS-N verification gate — 19/19 approved loss-scenarios verified #161, #165
DWARF / witness-mapping discovery (Phase 1 of #130) #131
Regression coverage LS-A-8/9/19, LS-CP-4 #163, #165, #166, #169
CI footprint reduction (path filters) #171
fuzz.yml musl-target drop (closes #168) #170

Milestone-consistent: #141 was milestoned v0.9.0.

Not in this release (tracked for v0.10+)

Test plan

  • CI green
  • After merge: tag v0.9.0, push tag, watch release.yml build the 4 platform binaries

🤖 Generated with Claude Code

P3 cross-component stream-pair detection foundation + a fully
operational Mythos delta-pass auto-runner. 12 commits since v0.8.1.

Headline changes:

- Cross-component stream<T> pairing detection (#141, ADR-3). The
  StreamPairGraph foundation for the in-module stream adapter: meld
  now inventories at resolve time which fused components form
  producer -> consumer stream pairings. The ring-buffer / copy-chain
  emitter is a runtime-verified follow-up (ADR-3 Path N).

- Mythos delta-pass auto-runner (#162, #164, #170, #173, #175). The
  AI-driven discover protocol now runs automatically on every
  Tier-5 PR by the maintainer, via claude-code-action on a Max-plan
  OAuth token. Five plumbing fixes brought it to a working
  end-to-end state: scan -> NO_FINDINGS verdict -> sticky comment ->
  mythos-pass-done label.

- LS-N verification gate (#161, #165). Every approved loss-scenario
  in safety/stpa/loss-scenarios.yaml is now enforced to have a
  matching ls_<letter>_<num>_* regression test; 19/19 verified.

- DWARF / witness-mapping discovery (#131) — Phase 1 of the #130
  epic; pins today's lossy passthrough as the green-to-red oracle
  for the Phase 2 remap work.

- Regression coverage for LS-A-8/9/19 and LS-CP-4 (#163/165/166/169)
  — closed every missing-test entry the LS-N gate surfaced.

- CI footprint reduction (#171) — bench/fuzz/ci skip on docs- and
  safety-only PRs; meld is a leaner consumer of the shared fleet.

- fuzz.yml musl-target drop (#170, closes #168) — fixes the
  recurring "sanitizer incompatible with statically linked libc"
  fuzz failures.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

LS-N verification gate

19/19 approved LS entries verified

count
Passed (≥1 test, all green) 19
Failed (≥1 test failure) 0
Missing (no ls_*_NN_* test found) 0

Approved loss-scenarios.yaml entries are expected to have a
regression test named ls_<letter>_<num>_* (e.g. LS-A-11
ls_a_11_*). The gate runs each prefix via cargo test --lib --no-fail-fast and aggregates pass/fail/missing.

Failed LS entries

(none)

Missing regression tests

(none)

Updated automatically by tools/post_verification_comment.py.
Source of truth: safety/stpa/loss-scenarios.yaml.

@avrabe avrabe merged commit 220d278 into main May 21, 2026
14 checks passed
@avrabe avrabe deleted the chore/release-v0.9.0 branch May 21, 2026 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

smithy: sanitizer/libc config drift recurrence on fuzz smoke jobs

1 participant