docs(skill): challenge wording matches runtime enforcement exactly#11
Merged
Conversation
Grok follow-up on PR #10: probe counts now use the runtime's own --challenge-mode vocabulary (tactical=1, standard=5), and the bypass description states actual behavior — MCP has no bypass, CLI --no-challenge/--force warns and records no challenge object, and the challenge gate is NOT wired to the gate-waiver system. The WAIVER line stays as what it really is: the skill's own step-skip protocol, not a runtime requirement.
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).
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.
Applies the two tightenings Grok requested in its PR #10 CONCERNS verdict (its own verified wording): probe counts in runtime --challenge-mode vocabulary (tactical=1 / standard=5), and the bypass description now states actual behavior — MCP has no bypass, CLI --no-challenge/--force warns and records no challenge object, challenge gate is not wired to the gate-waiver system; the WAIVER line is the skill's own step-skip protocol.
🤖 Generated with Claude Code