Add seven code-review Eval tasks on the host #1266

Activity

1. JacobStephens2

   added

   enhancementNew feature or requestNew feature or request

   ready-for-humanRequires human implementationRequires human implementation

   on Oct 24, 2026
2. JacobStephens2

   added a parent issue on Oct 24, 2026

   • Spec: a Bar a release that changes nothing can pass #1252
3. JacobStephens2

   marked this as blocked on Oct 24, 2026

   • Spec: Experiments, which measure a change before it reaches production #977
4. JacobStephens2

   marked this as blocking on Oct 24, 2026

   • Run the A/A Experiment on the host #1267
5. JacobStephens2 commented on Oct 25, 2026

   

   JacobStephens2

   on Oct 25, 2026

   OwnerAuthor

   More actions

   The host's code-review suite now has 17 approved Eval tasks. These are the seven added from the "Strong" table in #1252's triage comment. An agent on the host drafted each one's criteria, and Jacob approved all seven on 2026-10-25.

   Task	Bug	PR (issue)	A catching finding says
   bug-847-pr-788	#847	#788 (#712)	The reservation's reserve and release pushes leave out --no-verify, so a pre-push hook can block or strand the reservation
   bug-686-pr-267	#686	#267 (#262)	The re-run counts as started once the old failed ids disappear, so the watch can report CI passed without the re-run's result
   bug-652-pr-462	#652	#462 (#461)	A 0644 fake opencode doesn't stop the PATH search, so the test can start a real OpenCode session
   bug-1153-pr-855	#1153	#855 (#818)	observe() re-renders the whole Inbox every second, even with nobody watching
   bug-1105-pr-861	#1105	#861 (#826)	Stage rows come from a BTreeSet<String>, so they sort by bytes, not in the order a Run goes through its stages
   bug-947-pr-860	#947	#860 (#821)	allowed_emails accepts any entry with an @ and no whitespace
   bug-1084-pr-1053	#1084	#1053 (#987)	The 64 KiB tail window is reused for OTLP traces, whose events are larger, so the latest tool call can fall outside it

   Notes:

   • Each task's base is the first parent of its PR's merge commit, and its change is the PR head. Both were checked against git.
   • .thirdshift-issue.md is the originating issue as it stood at merge, plus its parent Spec (Spec: the Console, a web page for each machine's Commands #776 or Spec: Session traces, OTLP JSON Lines in place of Session logs #700) where it has one, as the imported tasks do.
   • For thirdshift console uses 50-74% of a core while idle #1153, the triage table's "authorization every 250 ms" clause isn't in Keep the Console Inbox live #855's diff; it arrived in Add Console accounts and sign-in #860. That criterion lists it as a near-miss, not part of a catching finding.
   • The five partly visible candidates stay out.
6. JacobStephens2

   closed this as completedon Oct 25, 2026