OrchestKit: what is actually open

The repo is green and the PR queue is empty. Four calls are left, and every one of them is yours rather than mine.

01 · the number that looks bad is three different things

130 open issues is not 130 open problems

Split by who filed them and how old they are, the pile stops being one pile.

130 open issues, stacked by kind 44 robot 52 wish list 22 other 12 how old is each kind robot queue all filed this week, none survives 30 days wish list mostly older than a month, 23 past 90 days bugs not one older than 90 days
What it meansBugs get fixed here. The robot queue drains. Only the wish list piles up.
If we do nothingThe count keeps reading as debt and hides that bugs are healthy.
02 · the thing I almost got wrong

A check said "close all 36" and it could never have said anything else

It searched for the wrong field name, in a file that only holds two of the eighteen versions.

what the check looked in, versus what it claimed about the file it read version 2.1.238 version 2.1.219 2 drawers → claimed about 36 issues spanning 2.1.221 to 2.1.238 the field was named feature_slug, the probe asked for slug so the answer was empty before the data mattered a control proved the file never held those names at all 18 versions
What it meansAbsent from that file never meant done. The join key does not exist.
If we do nothingThe next pass repeats it and closes 36 issues on an empty answer.
03 · your call

What happens to the 39 untriaged adoption stubs?

A robot files one issue per new Claude Code feature. Nobody has answered 39 of them, and the file that records answers forgets them.

after you pick:

04 · your call

Keep hardening the egress guard, or retire it?

Today I fixed a false alarm in the guard. An open issue argues the same guard cannot see six of the seven things it claims to watch, and the operating system already blocks them.

after you pick:

05 · your call

The declared supported version is 21 releases behind the one you run

The support file says 2.1.220. You are running 2.1.241. A note in the file says the freeze was deliberate, dated 2026-06-20.

after you pick:

06 · your call

The memory index is close to the size where it stops being read

It is at 19.5KB against a 24.4KB limit. Past that, the file that tells every future session what it knows is silently truncated.

after you pick:


    

      
      
      
    

  


  

    
So what?

    
Nothing here is blocked on code. Every one of these is a call that only you can make, and three of them get more expensive the longer they wait.