From e5051d75279e6c7b2baba4df5d56414a5436eea1 Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Thu, 20 Aug 2026 06:29:04 +0200 Subject: [PATCH] chore(rivet): RQ-58-SELDSL and RQ-58-FLAKE are implemented, not proposed MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Both shipped and merged with all 9 required contexts green — SELDSL as #1004 (50 -> 74 Rocq-proved rules; sel_dsl_rules reads 74 on main) and FLAKE as #1006 (29b1a853) — but neither lane bumped its own rivet status, so the release-readiness query still counted them as unfinished scope. Release readiness is a QUERY over these statuses, not an opinion, so a stale 'proposed' on merged work makes the v0.58 gate under-report. Caught by reading the scope on fresh main rather than at release assembly, which is where it would otherwise have surfaced as a late blocker. Refs #242. --- artifacts/release-v0.58.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/artifacts/release-v0.58.yaml b/artifacts/release-v0.58.yaml index 2f1cc520..6999b940 100644 --- a/artifacts/release-v0.58.yaml +++ b/artifacts/release-v0.58.yaml @@ -282,7 +282,7 @@ artifacts: stands. That is a real finding about the DSL's expressiveness and should be reported as such — with the specific construct that defeats it — rather than quietly reducing the target from 20. - status: proposed + status: implemented release: v0.58 tags: [north-star, vcr-sel-001, rocq, subtraction] links: @@ -509,7 +509,7 @@ artifacts: fixture a process-scoped temp path if the collision hypothesis holds. That converts a confusing flake into a precise message and closes the silent direction at the same time. - status: proposed + status: implemented release: v0.58 tags: [flake, stale-artifact, harness, silent-direction] links: