Repository navigation
v1.23.0
Aggregate rows from real tickets. A script prints one row of counts from a working doc, in the
project, so cost and challenger figures can leave a real project without its text.
scripts/ticket_stats.py <workdoc> [--row]. Read-only. PrintsCOST: lane=… scope=… dispatches=… dispatch_tokens=… unmeasured=… session_tokens=… minutes=… gates=… not_met=… mango=… date=…, or with--rowthe same fields as adocs/COST.mdtable row. Every field has a fixed shape
(a number, a fixed word, a version, a date) and is checked against it before printing, so no ticket
key, path, name or text from the doc can reach the output; no message quotes the doc.- Read from the doc, never estimated. Lane from
TIERand aDISCLOSURElist under## Phase 5;
scope fromSCOPEand theReviewed atfile list; dispatches, tokens andunmeasuredcells from the
Cost ledger; gates fromGate <n> status: cleared; raisednot metfrom the firstCHALLENGER VERDICT; the date fromLast updated:. Session tokens, minutes, the mango version and how many
not metitems were real are not in the doc: they come from--session-tokens,--minutes,
--mango,--real, or printunknown. Exit 3 when a field the doc should carry was not found. docs/COST.md. The table's columns are now the script's fields.validate.pyrefuses a header
that differs from them, a row with another number of cells, and any cell outside its field's shape.
The USD,cost_tierand model columns are gone: they are outside the approved aggregate list. The
Field report issue template now asks for the printed row only.- Runtime words unchanged. No skill, agent, principle or template text changed.