OrchestKit after beta: what is next, in order

Rendered 2026-09-07 06:30Z. Latest release v10.0.0-beta.2. Milestone 164 closed last night; this page is the one that replaces it.
92
open issues (42 unmilestoned)
10
open bugs
9
open milestones, 1 overdue (Video, due 06-30)
0
written criteria for beta to 10.0.0 GA

🎯 The shape of the next quarter in one sentence

v10 is feature complete and shipping as beta. The road from here has one gate (say what GA means, then meet it), one debt pile (10 bugs, three of which bit this week), and three new product lanes you opened yesterday as milestones 165 to 167, which chain in a natural order: page-serve is infrastructure the glyph docs page needs, and both are cheaper than the commerce lane.

Analogy: the house is built and people are living in it (beta). Nobody wrote down what "finished" means, so the inspector cannot sign off. Meanwhile there is a list of dripping taps, and three extensions are drawn up, one of which is the hallway the other two open onto.

flowchart LR GA["🔥 1 GA gate\nwrite the criteria"]:::hot --> GA2["meet them\nbeta.N to 10.0.0"]:::wait B["2 bug burn-down\n10 open, 3 hit this week"]:::warn --> GA2 PS["3 page serve\n#3899 #3900 #3904"]:::indep --> GD["4 glyph docs page\n#3901 then #3902"]:::indep GD --> C["5 commerce agents\n#3896 #3897 #3898"]:::indep OM["6 old milestones\nretire or re-date 4"]:::dim classDef hot fill:#3a1414,stroke:#e06666,color:#fff classDef wait fill:#3a2a10,stroke:#f0b040,color:#fff classDef warn fill:#3a2a10,stroke:#f0b040,color:#fff classDef indep fill:#1b1b4a,stroke:#8f88f0,color:#fff classDef dim fill:#222,stroke:#666,color:#ccc

Where each lane stands today

1 GA gate
#3972 filed
2 Bugs (10 open)
0 of 10
3 Page serve (166)
0 of 3
4 Glyph docs (167)
0 of 2
5 Commerce (165)
0 of 3
6 Old milestones
75 of 120 closed

🔥 Lane 1: the GA gate. Write down what 10.0.0 means

What it is blocks GA 1 issue to write, then N to do

Analogy: beta says "the shape will not change". GA says "we stand behind it". The second needs a checklist, and there is none.

Measured: grep GA CHANGELOG.md finds only past product GAs (Fable 5, 1M context); no issue titled 10.0.0 GA at render time; release-please will happily emit beta.3, beta.4 forever. Update, same morning: the gate is now filed as #3972 in milestone 169 "v10.0.0 GA" with the five criteria below. Two things make GA different from another beta for this repo specifically. First, the stable channel: ork is pinned at 9.8.0 by design and bump-stable-pin has exited 3 on every prerelease since alpha.1, so GA is the first time in v10 that script does real work, for every consumer on the stable pin. Second, the consumer evidence from 08-31 (two users fled to bypass mode over the egress ASK storm, the 8x palette, an unguarded find -delete) lives in #1881 and was the reason for the purge; GA should re-ask those two users.

Proposed criteria, five lines, measurable

#CriterionHow it is checked
1Two consecutive betas with zero hook regressions filedgh issue list --label bug,hooks --search created:>beta.N-1 is empty
2The 10 open bugs triaged: fixed, or labelled wontfix with a reasonlane 2 below; count of unlabelled open bugs = 0
3bump-stable-pin.sh exercised once on a dry run against 10.0.0a CI job or a manual run with the exit code pasted into the GA issue
4The two 08-31 consumers re-run one session each on beta and report no ASK stormtheir words in #1881, not a claim
5claude plugin details ork reads 10.0.0 on a clean machine after plugin updatethe last step of the release checklist, pasted
What it means
One issue, five checkboxes, and beta becomes a countdown instead of a plateau.
If we do nothing
beta.3, beta.4, beta.12. Consumers on the stable pin stay on 9.8.0 indefinitely.

Lane 2: the bug pile, 10 open

What it is feeds the GA gate yesterday's Hebrew roadmap had the same theme: tools that lie

Analogy: ten dripping taps. Three of them soaked someone this week.

