Skip to content

report: aligned terminal tables; refuse a mismatched --final-repeat - #11

Merged
mnkprs merged 1 commit into
mainfrom
report-table-layout
Aug 29, 2026
Merged

report: aligned terminal tables; refuse a mismatched --final-repeat#11
mnkprs merged 1 commit into
mainfrom
report-table-layout

Conversation

@mnkprs

@mnkprs mnkprs commented Aug 29, 2026

Copy link
Copy Markdown
Owner

Why

node src/report.ts printed Markdown pipe tables, which read as raw | rows when the fairtask-eval skill shows them inside an agent session. Worse, the skill's report command paired --final v3-verify with --final-repeat v5-rerun — a repeat of a different configuration — so an in-session report showed "75% · 65%" and "0 pts" for flag recall where the README says 70% → 75%, +5 pts.

What changed

  • src/lib/table.ts: one renderer with two formats — an aligned box table for terminals (Markdown emphasis stripped, display width counted in code points so κ/▲/▼ align) and the Markdown pipe table the README embeds. Section titles follow the same switch.
  • src/report.ts: builds rows as data and renders them; terminal format by default, --markdown for the README form. The --markdown output is byte-identical to the tables in README §4 (checked by diff). A --final-repeat whose variant differs from the final run's is refused with a message.
  • scripts/finalize-report.py passes --markdown.
  • src/data/build-eval-set.ts: the stratum and per-repository counts print as one line each instead of JS object dumps.
  • skills/fairtask-eval/SKILL.md: report command without the wrong --final-repeat; notes the table/markdown switch. README §2c rows for report.ts updated (--markdown row added; repeat rule stated).
  • src/table.test.ts: three tests for both formats (26 tests total).

…; refuse a repeat of another configuration

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@mnkprs
mnkprs merged commit 5b0b7de into main Aug 29, 2026
2 checks passed
@mnkprs
mnkprs deleted the report-table-layout branch August 29, 2026 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant