Repository navigation
Commit 3173e44
fix: offer Altimate Base to every user on an implicit free Zen default (AltimateAI#1302)
* fix: offer Altimate Base to every user on an implicit free Zen default
Closes AltimateAI#1301.
The 0.11.0 migration to Altimate Base only fired when `opencode/big-pickle` was
in persisted `recent`, which only a picker writes. 1,027 of 1,031 Big Pickle
machines were implicit-default users with no `recent`, so on 0.11.x they were
silently rerouted to the next public free Zen model (`nemotron-3.5-lightning-free`)
and never offered Base.
TUI (`packages/tui`)
- `usesImplicitFreeDefault()`: eligibility is now "launch default resolves to a
free public OpenCode Zen model (Big Pickle included), no explicit selection,
no project provider allowlist", judged on `fallbackModel()` so a restored
session model is never mistaken for the default.
- One startup decision in `app.tsx` replaces the two racing effects: prior
decline → skip; registered Base → migrate silently; returning user (prompt
history at startup, project sessions, or a recent model) → migration
disclosure; a brand-new user keeps the first-run welcome picker. A
`dialog.replace()` that loses a race falls through instead of latching.
- Escape / Ctrl-C on the migration disclosure now routes through the close
guard to the same path as explicit No: the decline is persisted AND the
provider picker opens, instead of stranding the user on the retired model.
- Migration copy names the actual free model being moved.
- Telemetry: `altimate_base_confirm_shown` / `altimate_base_choice` /
`altimate_base_register_result` now fire for the migration origin (they were
gated on the first-run funnel, so the migration was invisible), with an
`origin` field.
- `PromptHistory` exposes `loaded()` and a one-time `hadHistoryAtStartup()`.
Server (`packages/opencode`)
- `Provider.defaultModel()` and the ACP default scan: a registered Altimate Base
now outranks the keyless public Zen tier (`options.apiKey === "public"`) and
nothing else; a keyed Zen account or any BYOK provider still wins. Headless
hosts (`serve` behind the VS Code extension) therefore land on Base once the
install is registered.
Tests: `test/context/local.test.ts` (free-Zen detection, eligibility,
recents rewrite), `test/cli/tui/dialog-altimate-base.test.tsx` (migration
telemetry without first-run, Escape → decline + picker, generalized copy),
`test/provider/provider.test.ts` and `test/acp/default-model.test.ts` (public
tier vs keyed Zen vs registered Base, recents precedence unchanged, Big Pickle
never migrated headlessly).
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_012uzYijGHdhxvpUzhgWxayo
* fix: wrap two remaining hunks in altimate_change block markers
The marker guard in CI (with the upstream remote present) flagged two spans
that only had single-line marker comments over multi-line code.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* chore: drop the upstream product name from five AltimateAI#1301 comments
The branding leak audit in CI flags the upstream product name in a
single-line-marked test comment; the other four were inside marker blocks
but are reworded too so none can surface later.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: address review feedback on the Altimate Base default migration (AltimateAI#1302)
Inline findings from Cursor Bugbot, CodeRabbit, cubic, and two Codex passes.
TUI
- startup decision waits for kv hydration and treats a refusal in either store
(kv key or model.json flag) as a decline
- disclosure copy and the Big Pickle predicate use the launch default, never a
restored session's model
- accept path captures the launch default on mount and passes it to
migrateLegacyDefault({ from }); after registration the re-check keeps only
the explicit/allowlist guards and requires the fallback to be unchanged or
Base, so a registered provider sorting first cannot route to the picker and
a paid provider appearing mid-dialog cannot be migrated
- cleanup persists a decline only for an observed dismiss; Ctrl-C is an
"interrupt" that closes without deciding; programmatic closes emit no
cancel telemetry
- usability (useReady / prompt gate) judges the current model with the
current explicit marker, includes an older picker-written free recent, and
recent-model cycling marks the pick explicit
- prompt history excludes appends that race the startup read from the
returning-user snapshot
- persistence: every outstanding model.json write is tracked; tests await the
real writes instead of sleeping
Server
- public Zen tier is demoted only when options.apiKey === "public" and no key
is configured; fixtures discriminate the two cases
- ACP re-reads model.json (recents + decline) at each default selection
- own-property checks on recents so prototype-name ids cannot throw
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: queue prompt-history writes until the startup read settles; complete markers
- prompt/history.tsx: appends during the startup read update the in-memory
store immediately but defer the file write until the read has captured
hadHistoryAtStartup, so a racing append can never flip the returning-user
signal either way; the read merges with entries appended this launch
instead of overwriting them
- wrap four spans that only had single-line markers over multi-line code
(the marker guard diffs committed HEAD, so these surfaced only in CI)
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: address remaining bot findings on PR AltimateAI#1302 (prompt-history write race, migration telemetry, model cycling, test state isolation)
TUI
- prompt/history.tsx: serialize the startup rewrite and every append's write through one FIFO
write queue (`queueWrite`), so a racing append can no longer be clobbered by a still in-flight
startup flush; also enforce the no-consecutive-duplicate and MAX_HISTORY_ENTRIES cap invariants
when merging startup-read history with entries appended during the read
- altimate-onboarding.tsx: track an explicit `chosen` flag set only inside `no()`/`yes()`, so the
unconditional `onCleanup` fallback no longer records `altimate_base_choice` telemetry for a bare
process exit / top-level quit (previously misread as a decline because `lastCloseReason` stayed
`undefined`, which the old check treated the same as an actual dismissal)
- altimate-onboarding.tsx: snapshot `launchDefaultDisplay` alongside `launchDefault` once, at
mount, instead of reading the live `fallbackModel()`-backed memo from JSX, so the migration
disclosure cannot rename itself mid-dialog once `yes()`'s registration moves the live default
- local.tsx: `fallbackModel()` now honors a valid, still-allowed `explicitDefault` before falling
through to `recent`'s order, so `cycle()`'s deliberate-pick marker (which intentionally does not
reorder `recent`) is reflected as the actual launch default on the next launch instead of
silently reopening the migration dialog
- ui/dialog.tsx: fix stale comments that still described Ctrl+C as behaving "same as Escape" after
Ctrl+C was split into its own "interrupt" reason that deliberately records no decline
Tests
- Global.Path.state gets the same OPENCODE_TEST_HOME-style test-isolation override `home` already
had (via OPENCODE_TEST_STATE_HOME), plus a shared `withTestStateHome` helper in
test/fixture/fixture.ts; applied to every test in service-session.test.ts, default-model.test.ts,
and provider.test.ts that previously read/wrote the real model.json directly, which raced other
test files and risked clobbering real developer state if a run was killed mid-write
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Co-Authored-By: Claude <[email protected]>
* fix: close the altimate_change marker after append()'s closing brace
Co-Authored-By: Claude <[email protected]>
* fix: only flip prompt-history loaded() after the startup flush settles (AltimateAI#1302 critical finding)
- history.tsx: `setLoaded(true)` used to fire before the startup rewrite was even kicked off,
so a racing append could queue behind (or, before the previous commit's serialization, race)
a flush that hadn't landed on disk yet. `loaded()` becoming true now guarantees this launch's
startup flush, if one was needed, has actually settled — not merely "kicked off, and safe only
because nothing else raced it yet."
- history-startup-race.test.tsx: new regression test asserts the disk content the INSTANT
loaded() flips, with no separate `await flushed()`, unlike the pre-existing tests written
before `loaded()` implied this.
Comment thread: AltimateAI#1302 (comment)
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: round 6 bot review findings on PR AltimateAI#1302 (history race, cross-surface default divergence, kv-ready gate, stale close reason, onboarding skip)
TUI
- prompt/history.tsx: the startup flush and append()'s trimmed-rewrite branch now snapshot
`store.history` to a string SYNCHRONOUSLY at enqueue time (`serializeHistory`), instead of
reading it lazily from inside the queued write closure. Combined with removing the earlier
`await` before `setLoaded(true)`, all three steps (snapshot, enqueue, flip loaded()) run with
no await between them: an append that already ran is already in the snapshot and writes
nothing itself (persisted exactly once, by the flush); an append that runs after sees
`loaded() === true` and queues its own write behind the flush (persisted exactly once too).
This closes both a dropped-append bug (from awaiting the write before setLoaded) and a
duplicate-entry bug (from the lazy read) at once.
- context/local.tsx: reverted the `explicitDefault`-before-`recent` precedence in
`fallbackModel()` — it made the TUI and headless/ACP resolve different launch defaults from
the same `model.json` after a cycle, since the server never reads `explicitDefault`, and let a
malformed `explicitDefault` (prototype-name `modelID`) poison the TUI default ahead of
`recent`'s own validity checks. `cycle()` now passes `{ explicit: true, recent: true }` so the
cycled model moves to the front of `recent` instead — the single source of truth for TUI,
`Provider.defaultModel()`, and ACP alike.
- context/local.tsx: `hasUsableFreeDefault()` no longer reads the kv migration-decline key
before `kv.ready` — an unready kv now reads as undecided (assumed usable) instead of "not
declined", so the prompt gate can no longer discard a submitted prompt during kv hydration.
- context/local.tsx / app.tsx: extracted `shouldSkipOnboardingAtStartup` — app.tsx's startup
effect no longer latches "no onboarding needed" off a same-launch setup (an impatient
first-run user picking a free model before the effect settles), which used to skip the
`onboardingReady()` branch's funnel telemetry and scan gate entirely for that case.
- component/altimate-onboarding.tsx: the close guard no longer records `lastCloseReason` for a
dismiss vetoed by `busy()` (registration in flight) — that stale reason could otherwise survive
into an abrupt teardown and make `onCleanup`'s fallback persist a decline nobody made. Also
corrected two comments that still described Ctrl+C as behaving like Escape/dismiss.
Server
- acp/service.ts: corrected a stale module comment that contradicted the recents loop it sits
above — a persisted Big Pickle recent IS honored (matching `Provider.defaultModel()`), only the
implicit scans exclude it.
Tests
- history-startup-race.test.tsx: two new regression tests — an append landing before loaded()
flips, and one landing while the startup flush is still in flight — both assert exactly-once
persistence with an explicit no-duplicate-lines check.
- local.test.ts: new tests for cycle()-via-recents-order, the kv.ready gate, and the
onboarding-skip discriminator.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: keep the app.tsx local.tsx import single-line for the marker guard
Co-Authored-By: Claude <[email protected]>
* fix: Codex HOLD findings on PR AltimateAI#1302 (kv-ready pending direction, cycle() stability, history race test rigor)
1. kv.ready gate direction (local.tsx, altimate-onboarding.tsx, component/prompt/index.tsx):
`hasUsableFreeDefaultGated` previously treated an unready kv as "assume usable" (`true`) — the
wrong direction. With delayed kv hydration, `--prompt` or a fast manual submit could pass
`useReady()` and submit to the implicit public Zen model before onboarding/migration ever ran.
It now reports `"pending"` (genuinely undecided), not a boolean guess either way. Every
consumer of `useReady()` except the prompt submit gate collapses `"pending"` to `false` (the
same conservative default as before kv.ready-awareness existed). The submit gate gets a new
`useReadyPending()` seam: a submit attempted while pending defers (keeps the typed prompt,
opens nothing) and is automatically retried via a `createEffect` once kv resolves either way —
sent if it turns out usable, discarded (matching the normal picker-reopen path) if not.
2. cycle() traversal stability (local.tsx): passing `{ recent: true }` (round 6, fixing a
cross-surface TUI/server default divergence) broke `cycle()`'s own navigation — reordering
`recent` on every pick meant the next press read its index off a list that had just reshuffled,
bouncing between two models instead of visiting every one. `cycle()` now captures its
traversal order once, lazily, into a separate `cycleOrder` snapshot that stays stable across a
whole cycling sequence (re-captured only if the current model falls out of it, e.g. an
unrelated explicit pick) — while still persisting every pick to the front of `recent` via
`selectModel(..., { recent: true })`, so cross-surface consistency is unaffected.
3. History startup-race test rigor (history-startup-race.test.tsx): the two round-6 regression
tests polled `loaded()` via `Bun.sleep`, which does not reliably keep the startup write "in
flight" — confirmed they passed even against the dropped-append bug they were meant to catch.
Replaced with three barrier-controlled tests using `spyOn(persistence, "readText"/"writeText")`
against manually-resolved deferred promises: append while the read is pending, append while
the rewrite's write is still gated/in-flight (FIFO ordering), and append synchronously in the
same reactive tick `loaded()` flips (the precise shape that reproduces the lazy-snapshot
duplicate bug). All three were confirmed to fail against the relevant old behavior and pass on
HEAD before being kept.
New tests: cycle-stability.test.tsx (calls the real cycle() three times, asserts the visited
sequence — verified fails against the pre-fix bounce), ready-pending.test.tsx (the defer/retry
mechanism, verified against both the "sent early" and "usable" directions).
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: scope the shouldSkipOnboardingAtStartup discriminator to a genuine first-run completion
cubic (3986532221) correctly flagged this as a regression introduced by the round-7
shouldSkipOnboardingAtStartup fix, not a pre-existing follow-up: `setupComplete()` is a global
flag set by ANY model selection (`markSetupComplete()`, called from `DialogModel` on every pick),
not only a first-run/impatient-picker completion. A RETURNING user (e.g. an existing Big Pickle
user) who did an ordinary `/model` switch while app.tsx's startup effect was still settling made
`setupComplete()` true too, falling through to the `onboardingReady()` branch and firing
`onboarding_started`/`onboarding_completed`/`scan_gate_shown` telemetry plus `openScanGate()` for
a routine model change — not a genuine first run.
Fix: `firstRunOpenedThisLaunch` (altimate-onboarding.tsx) is a new one-way latch, set only when
the first-run picker actually opens THIS launch — app.tsx's own startup fallthrough, or the
prompt gate's equivalent (component/prompt/index.tsx now calls `markFirstRunActive()` there too,
closing the gap cubic named explicitly). app.tsx's `shouldSkipOnboardingAtStartup` call site now
passes `setupComplete() && firstRunOpenedThisLaunch()` instead of the bare global flag — true
only for a genuine same-launch first-run completion, so a returning user's routine switch reads
false and keeps skipping exactly as before this whole discriminator existed.
Tests: two new tests in local.test.ts exercise the real production signals
(markSetupComplete/markFirstRunActive/firstRunOpenedThisLaunch) against the actual discriminator
computation app.tsx performs — a returning user's routine switch must skip (no telemetry, no
scan gate), a genuine first-run completion must not skip. Confirmed the second test fails when
the `firstRunOpenedThisLaunch` latch is temporarily removed, then passes again restored.
Removed the corresponding item from tracking issue AltimateAI#1303 (fixed directly, not deferred).
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: Codex re-review round 8 (cycleOrder staleness, ready-pending test coverage)
1. cycleOrder goes stale after an external recents change (local.tsx): the round-7 fix
(cycleOrder, re-captured only when the current model fell out of the snapshot) still went
stale the moment a PICKER selection reordered `recent` without also knocking the current
model out of the old snapshot. Codex's repro: [A, B, C], cycle once, then pick D and A via
the picker -> recents [A, D, C, B]; A stays present in the stale [A, B, C] snapshot the whole
time, so the round-7 check never re-fires, and D stays permanently unreachable by cycling.
Fixed with a `recentsVersion` counter (bumped by a new `setRecent` wrapper — the only path
that writes to `modelStore.recent` now) and a `cycleOrderVersion` on the cycle() closure:
cycle() re-captures whenever the live version has moved past what it last saw or resynced to,
which happens for ANY external write, picker included — while resyncing after its own write
so repeated presses with nothing else interleaved keep reusing the same stable snapshot.
Regression test: extended cycle-stability.test.tsx's existing "stable order" scenario with
Codex's exact repro (pick D and A via the picker after cycling once, assert D becomes
reachable and the re-captured order stays stable afterward). All three tests in that file now
share one mount via beforeAll/afterAll rather than each mounting independently — a second or
third independent heavy provider-tree mount in this file was found to reproducibly hang during
its own bootstrap (a test-infrastructure resource-contention issue, worse the more work a
prior mount did, unrelated to anything under test) — chaining the scenarios onto one shared,
stateful mount sidesteps it while still exercising the real cycle() end to end. Confirmed the
new assertion fails (D never reachable, times out) against the round-7-only invalidation
check, and passes on HEAD.
2. ready-pending.test.tsx exercised a hand-rolled reimplementation of the defer/retry shape
instead of production code, so reverting the real fix in component/prompt/index.tsx left it
passing regardless. Extracted `createDeferredRetry` (packages/tui/src/util/signal.ts) — a
small, generic, reactive defer-then-retry primitive — and made both prompt/index.tsx's submit
gate and the test's harness call the SAME function. Confirmed the test fails (2 of 3 cases,
exactly the ones relying on automatic retry) when `createDeferredRetry`'s retry is temporarily
broken, and passes on HEAD once restored.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: wrap createDeferredRetry in altimate_change markers
Co-Authored-By: Claude <[email protected]>
* fix: latch first-run only after a successful prompt-gate dialog.replace()
Bonus fix found by cursor (3986991408) and cubic (3987011218) re-reviewing the setupComplete fix
(ce0d3af) moments after it landed: `markFirstRunActive()` in the prompt gate's `!ready()`
branch fired unconditionally, before `dialog.replace()` even ran — including when
`dialog.replace()` loses a race to another dialog and returns `false` without opening anything.
That latched `firstRunOpenedThisLaunch`/`firstRunActive` for a picker nobody ever saw, so a
returning user's LATER, unrelated `/model` pick would look like a genuine first-run completion
and fire onboarding telemetry + the scan gate — the inverse of the bug ce0d3af was fixing.
Mirrors app.tsx's own identical, already-correct pattern for its own first-run fallthrough: check
`dialog.replace()`'s return value and only call `markFirstRunActive()` once it actually succeeded.
No new test: this is a direct application of an already-established, already-tested pattern
(app.tsx's own `shown` check) to a second call site; the fix was verified via typecheck and the
full test suite, not a new mount-based test — exercising the full submit path would need mounting
the whole `<Prompt>` component (session/workspace/editor/move dependencies), which this session
already assessed as disproportionate for a single conditional-latch fix.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: Codex re-review round 9 (onboardingReady() latch, deferred-submit staleness)
1. app.tsx's `onboardingReady()` branch (~783) had the same class of bug as the
`shouldSkipOnboardingAtStartup` branch above it (cubic 3986532221), just reached from a
different starting condition: a bare `setupComplete()` check. `onboardingReady()`
(`useReady()`) is also true via `connected()`, not only via `hasUsableFreeDefault()` — so a
returning user with a configured legacy default (e.g. Big Pickle) who switches `/model` to a
PAID model has BOTH of `shouldSkipOnboardingAtStartup`'s skip predicates false (a paid pick
isn't covered by either `hasExistingLegacySelection()` or `hasUsableFreeDefault()`), falls
through to this branch, and `onboardingReady()` is already true via `connected()`. If that
`/model` switch raced app.tsx's startup effect, `setupComplete()` alone read as true even
though no first-run picker ever opened, firing onboarding telemetry and the scan gate for an
ordinary provider switch. Fixed the same way as the branch above: require
`firstRunOpenedThisLaunch()` alongside `setupComplete()`.
Tests: two new cases in local.test.ts against the real production signals — both skip
predicates false and the latch false fires nothing; the latch true still fires.
2. A deferred submission could include later, unrelated edits: defer prompt A (kv/readiness
still pending), edit the box to B without pressing Enter again, readiness resolves — B was
silently auto-submitted, a send the user never asked for. `createDeferredRetry` (util/signal.ts)
now takes an optional `getRevision` that is snapshotted at `.defer()` time and compared
against the live value right before the retry would fire; a mismatch cancels the retry
entirely instead of firing against stale state. component/prompt/index.tsx's submit gate
passes `unwrap(store.prompt)` (text + attachments) as the revision.
Test: ready-pending.test.tsx's harness passes `getRevision` through the same shared primitive;
new cases assert an edited-while-deferred submission is silently canceled (not auto-sent), and
an unedited one still sends normally. Confirmed the edited case fails (B gets auto-sent) when
the revision check is temporarily removed from `createDeferredRetry`, and passes restored.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: don't discard the typed prompt when the prompt-gate picker fails to open
Real data-loss bug caught by cursor (3987148590) and cubic (3987174889) moments after the
previous fix landed: when `dialog.replace()` loses a race to another dialog (e.g. a
close-guarded one — a deferred submit's automatic retry can hit this path directly, bypassing
the focus check a manual Enter press would go through) and returns `false`, the previous fix
correctly skipped `markFirstRunActive()` but still fell through to clear the input, extmarks, and
prompt store — silently discarding whatever the user just typed even though no picker ever
opened to explain why.
Mirrors app.tsx's own identical `shown` check fully now: return immediately on `!shown`, before
touching anything, same as app.tsx's own `if (!shown) return`. The user can just submit again
once whatever is blocking the dialog clears.
No new test: exercising this exact race (a close-guarded dialog specifically vetoing
`dialog.replace()`) would need mounting the full `<Prompt>` component with a real `DialogProvider`
and a second, close-guarded dialog already open — the same mount-cost tradeoff already assessed
and declined for the sibling fixes in this same function. Verified via typecheck and the full
test suite.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: fold cycle-stability tests into one, isolate state dir from real Flock lock artifacts
This repo's rule is no order-dependent or resource-contention-prone tests; both cubic findings
on cycle-stability.test.tsx are in scope:
1. The three sequential `test.serial` blocks sharing one `beforeAll`/`afterAll` mount made the
third test depend on mutations the first two produced — running it alone (a `-t` filter or
`--only-failures`) failed. Folded into ONE `test()` over a single local mount, with five
labelled phases (a small `phase()` helper wraps each block so an assertion failure's message
names exactly which stage failed) covering the same ground as before: stable traversal order,
persisting picks to the front of `recent`, picker-driven staleness/re-discovery, and stable
re-traversal afterward.
2. `kv.tsx`'s `Flock.withLock` lock directory is derived from `Global.Path.state`
(packages/core/src/global.ts), which had no test-isolation override at all — only
`Global.Path.home` did. The test's `kv.json` FILE itself was always correctly isolated via
`paths.state` (TestTuiContexts), but the LOCK it takes while reading/writing that file was
not, so it could still touch the real, current developer's global state directory. Added an
`OPENCODE_TEST_STATE_HOME` override to `Global.Path.state` (mirroring `Global.Path.home`'s
existing `OPENCODE_TEST_HOME` pattern, already used throughout this codebase's tests), and
made `Flock.setGlobal` take a getter over `Path.state` instead of a frozen snapshot — `Flock`'s
lock root was captured once at this module's import time, before any test's own setup code
could set the env var, so a plain override on `Path.state` alone would not have been enough.
The test now sets/restores this env var around its mount.
Verified empirically: before this fix, this test's own runs left new (and orphaned, if killed
mid-run) `.lock` directories in the real `~/.local/state/altimate-code/locks` — confirmed via the
directory's own mtime changing across a run with the fix temporarily reverted, and staying
untouched with it applied. Also confirmed via typecheck (packages/core, packages/tui,
packages/opencode) that the getter-based `Flock.setGlobal` argument still satisfies `FlockGlobal`'s
type.
Removed both items from tracking issue AltimateAI#1303 (fixed directly, not deferred).
Co-Authored-By: Claude Fable 5.1 <[email protected]>
* fix: snapshot the deferred-submit revision serialized; share the onboardingReady() predicate; re-defer test; orphan marker
- util/signal.ts: `createDeferredRetry` captured `getRevision()` by reference. Solid's
`unwrap` returns the store's raw underlying object, the same one later edits mutate in
place, so the defer-time value and the retry-time value were one object and an edited
prompt was still auto-sent. The defer-time revision is now stored serialized and the
live value is serialized again before retrying (cursor 3987286236, cubic 3987320771).
ready-pending.test.tsx's harness now hands the primitive one live mutable object, the
production shape; its edited-while-deferred test fails on the old primitive.
- ready-pending.test.tsx: the "re-deferred" test now actually re-defers (Enter twice while
pending) and asserts exactly one send (kilo 3987319604).
- context/local.tsx + app.tsx: the onboardingReady() branch's discriminator is an exported
`shouldFireFirstRunFunnelAtStartup` that app.tsx calls and local.test.ts tests, instead
of an expression the tests re-derived.
- app.tsx: remove an orphan `// altimate_change end`.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
---------
Co-authored-by: Claude Fable 5.1 <[email protected]>1 parent 463b89c commit 3173e44
27 files changed
Lines changed: 3511 additions & 327 deletions
File tree
- docs/docs
- configure
- reference
- packages
- core/src
- opencode
- src
- acp
- altimate/telemetry
- global
- provider
- test
- acp
- fixture
- provider
- tui
- src
- component
- prompt
- context
- prompt
- ui
- util
- test
- cli/tui
- component
- context
- prompt
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
68 | 68 | | |
69 | 69 | | |
70 | 70 | | |
| 71 | + | |
71 | 72 | | |
72 | 73 | | |
73 | 74 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
57 | 57 | | |
58 | 58 | | |
59 | 59 | | |
60 | | - | |
61 | | - | |
| 60 | + | |
| 61 | + | |
62 | 62 | | |
63 | 63 | | |
64 | 64 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
33 | | - | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
34 | 42 | | |
35 | 43 | | |
36 | 44 | | |
37 | 45 | | |
38 | 46 | | |
39 | | - | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
40 | 61 | | |
41 | 62 | | |
42 | 63 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
34 | 34 | | |
35 | 35 | | |
36 | 36 | | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
37 | 45 | | |
38 | 46 | | |
39 | 47 | | |
| |||
61 | 69 | | |
62 | 70 | | |
63 | 71 | | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
64 | 75 | | |
65 | 76 | | |
66 | 77 | | |
| |||
110 | 121 | | |
111 | 122 | | |
112 | 123 | | |
| 124 | + | |
| 125 | + | |
| 126 | + | |
113 | 127 | | |
114 | 128 | | |
115 | 129 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
805 | 805 | | |
806 | 806 | | |
807 | 807 | | |
808 | | - | |
809 | | - | |
810 | | - | |
811 | | - | |
812 | | - | |
813 | | - | |
814 | | - | |
815 | | - | |
816 | | - | |
817 | | - | |
818 | | - | |
819 | | - | |
820 | | - | |
821 | 808 | | |
822 | 809 | | |
823 | 810 | | |
| |||
846 | 833 | | |
847 | 834 | | |
848 | 835 | | |
849 | | - | |
| 836 | + | |
| 837 | + | |
| 838 | + | |
| 839 | + | |
850 | 840 | | |
851 | 841 | | |
852 | 842 | | |
| |||
856 | 846 | | |
857 | 847 | | |
858 | 848 | | |
| 849 | + | |
| 850 | + | |
| 851 | + | |
| 852 | + | |
859 | 853 | | |
860 | 854 | | |
861 | 855 | | |
| |||
869 | 863 | | |
870 | 864 | | |
871 | 865 | | |
| 866 | + | |
| 867 | + | |
| 868 | + | |
| 869 | + | |
| 870 | + | |
| 871 | + | |
| 872 | + | |
| 873 | + | |
| 874 | + | |
| 875 | + | |
872 | 876 | | |
873 | 877 | | |
874 | 878 | | |
| |||
882 | 886 | | |
883 | 887 | | |
884 | 888 | | |
885 | | - | |
886 | | - | |
887 | | - | |
| 889 | + | |
| 890 | + | |
| 891 | + | |
| 892 | + | |
| 893 | + | |
| 894 | + | |
888 | 895 | | |
889 | | - | |
| 896 | + | |
| 897 | + | |
| 898 | + | |
| 899 | + | |
| 900 | + | |
| 901 | + | |
| 902 | + | |
| 903 | + | |
| 904 | + | |
890 | 905 | | |
891 | 906 | | |
892 | 907 | | |
| |||
901 | 916 | | |
902 | 917 | | |
903 | 918 | | |
904 | | - | |
905 | | - | |
906 | | - | |
907 | | - | |
908 | | - | |
909 | | - | |
| 919 | + | |
| 920 | + | |
| 921 | + | |
| 922 | + | |
| 923 | + | |
| 924 | + | |
| 925 | + | |
| 926 | + | |
910 | 927 | | |
911 | 928 | | |
912 | 929 | | |
913 | 930 | | |
914 | 931 | | |
915 | 932 | | |
916 | | - | |
917 | | - | |
918 | | - | |
| 933 | + | |
| 934 | + | |
| 935 | + | |
| 936 | + | |
| 937 | + | |
| 938 | + | |
| 939 | + | |
| 940 | + | |
| 941 | + | |
| 942 | + | |
| 943 | + | |
| 944 | + | |
| 945 | + | |
| 946 | + | |
| 947 | + | |
| 948 | + | |
| 949 | + | |
| 950 | + | |
| 951 | + | |
| 952 | + | |
| 953 | + | |
919 | 954 | | |
920 | 955 | | |
921 | 956 | | |
| |||
935 | 970 | | |
936 | 971 | | |
937 | 972 | | |
938 | | - | |
939 | | - | |
940 | | - | |
941 | | - | |
942 | | - | |
943 | | - | |
944 | | - | |
945 | | - | |
946 | | - | |
947 | | - | |
948 | | - | |
| 973 | + | |
| 974 | + | |
| 975 | + | |
| 976 | + | |
| 977 | + | |
| 978 | + | |
| 979 | + | |
| 980 | + | |
949 | 981 | | |
950 | 982 | | |
951 | 983 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1027 | 1027 | | |
1028 | 1028 | | |
1029 | 1029 | | |
1030 | | - | |
| 1030 | + | |
1031 | 1031 | | |
1032 | 1032 | | |
1033 | 1033 | | |
1034 | 1034 | | |
1035 | 1035 | | |
| 1036 | + | |
1036 | 1037 | | |
1037 | 1038 | | |
1038 | 1039 | | |
1039 | 1040 | | |
1040 | 1041 | | |
1041 | 1042 | | |
| 1043 | + | |
1042 | 1044 | | |
1043 | 1045 | | |
1044 | 1046 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
27 | | - | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
28 | 40 | | |
29 | 41 | | |
30 | 42 | | |
| |||
0 commit comments