IssueWhatHitSuggested
#3894mcp-output-transform redacts claude-in-chrome tab ids as phone numbersblocked screenshot verification 3x last nightfirst
#3892alpha.67: subagent-stop/feedback-loop throws "Dynamic require of node:os"; review-pr fork reviews HEAD silently on a non-PR targeta crash and a silent wrong reviewsecond
#3936display-lint nudges on the exact shape it recommends when paths are longevery long command last nightthird, small
#3522flaky: skill-validation Test 6 asserts a hard 200 ms wall clockrandom CI redfix the assertion, not the runner
#3190bash 5.3 here-string deadlock past PIPE_BUF hangs the eval guard suiteknown, memory has the recipeapply the recipe
#3101playground mermaid breaks in non-default tabsgood first issueship with lane 4
#3684, #3780, #3667URL check follow-ups; pronoun targets; stamped counts in the repo descriptionlowone sweep PR or wontfix with a reason
What it means
Two real defects (#3894, #3892), one lint, one flake, six paper cuts. About a week of lanes.
If we do nothing
GA criterion 2 never clears, and the browser tools stay unverifiable.

Lane 3: page serve (milestone 166), the hallway

What it is infrastructure, unblocks lane 4 #3899 skill, #3900 retire the ad hoc pattern, #3904 editable images

Analogy: every session that wants to show you a page currently builds its own front door out of python3 -m http.server and a portless alias. Last night's session did it twice, and the door is still open (pid 30156). The skill makes it one call, with a screenshot and a cleanup.

What it means
#3899 is a two-day skill: register a portless route, print the URL, screenshot, clean up. #3900 deletes the pattern it replaces. #3904 can wait.
If we do nothing
Every glyph page keeps an orphan server behind it, and lane 4 has no delivery path.

Lane 4: the glyph docs page (milestone 167)

What it is docs, small #3901 one page, then #3902 one page per user-invocable skill

Analogy: last night was #3901 done by hand: a human asked "what is left", an agent drew it, and the page had to be served ad hoc. The issue is exactly that, but generated from SKILL.md so it never drifts, at a stable URL an agent can route a human to.

What it means
#3901 is one generator template plus a curated examples block; #3902 loops it over 106 skills and adds the drift test.
If we do nothing
"How do I use this" keeps getting answered in chat, per session, from scratch.

Lane 5: commerce agents (milestone 165)

What it is biggest, revenue-facing, least defined #3896 skill, #3897 catalog adapter contract, #3898 evals into ork:testing-llm

Analogy: the extension with the biggest floor plan and the fewest measurements. The contract (#3897) is the load-bearing wall; build it first or the skill (#3896) gets rebuilt twice.

What it means
Order inside the lane: #3897 contract, then #3896 skill against it, then #3898 evals. Two to three weeks, and it should start after lanes 3 and 4 so its pages have a delivery path.
If we do nothing
Nothing breaks. This is the one lane that is opportunity, not debt.

Lane 6: the old milestones, four of them need a verdict

What it is hygiene, one sitting
MilestoneOpen / totalStateSuggested
76 Video Gallery and Demos8 / 10due 2026-06-30, overdue 10 weeksdecide #2842 (extract demos repo) and either re-date or close the rest as parked
154 CC adoption1 / 372one issue left, #1848do #1848 (small) and close the milestone; CC watch continues as issues, not a milestone
95 Docs and Discoverability16 / 39alivefold #3901/#3902 in here or keep 167 separate; pick one home
104 Hook and Agent Quality21 / 63alive, now the bug lanedone: the open bugs were moved here the same morning; #3974 and #3894 fixed since
97 Memory System Hardening9 / 20quiet since Augustre-triage after GA
168 Sales dept content1 / 1hq-ext side, tracking onlyleave
What it means
Fewer open milestones with truer numbers; the bug lane gets a home.
If we do nothing
An overdue milestone and a 1-of-372 milestone keep reading as active work.

Suggested calendar

timeline title Next four weeks, if the order above holds week of 09-08 : GA gate issue written : bugs #3894 #3892 #3936 : milestones 76 + 154 decided week of 09-15 : page-serve skill #3899 + #3900 : remaining bug sweep : beta.3 week of 09-22 : glyph docs page #3901 : #3902 generator : beta.4, GA criteria 1 and 3 checked week of 09-29 : commerce #3897 contract : consumers re-run (criterion 4) : 10.0.0 if 1 to 5 hold

Dates are a proposal, not a commitment. One lane at a time is the floor rule that held last night; the calendar assumes it.

✅ Decide

Two forks. Pick one per block; the bar collects your answers as text.

D1. The GA gate
D2. First product lane to open after the bugs
(no picks yet)
0/2 chosen