Size/complexity/readability metrics report (ce.scan-report schema).

Verified T1/T2 clone blocks (ce.dedup-report schema).

Append-vs-rewrite and co-change over a git window (ce.churn-report schema).

Reference sites, resolution-free (the ce graph --sites rows).

Liveness verdicts over the reference graph, plus the symbol-level advisory of declarations no other file spells — never a verdict (ce.deadcode-report schema).

T3 near-miss clone judgment (ce.clone-report schema); units lists the cached unit universe instead.

Documentation-duplication judgment (ce.docdup-report schema).

Three-signal join: similarity, graph position, churn (ce.join-report schema).

Tree-scale structure judgment, eight axes (ce.structure-report schema).

ADR-006 baseline judgment: score, ratchet and axes (report only — this surface never writes a baseline).

The deterministic erase PLAN (ce.erase-plan schema) — dry-run by construction: this surface reaches the plan and nothing else, and applying it is a human act at the CLI or the GUI.

The applied-erase audit trail (ce.erase-trail-report schema): every record ce erase --apply or the GUI appended to .ce/erase-log.ndjson, with the lines the reader could not parse named by number. Read-only — nothing here can apply or append.

This machine's state (ce.doctor-report schema): ce-core handshake, the tier of every guard class the hooks read (the write guard, flow, tombstone), index freshness, daemon, degraded-run counter. The daemon is asked without being started.

Score trajectory over mainline git history (ce.trend-report schema; points cache in the index, rebuildable from history).

The same-role advisor (ce.similar-report schema): the units most like one unit or a text, in the core's order with its role bit and a six-channel evidence row; widen adds the PPMI associative view. Advisory — never a verdict.

One question in CE Datalog over the index's facts (ce.query-report schema): files, references, units, clones, mentions, path classes, with the built-in prelude (dead, reach, depends, same_dir, dir_ref) and the project's rules file; every answer labelled, its derivation under why; prelude answers the text a question builds on instead (ce.query-prelude schema: the prelude and the [rules.pack] program). Report-only.

The project's architecture rules judged (ce.rules-report schema): every assert in the rules file with its violations, each carrying its witness and derivation. The CLI exits on counts.violations; here it is a report.

Dead code inside functions (ce.flow-report schema): unreachable statements, dead stores, unused locals and parameters, judged by the core over flow/1 and placed by path, unit, kind, lines and variable; each finding says whether it is judged or advisory (unused parameters always are). Report-only.

Clone-merge suggestions (ce.merge-report schema): every clone group — T1/T2 families, T3 pairs — anti-unified by the core's merge/1: the parameters a merged function takes with each member's text at them, the member kept, the lines saved, feasible or why not. Advisory.

The architecture of the tree (ce.arch-report schema): directory layers and the arcs to cut out of their cycles (each with the file references behind it), file clusters and the files outside their cluster's directory, per-directory fan-in / fan-out / instability, and the files a change to impact reaches. Advisory.

Whether a newer CodeEraser release exists (ce.update-report schema): the latest tag, that tag's committed SHA256 pins, and the one action for this install. Reads the release index over the network; places nothing — applying is a human act at the CLI or the GUI.