chore(release): v0.11.0-alpha.10 — first release carrying self-update#9
Merged
Conversation
The alpha.9 release assets predate `s5d update auto`, while the shipped hooks.json already calls it — a release-binary user with updated skills would get a failing SessionStart hook (the same hooks/binary desync class as the ci bootstrap paradox). Two fixes: - SessionStart hook now degrades through a fallback chain: update auto → update check --hook → true. Any hooks/binary version skew in either direction lands on the best available behavior instead of a hook error. - alpha.10 cut with all four version touchpoints synced (Cargo.toml, three distribution manifests) and the prebuilt rebuilt, per the release-agent checklist added in PR #7.
random1st
added a commit
that referenced
this pull request
Jul 1, 2026
New tests: - approve_rejects_spec_modified_since_preview (#6) - import_rejects_spec_modified_since_approval (#6) - rollback_after_import_tombstones_aliases_and_removes_index (#10) - rollback_without_successful_import_fails (#10) - decide_rejects_winner_without_spec_ref (#15) - reconcile_restores_synced_status_after_drift (#9) Known bug (test ignored): - rollback_of_first_spec_does_not_break_second_spec_sharing_global_artifact (#13) — CONFIRMED: rollback tombstones global aliases by owning_package, breaking other specs that share the same global artifact. 84 tests pass, 1 ignored (known bug).
random1st
added a commit
that referenced
this pull request
Jul 1, 2026
…osed Scenario sweep (RAN-481, beta bar = 15/15): every previously uncovered or partial scenario now has a pinning test. The sweep was empirical — each gap was probed against the live binary first, and three of the six probes hit real defects, which is the point of the exercise. Closed scenarios: - #12 MCP containment: new tests/mcp_wire.rs speaks line-delimited JSON-RPC to the spawned binary — initialize/tools-list roundtrip, garbage/notification/unknown-method survival, and a full lifecycle over MCP proving the placeholder-import guard fires on this path too. - #9 reconcile semantics: reconcile is verify+stamp with fail-closed refusal — restore of uuid-bearing drift is structurally impossible (resolve() mints fresh uuids), so the test pins what matters: a failed reconcile never re-baselines the ledger and drift stays visible afterwards. - #14 partial corruption: re-init now restores deleted core files. - #5 decision tier: clean end-to-end without --force; the canonical path is >=3 hypotheses, evidence on each, acceptance criteria on the problem card, winner spec_ref via s5d new --hypothesis-id, and an explicit challenge summary. - #4 high assurance: full flow with configured test+contract commands on top of schema+graph+review, no --force. - #11 show: smoke assertions inside the #4/#5 flows. Bugs fixed (each found by its scenario probe): 1. Bulk 's5d reconcile' exited 0 while individual reconciles failed — an agent reading the exit code saw success over persistent drift. Now counts failures, prints them, and bails non-zero. 2. Re-running init did not recreate deleted config/ledger/index.yaml (only subdirs were repaired) — a deleted file bricked the project. ensure_core_files restores missing files with defaults and reports them; existing files, even corrupted ones, are never overwritten because that is a data-loss decision that stays with the user. 3. add-hypothesis/add-evidence rejected high-tier specs while the high scaffold ships a review gate satisfiable ONLY by gate:review evidence on a hypothesis — the canonical path of the most safety-critical tier was unpassable without --force. Loosened to decision|high at all four sites (CLI+MCP); decide stays decision-only since choosing a winner is decision-tier semantics. Known limitation documented, deliberately not fixed: owning_package is outside compute_state_fingerprint (G:type:id:uuid), so its corruption is invisible to drift-check even though rollback ownership depends on it. Pinned by a documenting test; the fix changes the fingerprint and would invalidate every existing baseline, so it needs an explicit migration decision. README tier table corrected: Decision and High carry a Review default gate (the table claimed None / Schema+Graph; code says otherwise).
random1st
added a commit
that referenced
this pull request
Jul 1, 2026
Closes the #9 gap: a standard/lightweight feature spec that DECLARED a `review` gate could never close it. The gate:review closure read only hypotheses[].evidence, and add_evidence hard-rejects non-decision/high tiers — so run-gates always failed and import was blocked (exit 7). Decision (S5D decision.s5d.review-gate-closure, winner confirmed by Roman over three rejected alternatives — relax the evidence tier-guard, forbid review on feature tiers, add a dedicated review-record): the review gate ALSO closes on a WorkflowPhaseRecord{status:Accepted} in the Record's phase_history — the human run-phase sign-off (named reviewer + timestamp) that feature specs already produce via `s5d run accept`. SCOPED to Standard/Lightweight only. Invariant (unit-tested): Decision/High review closure is unchanged. `is_feature_tier` gates the phase path, so an accepted phase can NEVER close a decision/high review gate — they stay evidence-only. High-tier rigor is preserved; the regression test proves it. Also: validate now errors when a Standard/Lightweight spec declares a review gate but has no workflow — the phase-acceptance closure would otherwise be unreachable. Mechanism: extracted eval_review_gate(spec, phase_history); run_gates gains a phase_history param sourced from the already-loaded Record at both call sites (CLI verify run-gates + MCP tool_s5d_run_gates). No new persistence — phase_history already exists on the Record. 267 tests pass (4 new, incl. the high-tier invariant); clippy + fmt clean. S5D-Spec: feat.s5d.review-gate-closure
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.
Release cut: alpha.9 assets predate
s5d update autowhile shipped hooks already call it — a release-binary user with updated skills gets a failing SessionStart hook. Fixes: (1) SessionStart fallback chain (update auto → update check --hook → true) makes any hooks/binary skew graceful in both directions; (2) all four version touchpoints synced + prebuilt rebuilt per the release-agent checklist. 200 tests green.🤖 Generated with Claude Code