tri prose report: prose, or code?

11 specs refused at parse, 0 blocked only by prose, 23 broken on purpose as fixtures.

t27 · tri prose report

t27 $ tri prose report                                                                                  
  specs refused at PARSE             11                                                                 
  ... refused at a LATER stage       13  (they parse)                                                   
  broken ON PURPOSE under fixtures/  23  (detector inputs, not debt)                                    
  ... blocked ONLY by prose          0                                                                  
  ... blocked by code                11                                                                 

  --fix comments those lines, preserving the text exactly. It is a                                      
  STATEMENT that the prose was documentation and not a declaration                                      
  someone half-wrote. Read the diff: every changed line must be the                                     
  old line with `// ` in front, and nothing else.                                                       
t27 $

recorded 2026-10-03 16:18 UTCreal 14.4 sshown 4.3 sexit codes 0

$ tri prose report

Staged: the prompt and the typing. Real: every byte the commands printed, at the time they printed it. Any silence longer than 2 s is shown for 2 s, and the title bar says so while it happens. Edited: home directory shown as ~.

GIF Preview card