Repository navigation
Release Jun1 SUPPORTED.md authoring (operator D-REL-3b answered 2026-05-30: v0.1.0 supported = Rust + Python + Go; TypeScript = v4-alpha-only): author docs/SUPPORTED.md as the user-facing support-contract doc for v0.1.0. Location docs/SUPPORTED.md (root of docs/) survives §2 publish-snapshot strip l - #4025
Merged
Merged
Conversation
briansrls
marked this pull request as ready for review
May 30, 2026 20:37
Incorporate Compiler Spine v2 emit health (HIGH/MEDIUM/MEDIUM-LOW), known-open-bugs table, compile-verified weather hero status, and §2 v4 Rust/TypeScript alpha one-liners per release scope amendment. Co-authored-by: Cursor <cursoragent@cursor.com>
Drop cite of scripts/_internal/check-clean-checkout-build.sh from the normative contract; the inline compile + cargo check block is the auditable public receipt. Avoid pointing readers at paths stripped from the publish snapshot. Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls
force-pushed
the
session/silent-bee-431
branch
from
May 30, 2026 20:46
2ec4a57 to
61b8fd0
Compare
Contributor
Author
|
Addressed (valid) — Fixed in — sent from silent-bee-431 |
Operator amendments: Go stays in §1 (MEDIUM-LOW); add complexity.dag and interpreter demos with test evidence; document weather Python/Go swap as not yet e2e clean while Compiler Spine emit fixes are in flight. Co-authored-by: Cursor <cursoragent@cursor.com>
Replace prior disclaimer text with match-as-expression vs TCO temp-decl (Python) and module/:= scope (Go) failure classes; note v0.1.0 disclaimer commitment and v0.1.1 relaxation ETA. Co-authored-by: Cursor <cursoragent@cursor.com>
5 tasks done
briansrls
added a commit
that referenced
this pull request
May 30, 2026
…cation transcript (zero-overclaim) (#4032) * docs(close/receipt): #4023 follow-on — §1.5 run-status discipline (zero-overclaim) Per operator directive 2026-05-30 (via snappy-bee-513): "i do NOT want ANY overclaim". Adds §1.5 to v0.1.0-v4-ship-disposition.md as the canonical Close/Receipt-lane statement of emit-vs-run discipline. Cross-doc consistency: PR #3991 (D-REL-1) and PR #4025 (SUPPORTED.md) hyperlink here rather than restate. §1.5 contents: - Rule: PROVEN requires demonstrated run-status (passing CI gate, e2e transcript, or executable receipt that validates output); emit success alone is never sufficient. - Why: supported-tier emit lenses routinely produce output that satisfies the emitter but fails python -m py_compile / go build / cargo check / rustc; calling those surfaces PROVEN would be the most user-visible class of overclaim. - Per-target run-validation table (Rust / Python / Go / TS / LeafModelClaim runner / RoundTripClaim) with explicit pass conditions and the fallback (GAP / EXECUTION_NOT_WIRED) when only emit succeeds. - Audit cadence: downstream PROVEN claims subject to retroactive downgrade by this lane if they cite emit-only evidence. - §1.5 self-audit of this supplement's §2 rows: leaf-model rows cite the three CI gates that actually fire on main (ci.yml:243/246/249); no §2 row claims PROVEN. merry-bear-248's verification (cited in PM brief as Python/Go weather-hero emit-OK/run-fail evidence) not yet on main as a tracked file; principle stated abstractly so the citation lands when that artifact is available. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * WIP: Close/Receipt Manager — authority over close predicates, two-axis dispos * docs(close/receipt): #4032 — link §1.5 to landed weather-verification transcript Adds the concrete-evidence-anchor sentence to §1.5 pointing at docs/release/v0.1.0-weather-verification-2026-05-30.md (landed in this same PR). Closes the abstract→concrete loop snappy-bee-513 requested: SUPPORTED.md / D-REL-3b / README per-target claims can now cite a hard file path as the run-status receipt. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Remove --dry-run from the §1 CLI support table; document that main.rs does not pass cli.dry_run into handle_run (always dry_run: false). Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Author
|
Addressed (valid) — Removed Fixed in latest push on — sent from silent-bee-431 |
This was referenced May 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-opened by session-dashboard for session
silent-bee-431.Pushing to
session/silent-bee-431advances this PR.Worker attestation
Before flipping this PR to ready for review, confirm each item:
npm test,cargo test) and the result.Closes #Ndirective.Summary
TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.
Test plan