mirror of https://github.com/pbakaus/impeccable.git synced 2026-09-22 02:56:52 +03:00

Files

T

Paul Bakaus 5ddf1ad7bd Merge main and honor selector waivers in palette readings

Keep selector-waived colors out of the page-wide two-hue palette gate introduced on main. A focused regression fails without the fix; Rust workspace, rebuilt-engine Bun/Node, distribution and direct/snapshot Chrome checks pass. Rebuild the detector bundle. Leave aggregate multi-selector attribution unchanged pending pbakaus's reporting-contract decision.

AI-assisted by Codex under pbakaus's instructions.

2026-09-21 11:20:25 -07:00

00-header.js

The Rust engine: one binary replaces every script and the JS detector, fully open (#714 )

2026-09-04 10:42:45 -07:00

10-probe.js

Five rendered rules measure what they claim, and a hit records the width it fired at (#840 )

2026-09-21 08:22:08 -07:00

15-snapshot.js

Five rendered rules measure what they claim, and a hit records the width it fired at (#840 )

2026-09-21 08:22:08 -07:00

30-scan-common.js

Fix selector waivers across live and visual scans

2026-09-14 18:32:00 -07:00

35-visual.js

Fix selector waivers across live and visual scans

2026-09-14 18:32:00 -07:00

40-overlay.js

extension: kinpaku UI for the popup, DevTools panel, sidebar and overlays (#729 )

2026-09-04 13:00:13 -07:00

50-scan.js

Fix scoped waivers in hooks and pattern scans

2026-09-14 18:50:37 -07:00

60-offscreen.js

Fix scoped waivers in hooks and pattern scans

2026-09-14 18:50:37 -07:00

99-footer.js

The Rust engine: one binary replaces every script and the JS detector, fully open (#714 )

2026-09-04 10:42:45 -07:00

README.md

The Rust engine: one binary replaces every script and the JS detector, fully open (#714 )

2026-09-04 10:42:45 -07:00

README.md

browser-bundle: the page-side JavaScript of the detector

Plain JavaScript that runs inside a page or the extension: the DOM probe the wasm rule core calls back into, the page snapshot producer, the visual-contrast sampling IO, the overlay UI, the scan API and the extension's offscreen document. Measurement and presentation only; every rule decision is a call into the wasm rule core built from crates/core (docs/ENGINE.md).

Two consumers:

crates/browser embeds 15-snapshot.js (the snapshot producer the URL engine injects; no WebAssembly runs in the page).
crates/bundle (the impeccable-bundle library) embeds every file here with include_str! and concatenates them, in filename order, with the wasm core into the in-page bundle plus the extension's extension/detector/ pieces. cargo xtask bundle is its caller inside this workspace: it writes dist/detect-antipatterns-browser.js, copies that bundle to the tracked crates/live/assets/detect-antipatterns-browser.js the engine embeds, and writes the extension pieces. A downstream crate with its own rule pack calls the library directly (docs/ENGINE.md).

Because the files are embedded, a new one here has to be added to PAGE_JS in crates/bundle/src/lib.rs (and to the order it is concatenated in); a test fails when the two lists disagree.

15-snapshot.js lists the computed-style properties the rules read; the bundle build checks that list against the core's and fails when they drift.