Repository navigation
Phase 6: Invalid, Partition, diagnose, github_matrix - #57
Merged
Merged
Conversation
…matrix Negative targets are classified through the negative-row search and covered by a sub-request over the other parameters with the same engine, with separate bookkeeping and a ! marker on negative rows. Must-include, full factorial, and excursions accept wrappers under their row policies. realize draws each Partition once under the caller's rng. diagnose ranks combinations present only in failing cases and groups indistinguishable ones; followups finds isolating cases or proves there are none. github_matrix writes a validated GitHub Actions include matrix with JSON.jl. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
figures, JSON field-name validation Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Owner
Author
|
Review round 1 applied (see Full suite: 309,720 pass, 0 pending, 0 failures. 🤖 Generated with Claude Code |
The docs environment pinned Documenter 0.25, which needs JSON 0.21, while the package now requires JSON 1, so CI could not resolve it. Documenter 1 makes missing docstrings and unresolved references errors by default; they stay warnings until Phase 7 completes the manual. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
README and home page lead with the promise, the decision table, and one example with its printed output. The manual is a tutorial in five levels, nine how-to guides by job, explanation pages on values and oracles, interaction coverage and its evidence, constraints, and the engines, a reference organized by purpose with every exported docstring opening on the situation it serves, a 0.4 to 0.5 migration table, developer pages, and a one-pager for AI agents. Doctests run in the docs build and in the test suite; the build fails on any warning. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
wording, two-check lockfile pattern, badge and contract wording Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Phase 7: documentation and first contact
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.
Phase 6 of
design/20260926_implementation_plan.md, stacked on #56. Review note with the complete target-screen transcript and open decisions:design/phase6_review.md.Invalid: the covering design is built over ordinary values, then each invalid value's negative targets (contract §6) are classified and covered by a sub-request with the same engine; results keep separate negative bookkeeping, mark negative rows with!, andreportstates the two guarantees. Must-include, full factorial, and excursions accept wrappers under their row policies.Partition: results keep the wrapper;realize(case; rng)andrealize(cases; rng)draw once per partition under the caller's generator.diagnose(cases, passed): ranked suspects grouped by identical failure patterns, explicit statuses for no failures, all failures, and conflicting duplicates;followupsfinds an isolating case or provesinseparable/indistinguishable/unknown. Marked experimental.github_matrix(cases): a validated{"include": [...]}via JSON.jl; wrappers, non-finite numbers,missing, and collections rejected naming row and field before anything is written.Full suite: 276,387 pass, 0 pending, 0 failures. Aqua green.
🤖 Generated with Claude Code