mirror of https://github.com/pbakaus/impeccable.git synced 2026-09-21 18:47:02 +03:00

Files

T

Paul BakausandClaude Fable 5.1 d3b58b02a3 The probe's two text-rect helpers say which text they read

`__textLineRects` collected only the direct text once the line probe grew
its own deep walk, so its name promised lines it no longer produced: it is
`__directTextRects`, the list the union rect is built from. The snapshot's
union helper takes the rects rather than the node now, and its comment says
so. No behavior.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LQBUunp8QttxZqihybNmtL

2026-09-20 20:03:28 -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

The probe's two text-rect helpers say which text they read

2026-09-20 20:03:28 -07:00

15-snapshot.js

The probe's two text-rect helpers say which text they read

2026-09-20 20:03:28 -07:00

30-scan-common.js

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

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

35-visual.js

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

2026-09-04 10:42:45 -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

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

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

60-offscreen.js

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

2026-09-04 10:42:45 -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.