spec(port): port specs/port/trinity/src/cli/tri_record.t27 (Closes #9620)

[dmitrii-f-t27]

Summary

Port gHashTag/trinity:src/cli/tri_record.zig (at ee512359254b, 157 lines) as specs/port/trinity/src/cli/tri_record.t27 — Roadmap Stage 5 (goal #4547), target t27c gen-rust. Closes #9620.

The original is the terminal-recording wrapper: it records any tri * command to GIF via asciinema + agg.

Per the issue's rule ("Port the decision, not the plumbing"), the one listed function is ported under its name as a pure function (no transports — the argv and environment reads, the directory creation, the file checks, the subprocess runs and the prints are the callers' plumbing) with 7 tests (33 runtime asserts, 0 vacuous, 100% function coverage):

• the usage gate (original lines 29-46): only the program name → the usage block prints and the run exits 1;
• the environment overrides with their fallback (lines 52-59): a present-but-invalid value keeps the default, exactly like the original's catch; an absent variable keeps it too — cols 120, rows 40, idle_max 3 carried as the defaults;
• the TRI_REC_OVERWRITE flag (lines 61-63): presence alone turns overwrite on — any value, no parsing;
• the basename cut (lines 72-75): the GIF is named after the command's first word — the length up to the first space, or the whole command when it has none;
• the existing-GIF block (lines 89-95): without overwrite an already-existing GIF stops the run before any recording;
• the exit-code cascade (lines 123-155): usage, the GIF block, an asciinema failure and an agg failure each exit 1; only a recording that ran and converted exits 0;
• the KB size display (lines 149-152): bytes / 1024, truncated.

Verification (all run live from the worktree root, zig 0.16.0)

• t27c parse: OK. t27c spec-status: IMPLEMENTED. t27c typecheck: 0 errors, 0 warnings.
• t27c coverage: 7/7 tested (100%) — no transports in this port.
• t27c test-report: 7 tests / 7 pass / 0 FAIL / 0 BLOCKED, 0 vacuous passes — the usage gate, the override rule for absent/present/valid/invalid values, the presence-only flag, the basename cut for no-space/space-first/multi-word commands, the GIF block both ways, the KB truncation at the 1023/1024 boundary, and the exit cascade through every stage failure.
• All four generators were run before the push: gen (124 lines, 0 'not yet implemented'), gen-rust, gen-c, gen-verilog.
• grep -cE '^\s*(pub )?fn (main)\(': 1. grep -cE '^[[:space:]]*test[[:space:]]+("|[A-Za-z_])': 7 (≥ 1).
• Boundary: git status --short — exactly this one file. The repo's lefthook pre-commit passed.
• dupe_scan: all 7 function names unique across the corpus (checked before the commit); the branch sits on current master and the bare scan reports zero error lines — no new duplicate group, none grew.

Dmitrii Fedorov (@dmitrii-f-t27)

[dmitrii-f-t27]

@gHashTag Please merge this PR into master via the golden chain — rights on gHashTag/t27 are read-only for me (403), so only you can merge it.

Verification of this head (e632042, on current master — no extra merge needed):

• Required CI trio green: validate, check-linked-issue, parse-ratchet; also Check L1 TRACEABILITY, duplicate-bodies and cli-tri green.
• The t27b-native-run artifact of this head (commit e632042, run 39066716817) row for specs/port/trinity/src/cli/tri_record.t27: reference pass, t27b pass, tests 7, invariants 0, asserts 33, blockers [], detail empty, reference_disagree: [].
• All four generators were run locally before the push (gen, gen-rust, gen-c, gen-verilog) — this spec emits cleanly everywhere.
• The only red checks are proven base-red on master WITHOUT this PR:
  • Corpus ratchet: the failing step is 'Every conflicted type name has a written verdict' — docs/reports/type_conflicts_classified.json disagrees with the tree (UNJUDGED/STALE). The identical error fails on master itself (workflow runs on 18c98cc and b655dce). This spec declares no struct or enum, so it cannot add a conflicted type name.
  • t27b-native-ratchet: the registration debt, red on master across this whole port series.

After the merge I will: verify the spec file live on the merge SHA, confirm #9620 auto-closed, and file the 14-step report.

Dmitrii Fedorov (@dmitrii-f-t27)

[gHashTag]

Landed unchanged (as a merge commit) in #10174, together with ten other green ports, on top of the master fixes #10160/#10172. Closing this as superseded; the linked issue closes when #10174 merges.