Skip to content

v0.1.2

Latest

Choose a tag to compare

@pr0d1r2 pr0d1r2 released this 10 Nov 07:07
· 1 commit to main since this release

Still a 0.1 patch, so the version ladder's promise is
unchanged: the json contract and the library surface may still move before
0.2. What a caller can observe: new set names (typography-<code>,
hazard:tags), mojibake reported as one finding and restored by fix,
init --keep-fixable, a schema key at the top of sets --format json,
prebuilt release archives, and the flake building on Intel Macs. v0.1.2
was planned on 2026-10-18 and never tagged, so everything since folds into
it.

Added

  • typography-<code>: every CLDR locale's own quotes and punctuation as a
    set, generated by the same script and pinned tag as the letter sets, with the
    same aliases and lazy lookup. *.md ascii+typography-pl keeps Polish U+201E
    and U+201D through ctrm fix and still straightens a U+201C. ctrm sets
    describes them as punctuation under kind locale, so unlisted_locales
    counts them too; ctrm init never drafts one.

  • double-encoded (#32): text that was UTF-8, read as Latin-1 and saved as
    UTF-8 again ("mojibake") is one finding per run, naming the character it
    decodes to (a.md:1:15 double-encoded "⊥" (U+22A5)), instead of a scatter of
    unrelated findings. The run is a lead U+00C2-U+00F4 plus its continuations
    with at least one C1 control, so an accented letter on its own, or U+00C3
    U+00A9 in Latin-1 prose, is left alone. ctrm fix re-decodes it losslessly,
    and ctrm init lists it under "fix these" instead of widening the file type
    to any.

  • A VS15/VS16 (U+FE0E/U+FE0F) right after a granted character that has a
    standardized variation sequence (✔️) is no longer reported, and fix
    leaves it, so text matching a tool's emoji output stays byte-exact (#34). A
    lone selector, or one after ASCII, is still reported.

  • hazard:tags in a .ctrm set list (#15): tests/fixtures/x/* ascii+hazard:tags
    lets tag characters (U+E0000-U+E007F) into the named paths only. Each is
    reported as a tag-character note at warn, never failing the run
    (not even under --strict), and fix leaves them. The pattern must be an
    exact path or a glob with a literal first segment (* and ** at the
    root are refused), and no other hazard class can be granted. guard
    still refuses to let an agent read such a file.

  • ctrm init --keep-fixable (#36): the draft grants what fix would
    rewrite too (typography), so check reports none of it; a hazard is
    never granted and still fails check. Without it,
    each file type's draft now says how many findings in how many files
    check reports until ctrm fix runs, counting only what the drafted
    line leaves ungranted.

  • x86_64-darwin in the flake systems (#20, closing #18). Consumers
    pin a tag, so v0.1.1 had no characterminator.packages.x86_64-darwin.
    nixpkgs 26.05 is the last release to support this system.

  • Prebuilt binaries attached to each GitHub release from this tag on:
    one archive each for Linux x86_64, Linux aarch64 and macOS aarch64
    (ctrm, LICENSE, README.md) plus one SHA256SUMS, built from the
    tag itself.

Fixed

  • ctrm sets --format json opens with schema like every other document;
    it began at verb. A key added, so the version stays 1. docs/JSON.md
    now lists the keys sets really has.