- CI: the "Native Linux tests (C++ SMLib)" job, Clippy's run with
--features smlib and every SMLib fetch step go; the kernel rig and the
fillet rig build the CLI without the feature, and the ladder gate runs
without --kernel smlib.
- xtask kernel-cases has no --kernel any more (solidcore|smlib|both, and
the side by side with the C++ kernel); passed, it is refused as --route
is. A run keeps results.json and dumps/ in its output folder and writes
docs/kernel-cases.md, the kernel's report.
- The per-area lists: each area's KNOWN_FAILING.solidcore becomes its
KNOWN_FAILING, replacing the C++ kernel's list; the workflows, the
README, the plan's self-test and xtask's help say so.
- tests/KNOWN_FAILING_TESTS.smlib, xtask's SMLIB_LIST and
scripts/fetch-smlib.sh are deleted; PATHS-ALL drops the script.
- The CLI's kernel-cases names its kernel solidcore.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtL5M41G8Nua7HvuFPZkmJ
KNOWN_FAILING.solidcore lists the 24 cases that fail on the default kernel, 23 of them also on SMLib's
list. The ladder golden is the C++ kernel's and solidcore differs on one case, so that gate opts in.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk
--known-failing follows the run's kernel: KNOWN_FAILING.solidcore for the default and the CI gates,
KNOWN_FAILING for --kernel smlib. The solidcore lists come with the final pin. Also fixes the --route
test for the new default.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk
--kernel smlib and both remain. --known-failing still grades the SMLib side, whose lists these are,
so it needs that said, and the CI gates opt in. The ladder takes --kernel for its one backend.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MNXLXkZLQ6T7TSi4wswcmk
A plan job (scripts/ci/kernel_rig_plan.py, with its self-test) maps a pull request's changed files
to the areas: tests/kernel-cases/<area>/PATHS for each area, tests/kernel-cases/PATHS-ALL for the
shared core, the ladder whenever any area runs. Areas come from the folders, so a new one needs no
workflow edit. Pushes, merge groups, the release gate and runs by hand run every area. The
kernel-rig check counts a skipped build or shard as passed only when the plan selected none.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kernel-rig.yml builds solidcraft-cli once (release, SMLib prebuilt; sccache on a sticky disk
that only pushes to main and develop commit) and hands it, with the rig's runner, to a matrix
of eleven shards: the ten areas of tests/kernel-cases/, each against its KNOWN_FAILING, and
the ladder against its golden. One path filter covers the kernel surface; drafts skip; a new
push cancels a pull request's old run; merge groups always run it, and the release gate calls
it. The areas other than fillets get a KNOWN_FAILING with only its header, to be seeded from
develop after the SMLib pin bump.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>