Skip to content

CodeEraser 1.5.1

Choose a tag to compare

@github-actions github-actions released this 02 Sep 00:03
· 55 commits to main since this release

CodeEraser 1.5.1

A maintenance release: the close-out sweep after 1.5.0 (a 43-agent "could have,
didn't" pass and a 13-agent i18n audit, every confirmed item landed) plus the
website tidied end to end. Scores are fully comparable with 1.5.0: no judged
axis moved, no default guard tier changed, the wire stays at 6.5.0 and the index
schema at 15; every change to the judged tree is either a comment, a rendering
of an existing fact in the reader's language, or an additive report field.

Dead-code rows say why in the reader's language

ce deadcode used to mint its reason as an English sentence in the measurement
layer and print it into Chinese consoles and the GUI in both languages. The
measurement side now emits a code (0 = no kept in-edge, 1 = referenced only
by dead code); ce.deadcode-report 0.4.0 and ce.graph-canvas 0.4.0
carry whyCode beside the English why, additively, and the console and the
GUI render it from their own language tables. Older reports fall back to the
English sentence they already carry, never to undefined.

Smaller fixes from the same sweep

  • The GUI health screen's OK / FAILED verdict was hard-coded English; it now
    reads the handshakeOk / handshakeFailed keys, the same words the CLI uses.
  • ce erase's advice rows for a language with unresolved reference sites now
    say how many sites remain; ce.erase-plan 0.2.0 carries sites additively
    and the wire's reason bits are untouched.
  • Six source comments and one methodology booklet still said "until a score
    floor lands"; the close-out ruled that floor out, and the comments now say so
    instead of promising it.
  • The nine frozen evaluation points in bench.json cite docs/X.md:A-B in
    prose that no gate ever parsed; a new gate (bench_frozen_sources) resolves
    every citation and requires each number in the value to appear on the cited
    lines. Six more docs-constant chips are bound to the source constants they
    name (allowlist 22 → 16).

The website

All eight pages of https://codeeraser.dev were reworked from screenshots rather
than from the stylesheet: one shared stylesheet (the per-page <style> blocks
were byte-for-byte copies the scan-only gate cannot see), unified tables,
footers and metadata, pictures that reserve their space before loading, a jump
bar and stable anchors on the methodology page, two new Chinese diagrams
(methodology.zh.svg, stack.zh.svg), the archify diagrams stamped dark with
translated descriptions — and a handful of real errors found by looking: a
diagram that said "five named conditions" where there are six, a chip backing
the wrong fact, an overflowing text line, straight quotes on the Chinese page.

Benchmarks

1.5.1 changes cli/src, so it earns a row; per the series' own rule the whole
latency table is replayed in one sitting after the tag, and the rows for 1.5.0
and 1.5.1 land together with that replay. Until then every version-bearing
surface says exactly that.

Full details in the CHANGELOG. Channels: GitHub Release (ten pinned assets),
crates.io, npm, https://codeeraser.dev.