v0.4.0 — the trademark screen

Every engine gains a TMview trademark screen: one request across ~75 registers (JPO / USPTO / EUIPO included) counting same-name word marks — clear, no identical (N similar), or IDENTICAL mark exists on the report's TM line. A screen, not clearance: no Nice-class or similarity judgement, and the attorney advice stays. The bundled onomly.wasm grows to 84,930 B with the JSON parse; native binaries rebuilt by CI (stripped).

v0.3.0 — stripped

The Linux binaries lose their embedded DWARF: CI strips them after the build, bringing them from ~26 MB to the same class as the macOS binary. Engines unchanged (native almide / bundled WASI 0.3 component / native single-file binaries).

v0.2.0 — no shell anywhere

The shell scripts are gone. Three engines, zero wrappers: native almide (full verdicts incl. whois), the bundled onomly.wasm WASI 0.3 component under wasmtime (http-only), and — new — native single-file binaries built by CI from onomly.almd with the release almide compiler (onomly-linux-x86_64, onomly-linux-aarch64, onomly-macos-aarch64; full verdicts, no dependencies, 5.7 s for a full sweep). Engine detection now lives in SKILL.md as instructions. Also installable as a Claude Code plugin: /plugin marketplace add O6lvl4/onomly.

v0.1.0 — three engines, one launcher

First tagged release. The onomly launcher auto-detects the best engine: native almide (full verdicts incl. whois) → the bundled onomly.wasm WASI 0.3 component under wasmtime (http-only, fastest sweep) → serial bash. Installable as a Claude Code plugin (/plugin marketplace add O6lvl4/onomly) or by plain clone. onomly.wasm (67,438 B, verified build, direct async ABI) is attached with its sha256; rebuild needs an almide develop build until the wasi:http@0.3 p3 shim ships in an almide release (almide/almide#1710).