mirror of
https://github.com/stablyai/orca.git
synced 2026-11-15 10:27:33 +00:00
Brennan Benson
7a44471331
* fix(native-chat): hold an automatic continue until the chat's account has usage again The automatic continue after a usage limit sent at the cut's reported reset without looking at the account, so it could send into a still-spent weekly window. Each sweep pass now attributes the chat's launch account (the host's launchAccountHome) to Orca's polled reading taken in that same home, and holds the send until the latest spent window's reset (+15 s). The hold is derived each pass, never saved, only grows for one cut and account, and waits up to two minutes for a reading taken since that reset before falling back to the reset it has. A spent window with no known reset stops the automatic continue for that cut; on System Default, where Orca can't tell which login a reading saw, a fresh reading with room releases both. Rows on desktop and phone show the held time through an optional continueAt; older clients keep the cut's time. * fix(native-chat): attribute usage holds once per account and retire them with their scope - C1/X7: launch home resolved once per provider and reading once per (provider, home) per pass; narrow usageReading accessor replaces getState(). - X8: forget() drops the hold; hidden-chat caches are pruned while the setting is off; readState stores nothing for an unattributed chat. - X3/C3: launch and reading homes compared in canonical form (~, dot segments, async realpath, bounded cache). - X4/C2: a hold belongs to its scope (canonical home + billing kind) and retires when it changes. - X2: a launch whose provider has no reading yet asks once and waits within the two-minute window. - X5: attribution runs before the overdue check, so a restart keeps the account's later reset. - X6: the launch account is re-attributed right before each send; beforeRun refuses a changed attribution. - C5: cold chats publish when their continue time moves. - X1/C4: WSL launches keep the cut's own reset (no hold). * fix(native-chat): gate held continues on an account scope token and stop reviving stale cuts - C6: a hold extends only with a spent window that had begun by the cut's reset. - X6-R2, X10, P1-1: a synchronous account scope token (selection, launch env, reading home and provenance) is captured at attribution; send() re-resolves only when it moved, memoized per token, and beforeRun compares live and captured tokens. Opening a chat drops only cold-cut caches. - X11: production tick() test at N=300 and 10N=3000 counts resolver and reader calls. - X2-R2: the bootstrap wait starts when a pass first sees the due send without a reading. - X9: canonical homes are resolved once per account per pass; the unbounded-lifetime cache is gone. - C5-R2: unloaded chats have no status push path, so the cold continueAt publication is removed. * fix(native-chat): separate continue eligibility from current spending and bind sends to their attribution's sources - X12: a cut's eligible anchor (its reset, an established hold, or a covering window) takes the 24 h overdue test; once eligible, every currently spent window holds the send. - X13/P1-2, X6-R3: the account owner returns attributions with a synchronous source witness (settings snapshot identity, cached login-shell capture revision, reading-source identity); Claude billing comes from the launch's own env composition. A result whose sources moved while it resolved is discarded; send() and beforeRun bind to the attribution's own witness and supersede without spending an attempt. - CI-1: the scope-token type assertion is gone with the token. * fix(native-chat): keep a covering hold beside spent windows of unknown reset - X12-R4 / C7: rebuilding the covering anchor skips spent windows whose reset, and so start, is unknown; the eligible branch still refuses on them. - E1-R4: the preparation-change and suspended-attribution race tests run on a Claude chat through the real host send, mutation and accepted settlement. * refactor(native-chat): move the usage-limit continue status into its own wire module The merge with main put agent-session-wire.ts one line over the 300-line limit. * fix(native-chat): read the shell capture revision lazily so module mocks without it still load Tests that main added mock login-shell-environment without the revision accessor, so binding it at module load failed. * fix(native-chat): release a usage hold on fresh room for any account without stranding the cut - QA-1: room in a fresh attributed reading newer than the last spent evidence (spentSeenAt) releases the hold and clears an unknown reset for every account; the System Default-only branch and identityKnown are gone. - QA-1b: the release pulls heldUntil down to that reading instead of clearing it, and an unknown-reset hold anchors on its last evidence, so a release over a day after the cut sends. * fix(native-chat): release an expired usage hold from its room reading and ask for readings while a reset is unknown - R6-1 / QA-1b-R6: a release sets heldUntil to the room reading itself, so an expired finite hold followed by an unknown reset no longer strands the cut. - R6-2: the usage poller idles while Orca is unfocused with no viewer, so an unknown reset asks for a non-forced reading at most every 10 minutes through the existing refresh. * fix(native-chat): bound unknown-reset readings per account and honor the failure backoff - R7-1 / X-R7-1: the rate-limit service owns the automatic-read cadence: a read waits while the provider's last reading or admitted automatic read is within the asked interval, so held chats on one account cause at most one unknown-reset read per 10 minutes. - R7-2: automatic reads wait out the poller's failure backoff (shared failureRetryDue) and start its clock; forced refreshes are unchanged. * fix(rate-limits): scope automatic usage-read admission to the selected account - R8-1 / X-R8-1: an admitted automatic read counts toward the cadence only for the account whose reading source the service held then, so a switch never lets one account's read delay another's. - Prunes the flaky-test-pattern baseline: service-refresh-orchestration no longer reads the wall clock. * fix(native-chat): keep a usage-reading request retryable until the service starts it, and show the last known reset while one is unknown * fix(native-chat): show no automatic continue while a chat waits on an unknown reset, since fresh room still releases it * fix(native-chat): publish no continue time for a cancelled or stopped cut while its account's reset is unknown