mirror of
https://github.com/pbakaus/impeccable.git
synced 2026-09-14 07:06:45 +03:00
Paul BakausandClaude Fable 5.1
0547ed6a63
The engine no longer lives in a separate repo. `crates/` is a snapshot of the
open crates (foundation, core, common, context, live, hook, skills, comp,
comp-verbs, html, browser, detect, cli) plus `Cargo.lock`, taken as a git
archive of the engine repo at the commit that finished the boundary split.
None of that repo's history comes with it, and none of it should: the closed
half stays private.
The closed half is the rule engine. It ships as a prebuilt native archive per
target, `libimpeccable_detector.a`, published as a `detector-v<X>` GitHub
Release on this repo. `crates/core/build.rs` resolves and links it three ways:
`IMPECCABLE_DETECTOR_LIB=<dir>` for a local detector build, else the
`~/.impeccable/detector/<version>/<target>/` cache, else a download verified
against its `.sha256` sidecar. `crates/core` is a thin shim over a three-symbol
C ABI; nothing above it knows the boundary exists.
What changed versus the engine repo copy:
- Every crate manifest moves from `license-file.workspace` to
`license.workspace` (this workspace declares Apache-2.0), and the workspace
gains the `postcard` dependency the boundary encoding needs.
- The launcher contract test reads `skill/scripts/impeccable{,.cmd}` instead of
a sibling `launcher/` dir, and `engine_binary` downloads from
`github.com/pbakaus/impeccable/releases/download/engine-v<version>/` instead
of the retired dist repo. No oracle golden carried the old URL, so no
re-recording was owed.
- The tests that hunted for a public repo through `IMPECCABLE_PUBLIC_REPO`,
`../impeccable-second` or a hardcoded home directory now resolve the root as
`CARGO_MANIFEST_DIR/../..`, because they are in it. The env var stays as an
override for an out-of-tree checkout.
- The in-page bundle (`detect-antipatterns-browser.js`, 2 MB of generated wasm
glue) is no longer tracked. `crates/core/build.rs` resolves it beside the
archive, hands the path to `impeccable_core::browser::IN_PAGE_BUNDLE_JS`, and
live mode serves that. `scripts/check-detector-release.mjs` now requires it
and its `.sha256` in a detector release.
- The live crate embeds `skill/scripts/live-browser*.js` and
`modern-screenshot.umd.js` directly rather than through vendored copies, so
the binary and the installed skill cannot drift.
- `crates/browser/assets/` (an unused second copy of the bundle) is gone.
- `tests/lib/engine-bin.mjs` also accepts `target/release/impeccable`, so a
plain `cargo build --release -p impeccable` is enough to run `bun run test`.
Verified with the archive from a local detector build: `cargo test --workspace`
267 pass, oracle 795 pass / 0 fail / 0 missing, `bun run build` clean, the
default suite green, and the launcher's `engine-probe` handshake answering
through `skill/scripts/impeccable`.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Vau2X53xGTjjTCXWMVBoNY
45 lines
1.6 KiB
TOML
45 lines
1.6 KiB
TOML
# The impeccable runtime: one Cargo workspace next to the skill it powers.
|
|
# `cargo build --release -p impeccable` produces the engine binary the launcher
|
|
# (skill/scripts/impeccable) runs. See docs/ENGINE.md.
|
|
[workspace]
|
|
resolver = "2"
|
|
members = ["crates/*"]
|
|
|
|
[workspace.package]
|
|
version = "0.1.0"
|
|
edition = "2021"
|
|
license = "Apache-2.0"
|
|
publish = false
|
|
|
|
[workspace.dependencies]
|
|
impeccable-foundation = { path = "crates/foundation" }
|
|
impeccable-common = { path = "crates/common" }
|
|
impeccable-core = { path = "crates/core" }
|
|
impeccable-detect = { path = "crates/detect" }
|
|
impeccable-html = { path = "crates/html" }
|
|
impeccable-browser = { path = "crates/browser" }
|
|
impeccable-live = { path = "crates/live" }
|
|
impeccable-context = { path = "crates/context" }
|
|
impeccable-hook = { path = "crates/hook" }
|
|
impeccable-comp = { path = "crates/comp" }
|
|
impeccable-comp-verbs = { path = "crates/comp-verbs" }
|
|
serde = { version = "1", features = ["derive"] }
|
|
serde_json = { version = "1", features = ["preserve_order"] }
|
|
thiserror = "2"
|
|
regex = "1"
|
|
once_cell = "1"
|
|
# The boundary encoding: every value that crosses into the closed detector
|
|
# is postcard bytes (docs/ENGINE.md).
|
|
postcard = { version = "1", features = ["alloc"] }
|
|
|
|
# No cross-crate LTO: crates/core links the prebuilt detector as a native
|
|
# archive of Rust objects, and fat or thin LTO internalizes the std symbols
|
|
# those opaque objects still reference (the link then fails with "symbol(s)
|
|
# not found"). Cargo's default thin-local LTO is what `lto = false` means.
|
|
[profile.release]
|
|
opt-level = 3
|
|
lto = false
|
|
codegen-units = 1
|
|
strip = true
|
|
panic = "abort"
|