* fix(cloud): PAIRED-BADGE no "primary" badge or star on a cloud workspace's own row in the LIVE card; delete dead card header paths
#560 gated the badge in worktree-card-header.tsx, which only the unrendered
WorktreeCardParentContent used; the live card (default-workspace-card.json via the element registry)
drew PrimaryBadge/PrimaryStar with no cloud check, so a paired-from-birth row kept "primary". The
gate now sits in the template parts themselves (NotOnCloudRow, useIsCloudHostRow). Deleted the dead
header, parent content and meta row so a fix can't land there again.
* chore(cloud): PAIRED-BADGE drop the deleted meta row from the localization allowlist (path-literal ratchet)
* fix(cloud): PAIRED-ACCOUNT-FILTER paired workspaces are scoped by the account their pairing was made under
* perf(cloud): PAIRED-ACCOUNT-FILTER read the active account once per profile-index write, not per paired lookup
'How to push to GitHub' is now an OpenExternalSplitButton: its chevron copies GitHub's
guide (PUSH_TO_GITHUB_URL) without opening it. 'Contact support' sits in the More
menu, where a row can't carry the chevron, so a 'Copy support link' item sits right
below it, the same pattern as 'Copy GitHub link' under 'Add a GitHub repository…'.
The support URL moves to vm-build-repo-actions.ts (ORCA_SUPPORT_URL) next to the
GitHub guide's.
Neil (n39): Project "~" (a folder) with Run on = Orca Cloud opened a 256 px Agent menu
under the full-width field. The composer passed matchTriggerWidth only for a resolved git
repository that isn't a project group (upstream's rule), so a folder, a GitHub-only Orca
Cloud repo or a still-resolving cloud target fell back to min-w-64. The field is always full
width there, so the menu now always matches it (coordinator ruling). The right-aligned
'Not set up' labels are unchanged.
Waking card, owned and paired surfaces, the asleep view and the Sleep-failed toast spliced "This
workspace" into {{name}} templates ("Couldn’t wake This workspace", "Waking This workspace.").
cloud-workspace-name-copy.ts gives each sentence an unnamed variant ("Couldn’t wake this
workspace", "Couldn’t put this workspace to sleep", "Waking this workspace."…) and headings read
"Cloud workspace". Drops the two private fallback keys it replaced.
* fix(cloud): SLEEP-IN-PROGRESS (2/2) a paired cloud workspace shows the waking overlay, its sealed read-only copy with Wake to continue, and the saving state after Sleep
- PairedCloudWorkspaceSurface, mounted from OrcaCloudWorkspaceSurface for paired rows
- the same CloudWakingOverlay (Retry wakes through the control plane, billing copy included)
- asleep: the control plane's sealed snapshot via useCloudReadSnapshot + CloudReadSnapshotView
- Sleep marks a paired copy saving; re-read every 2.5 s until a new-enough copy, failed at the deadline
- useWakeOverlay moved to its own module (shared by owned and paired)
* fix(cloud): SLEEP-IN-PROGRESS (2/2) re-read the sealed copy through the window-visibility interval (recurring-timer ratchet)
Operator routes GET /v1/internal/secrets/kek and POST /v1/internal/secrets/rewrap
move every envelope-encrypted row (secrets, agent_credentials, github_user_tokens)
from a retired KEK to the active one: idempotent, resumable, conditional writes,
counts-only logs. A v2 row format behind SECRETS_SEAL_FORMAT=v2 (default v1)
keeps the KEK id out of the value layer's AAD so rotation re-wraps data keys
without decrypting values. Adds the KMS design doc.
* fix(cloud): SLEEP-IN-PROGRESS (1/2) a sleeping cloud workspace says it is saving its read-only copy until the copy is in, and says so if it never arrives
From the Sleep press until a copy at least as new as the press is read back, the row ("Going to
sleep · Saving copy…"), the asleep view and the Files pane show a saving state instead of their
"nothing was saved" lines or an older copy; the view polls every 2.5s meanwhile. No copy within 90s:
"Couldn't save a read-only copy. Your files are safe in the workspace." with Wake. Owned workspaces
(paired ones have no read-only view yet: 2/2). Copy and layout per design-squad.
* chore(cloud): SLEEP-IN-PROGRESS drop the two now-unused localization keys
Restart reaches a paired workspace's sandbox: main's restart resolves a bound pairing
(restartPairedOrNotCloud) and restarts it through the control plane, dropping the bound server's
dead connection so it reconnects, with the same waking > connecting > ready / failed progress as an
owned restart. The panel offers Wake (the sidebar open path, which wakes paired rows since #571/#583)
and Restart on paired rows again; Archive and Move stay hidden until PAIRED-ARCHIVE.
packaged-cli-assets' macOS launcher test compares an os.tmpdir()-based path
with the realpath the launcher reports, so it failed in the gate on any PR
selecting it (#574 batch 8, parallel and serial). Export a realpath'd TMPDIR
so the gate environment matches what child processes see.
design-squad: arrow keys land on Retry like on any row, Enter runs it, and while it reads it shows
Loading… and can't run twice. Coordinator: the GitHub list (and other team answers) re-read on an
owner/member role switch; tests cover owner → member → owner, then a restart.
A failed first page resolved as an empty listing, cached for 5 minutes per identity, and an empty
list hides the Project picker's GitHub section: after a restart or role change the section was
gone for minutes. A failed read now isn't cached and the section says 'Couldn't load GitHub
repositories. Retry'; an empty answer isn't kept either, so each open asks again.