CodeEraser 0.4.0

v0.4.0 — the structure screen grows a tree, and axis 3 lands where it lives

GUI

• Structure tree lens (map | tree switch, persisted): an indented
  directory tree over the SAME report the treemap renders. Each row rolls
  its subtree's findings into a heat rail (log-ranked against the report's
  own range), carries an own-findings chip, subtree/files columns under a
  sticky header, and inline axis tags — the count becomes the answer.
  Unary chains fold exactly like the treemap's strips; selection and the
  detail aside stay shared across both lenses.
• Squarified treemap (Bruls et al. 2000) replaces the slice-and-dice
  layout: tiles approach unit aspect, unary chains collapse to one strip,
  labels middle-truncate, and a paint-order halo keeps text legible on the
  hot end of the ramp.
• Three-screen polish round: brand header, alarm-ramp legend, score bar,
  chips-based summary, trend endpoint marker, candidate magnitude bars,
  language toggle fixes, and a window floor of 860×560.

Judgment core

• Axis 3 (misplaced) now reports its directories: findings carried
  no axis-3 rows even though the axes strip counted them — on this
  repository, 42 misplaced-file violations (46% of the judged total) were
  invisible to both GUI lenses and to the report's per-directory face.
  One predicate now feeds both faces (count + deduped dir list); the
  structure golden and the hand-computed test assertions moved with it.

Guard / reports

• The Stop audit closes its untracked blind spot: git diff HEAD
  cannot see a brand-new file, exactly what a probe-bypassing shell write
  leaves behind. The stop path now merges ls-files --others --exclude-standard (binaries count 0 lines, .ce/ skipped);
  ce precommit stays staged-only by design.
• ce graph --sites --format json carries a schema id
  (ce.sites-report/0.1.0) — the last bare-JSON face among the eleven
  report families.

Site & docs

• codeeraser.dev: showcase screenshots (treemap, tree, candidates), an
  architecture SVG shared by the README and both site pages, narrow-screen
  overflow fixes (one min() sweep), and stylesheet cache-busting so a
  deploy reaches returning visitors immediately.
• README (en/zh): hero screenshot, architecture diagram, tightened
  install section.

CI

• The ubuntu apt step gets real armor: a pinned mirrorlist, per-try
  timeouts, three attempts, and a 15-minute step budget — measured at
  23s on a healthy day instead of a six-hour black hole on a bad one.

Full test surface for this train: 54-case end-to-end matrix (all report
families, ratchet lifecycle, guard modes, daemon + MCP, installed-binary
resolution), core golden suite, cli integration suite, and the dogfood
gate this repository runs on itself every push.

CodeEraser 0.3.0

Ten assets, same shape as v0.2.0: ce + ce-core for three platforms, three GUI installers (NSIS / AppImage / dmg — each bundles both binaries as sidecars), and SHA256SUMS. Verify downloads against SHA256SUMS; the pins in plugin/bin/manifest.env are the permanent trust anchor (code signing is deliberately out of scope — see README).

New

• App icon. The GUI, installers and taskbar finally carry the product's own mark: a two-tone eraser mid-swipe through code rows, fragments dissolving in its wake. Legible down to 16 px.
• erase skill (Claude Code plugin). The delete half of the product loop: walks an agent from the three JSON report faces (deadcode / clone / docdup) through read-both-sides verification, exemption respect, small-batch deletion, and ce check convergence against the banked baseline.
• ce check --roast. Four score bands of console-only snark, bilingual, computed against the effective score scale.

Changed

• The GUI discovers ce-core through the same resolver chain as the CLI (env → bundled sidecar → PATH) instead of env-only — installer users get judgment out of the box.
• Versions are single-sourced: a mirror gate pins plugin.json / tauri.conf.json / gui Cargo.toml / ce-core.cabal to the crate version, and the core self-reports from Paths_ce_core (the 0.0.1-era injected literals are gone).
• README install sections lead with the prebuilt assets; the code-signing stance (ruled out, SHA256 chain as anchor) is stated in both languages.

Retired by ruling

PostToolUse deep-judgment, SARIF/Markdown output, and code signing/notarization are out of the design — recorded in DEVELOPMENT_PLAN.md with their reasons.

CodeEraser 0.2.0

Draft build phase (M7-P1). Unsigned binaries — verify SHA256SUMS; pins land in plugin/bin/manifest.env before the tag publishes this release.

CodeEraser 0.1.0

Draft build phase (M7-P1). Unsigned binaries — verify SHA256SUMS; pins land in plugin/bin/manifest.env before the tag publishes this release.