spec(port): port specs/port/trios/crates/trios-cli/src/cmd/race.t27 (Closes #9489)

[dmitrii-f-t27]

Summary

Port gHashTag/trios:crates/trios-cli/src/cmd/race.rs (at 8b229e9489ee, 279 lines) as specs/port/trios/crates/trios-cli/src/cmd/race.t27 — Roadmap Stage 6 (goal #4548), target t27c gen-rust. Closes #9489.

The original is the IGLA RACE CLI command: init creates the Optuna study in Neon and prints its SQL schema, status renders the live leaderboard with the ASHA rung ladder, report_trial logs a trial result back to the race.

Per the issue's rule ("Port the decision, not the plumbing"), the four listed functions are ported under their names — the three transports (init, status, report_trial) with undefined; bodies no test calls — and the decisions are ported as pure functions with 12 tests (40 runtime asserts, 0 vacuous), including the original's own test_race_config_default:

• RaceConfig_default — the default configuration: Neon fallback URL, igla-race study, reduction factor 3, rung bounds 3 (1000 steps) / 27 (9000 steps), target BPB 1.50 (original lines 29-41; the env read is the caller's plumbing, the fallback constants are the decision);
• the schema shape: 3 tables, 2 views, the igla_race_trials table and igla_leaderboard view under their declared names (lines 77-148);
• status_limit — the unwrap_or(10) default, with the take(limit) cap against the entry count (lines 168, 207);
• params_truncated_len / params_needs_ellipsis — the 25-character parameters column with its ellipsis, exactly when longer than 25 (lines 209-213);
• agent_label — the missing-agent ??? fallback (line 208);
• the mock leaderboard rows by rank (BPB 2.716/2.743/2.780, ALFA/BRAVO/CHARLIE) and the race statistics (12 active, 42 completed, 23.5% promoted, lines 171-230);
• asha_step_ladder — 1000 → 3000 → 9000 steps — and igla_found — the BPB < 1.50 threshold on the last rung (lines 232-235);
• bpb_display_decimals ({:.3}, line 253) and report_includes_agent (the Agent line's presence gate, lines 255-257).

Rust's Option has no unwrap construct in this language: the decisions that read it are ported as verdict functions taking the presence flag, the shape the issue's table gives argv and optional inputs.

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: 21/24 tested — the only untested are the 3 transports, by design (no test may call them).
• t27c test-report: 12 tests / 12 pass / 0 FAIL / 0 BLOCKED, 0 vacuous passes.
• t27c gen | grep -c 'not yet implemented': 0; gen | wc -l: 215 (> 12).
• grep -cE '^\s*(pub )?fn (RaceConfig_default|init|status|report_trial)\(': 4. grep -cE '^\s*test\s+(["|[A-Za-z_])': 12 (≥ 4).
• Boundary: git status --short — exactly this one file.
• python3 tools/dupe_scan.py --name <fn> for all 21 new helper names on a clean origin/master worktree: no function named … in 2039 spec(s) — all unique.

Note

The twin issue #9571 carries the identical brief for the same file (same original, same target); this port resolves it — no separate port is needed.

Dmitrii Fedorov (@dmitrii-f-t27)

[dmitrii-f-t27]

Correction of my earlier comment on this PR. The earlier text asked for a merge and said the red checks were base failures only. That was wrong while CI is red, and it is withdrawn. This is not a new merge request.

Current state (head de458ef): 26 checks success, 3 failure. The CI is not green. (Correction: the earlier text said 27 passed; the right number is 26.)

The port: specs/port/trios/crates/trios-cli/src/cmd/race.t27 only, Closes #9489. Its own tests: 12 of 12 pass, 40 runtime asserts, 0 vacuous, checked natively with t27b on the latest base and by the reference. The earlier parse, gen and typecheck checks stand.

The three failures, precisely:

• cli-tri: cli/tri/src/gates.rs:9012 does include_str! of .github/workflows/brain-seal-refresh.yml. That workflow was deleted in ci: one queen-publish job opens the derived-record PRs the labs' verdicts allow (Closes #9092) #9117 (ci: repair the two workflows whose failure was in the workflow #3324 only removed its push step). It fails the same way on master. Tracked in cli-tri: retire deleted-workflow test and refresh measured census pins #9634; the fix needs an owner decision, see cli-tri: retire deleted-workflow test and refresh measured census pins #9634 (comment).
• duplicate-bodies: 12 violations on master (groups of the gen_w ports and the STEP1/STEP2 ports). The full master CI artifact was compared. That none of this spec's helper names appear in those groups is not the proof; the proof is the master run itself. gen_w part: spec(port): share tree helpers across eight gen_w ports (Closes #9633) #9636 (issue duplicate-bodies: share tree helpers across eight gen_w bench ports #9633); STEP1/STEP2: ci: remove copied helpers from STEP1/STEP2 t27 ports #9631.
• t27b-native-ratchet: on master one native refusal (rust_convert, CSE hoist, ci: restore rust_convert native pass (reference CSE hoist regression) #9632) plus a backlog of unlisted specs. In addition this PR has one unlisted row of its own: specs/port/trios/crates/trios-cli/src/cmd/race.t27 passes natively but the ledger docs/reports/t27b_expectations.json has no row for it. A missing ledger row of this port is not a pure base failure; it needs the ledger refresh (t27b-native ratchet is red on every master run since it landed: ledger 099ac2224 predates 16 improvements and 40+ new specs #9600) or a one-line data row. The mesh-node crypto mismatch is mesh-node port: stop random keypair test from reading undefined primitive results #9635 (PR t27b: repair crypto and rust_convert; distinguish PR ledger lag #9637).

Tracking: #9631 (STEP1/STEP2), #9632 (rust_convert), #9633 with PR #9636 (gen_w), #9635 with PR #9637 (mesh-node crypto), #9634 (CLI), #9600 (ledger).

@gHashTag: please keep the golden-chain merge pending until every check on the last SHA is green. Nothing is requested now.

Dmitrii Fedorov (@dmitrii-f-t27)