AGENTS.md: one switch, SOLIDCRAFT_KERNEL, in place of the booleans-only note

Rebasing onto the sugar rule kept both the old SOLIDCRAFT_BOOLEANS
paragraph and its replacement; only SOLIDCRAFT_KERNEL exists now.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QWhMwdqJYQKQq8RCLSL1LT
This commit is contained in:
jyvikoandClaude Opus 5.5 committed 2026-10-21 08:57:19 -04:00
1 parent 5c593774a0
commit e4d89352f9
1 file changed
-5
-5
View File
@@ -31,11 +31,6 @@ solidcore's API (ADR 0002). Until it merges back, these rules differ from `main`
engine and doc. A thread is a helical sweep in the kernel; its ISO size table, the check that
refuses a thread off its hole's or shaft's size, and multi-start threads (an array of helical
sweeps) are sugar.
- **Booleans can run through SMLib**: in a build with the feature, `SOLIDCRAFT_BOOLEANS=smlib`
(read once per process; `truck` or unset is the default) sends every `solidcraft_kernel::boolean`
through SMLib, with SMLib's own history (`crates/kernel/src/boolean_backend.rs`); the engine and
`solidcraft-cli` pass the feature on as their own `smlib`. Set to `smlib`
in a build without the feature, every boolean fails rather than running truck.
- **One switch picks the kernel**: in a build with the feature, `SOLIDCRAFT_KERNEL=smlib` (read
once per process; `truck` or unset is the default) runs every operation that has an SMLib path
through SMLib; operations ask `solidcraft_kernel::backend()` (`crates/kernel/src/backend.rs`).