- Make owner confirmation lists what happens (sleeps, share links stop, the
disk goes with it, shared mode for good), stays open while the workspace
goes to sleep, and shows a refusal in place.
- Whoever made the change is told whether the previous owner will see a notice.
- The previous owner gets a notice (until dismissed) advising them to rotate
personal secrets; the new owner is told once that it runs like a shared
workspace.
- "Owner changed" chip in the top bar and a line in the sidebar hover card.
- Audit log words Orca's "previous owner told" row, and a row cut short shows
its whole sentence on hover (AUDIT-TRUNC-HOVER).
* feat(cloud): EP-10 delete a team whose plan is set to end: the dialog says it ends now with no refund; a failure after the plan ended says so and offers to try again
* fix(cloud): EP-10 delete dialog copy (design-squad)
* chore(cloud): EP-10 sync protected-copy keys for the delete dialog's new lines
* fix(cloud): EP-8 Delete of a running sandbox this computer can't reach (revoked pairing) goes through Orca Cloud with Force delete, never waits silently
* fix(cloud): EP-8 refusal copy says sandbox and this computer (design-squad)
Stripe's portal on API 2025-09-30.clover cancels by setting cancel_at, not cancel_at_period_end,
so billing never saw the cancellation: no 'Plan ends', no grant end. The mirror now stores
cancel_at (migration 0009); cancel_at_period_end is the 'cancelling' flag for either form; grants
end at cancel_at; entitlements carry cancelAt; the desktop's 'Plan ends' uses it.
Test: two teams of one owner (separate customers), one cancels via cancel_at: its own plan shows
ending on that date, the other is untouched; un-cancelling clears it.
* fix(skills): accept share links on the build's configured artifacts origin (EP-2)
A build signed in to staging publishes share-staging links, which the
install dialog rejected. The parser now also accepts the exact artifacts
origin this build resolves; production hosts are unchanged.
* fix(skills): declare shareLinkOrigins on SkillsApi
The Worker reads environment-build.sh's own lines from the stored build log at finalize and records
autoInstall { manager, outcome } in the build result (no image change). The build view carries it;
the environment page shows 'Dependencies installed (pnpm)' or that the install failed and workspaces
run their own setup.
* wip(cloud): PARITY-FOLLOW design fixtures (top-bar followers, sidebar Team and Following)
* feat(cloud): PARITY-FOLLOW phase 1: sidebar Team list and the top bar's people (creator and who is here now)
* test(cloud): PARITY-FOLLOW fixtures name the workspace a teammate is in
* fix(cloud): PARITY-FOLLOW fixture typecheck
* feat(cloud): PARITY-FOLLOW follow endpoint: workspace_follows (0055), PUT/DELETE /v1/team/workspaces/:id/follow, followers in workspace views
* fix(cloud): PARITY-FOLLOW lint: the hover action's wrapper owns its visibility; no Button restyles; no side effect in a state updater
* feat(cloud): PARITY-FOLLOW phase 2: Follow in the top bar, followers in the stack, Following section in the sidebar
* test(cloud): PARITY-FOLLOW no real-time wait in the live-read test
* feat(cloud): SSO-FOLLOWUPS members managed by the identity provider on the Team page; a clear message when single sign-on ends a sign-in
* fix(cloud): import the roster type where it is used
* feat(cloud): wording for single sign-on and directory sync events in the audit log
* fix(cloud): the missing-DNS-record audit line reads as an action (design-squad)
Conductor's cloud runs Amazon Linux; Orca's sandboxes Ubuntu. The Conductor importer now rewrites
the setup's own dnf/yum install lines to apt-get when every package has a clear Ubuntu name, and
leaves anything else as written. A script file the setup runs is only read (never changed or run)
to list its dnf lines. The setup-script review and the environment import show 'Uses dnf' with
what changed or the lines to check.
* feat(cloud): ENTERPRISE-SSO Settings › Enterprise single sign-on and directory sync, driven by server state
* feat(cloud): key icon on the single sign-on group title (TEAM-DIALOG-2)
* fix(cloud): Contact us in the SSO block is a plain button; Copy link is for sign-in surfaces
* test(cloud): the copied SSO setup link is minted like the opened one and never logged
* fix(cloud): design-squad review of the SSO blocks (sentence-case chips, directory sync icon, grace and last-change wording)
* fix(cloud): sentence-case success badge variant for the SSO chips; catalog matches the new copy
* fix(cloud): register the Enterprise IPC handlers with the team handlers (file line limit)
* feat(cloud): every setup notice line has plain words and a real action, or doesn't show (ENV-NOTICE-ACTIONS)
- Doctor checks that reached the bare 'check' line now classify: low disk ('disk')
and a missing repo tool ('tool') get their own plain words; disk.free without a
code and any check this desktop doesn't know are hidden, never a bare label.
- The push notice reads repo access plus the person's own gh rights on the repo
(new gitHubInstallRights IPC): Install on {owner} only where installing can
work, 'Copy request for an owner' once an owner was asked, Check again where
the App already reaches the repo, plain words for someone else's public repo
(octocat/Hello-World). Install no longer carries a Copy link.
* copy(cloud): a push nobody here can install offers Copy request for an owner (design-squad, ENV-NOTICE-ACTIONS)
* fix(cloud): ENV-NOTICE-ACTIONS rebase onto AUTH-ONLY-COPY-LINK: the owner request takes the install page from the repo-access answer
A GitHub App user token generally can't read orgs the App isn't installed on, which is
exactly when canInstall is asked. Read the owner type anonymously first (GET /users/{owner}):
another user's account is false; an org is true only for active admin, false for another
role/state, and null for 403/404/errors/timeouts. Owner-type lookup failures are null.
Present while the Orca GitHub App isn't installed for the repo owner ('missing', or
'public' with no installation). true: the caller's connected GitHub login is the owner,
or their membership in the owner org is active admin. false: member, non-member (403/404),
or another user's account. null: no connected GitHub user token, the token can't be read
or refreshed, or GitHub errored / timed out (3 s). Never fails the answer.
The token comes from memberGitIdentity (decrypt + refresh near expiry).
* feat(cloud): COPY-LINK-FIRST-CLICK Copy link on the first Sign in and setup's first Continue in browser starts the same flow without opening the browser
* feat(cloud): COPY-LINK-FIRST-CLICK loopback sign-in links say they open in any browser on this computer (menu line and copied toast)
* fix(cloud): COPY-LINK-FIRST-CLICK Copy link stays on sign-in only; the choose-plan Continue in browser has no copy link
NO-ROW: a create with no project here yet (GitHub-only Orca Cloud) now has its pending row
atop the list when grouped by project too (it got a blank 'repo:' section before). While it
opens, openCloudWorkspace reports the server it pairs to (onHost); the sidebar hides that
server's rows until the hand-off removes the pending row, both in one store update, so the
workspace never shows twice.
CANCEL: createSandboxWithProgress (owned and GitHub-only creates) deletes what a cancel
leaves: cancelled in flight, it replays the create by its Idempotency-Key and deletes the
sandbox the control plane hands back (reclaimCancelledCreate, retrying while the first is
still in progress); cancelled just as it answered, it deletes it. A cancelled clone already
deleted itself. The GitHub runner deletes the sandbox when Cancel lands before or during
Open workspace (which also drops this computer's pairing), and cancel's 'Deleting the
sandbox…' waits for it. Copy link moves to cloud-workspace-share-link.ts (re-exported) to
keep open-cloud-workspace.ts within max-lines.