Decision: four UI polish calls before 1.0

Umbrella decision issue. #389 shipped redesign turns 3-5, but four owner-level choices still have reversible fallbacks in code. None adds a UI blocker to the 1.0 contract in #307. The point is to make the final UI contract explicit before the fallbacks become accidental precedent.

This issue is to decide, not to drift.

1. Passkey ceremony activity

Turn 5 section 5f asks whether passkey setup and unlock should be the one exception to section 3h's latch rule. WebAuthn can leave control with the browser for several seconds.

Shipped: the action disables and becomes ..., while the gate says Your browser is asking. Nothing has been sent anywhere. (extension/sidepanel/components/vault-gate.js). The existing reduced-motion-aware brand orb is available in extension/sidepanel/styles.css.

• A. Keep the latch and sentence.
• B. Show the brand orb during passkey setup and unlock, while preserving the sentence and reduced-motion behavior.

2. Onboarding step-indicator shape

Turn 5 section 5e settles the indicator as monochrome, but its mock uses left-aligned bars while the shipped UI uses centered round dots (extension/sidepanel/styles.css). The live funnel now has four steps, not the mock's three (extension/sidepanel/components/onboarding-view.js).

• A. Keep the centered round dots.
• B. Use left-aligned bars, rendered as four monochrome steps.

3. Theme behavior for standalone pages

At a21080c, four committed light/dark pairs are byte-identical: vm-tab-failed, notebook-tab-failed, app-tab-failed, and the dev-only eval-runner (scripts/cdp/states.mjs). Pod is the exception: it follows the OS light theme (extension/engine-tabs/pod-tab/styles.css), while the VM, Notebook, and App failure surfaces stay dark.

• A. Add light-theme treatments to all four non-theming surfaces, matching Pod's behavior.
• B. Keep those four surfaces deliberately dark-only and document Pod as the explicit themed exception.

4. Skipping provider setup

Turn 5 section 5h calls I'll do this later a product decision. The shipped button advances with no writes (extension/sidepanel/components/onboarding-provider-step.js), and the composer then gives an honest Settings action instead of sending without a provider (extension/sidepanel/provider-readiness.js). This is therefore a confirmation or reversal of current behavior, not a blank-slate decision.

• A. Keep the no-write skip.
• B. Require a usable provider before onboarding can continue.

Decide here

Reply with one choice per item, for example 1B, 2A, 3A, 4A. The shipped fallbacks remain in place until a choice changes them.

Review the four decision areas and the referenced entry points: extension/sidepanel/components/vault-gate.js, extension/sidepanel/styles.css, extension/sidepanel/components/onboarding-view.js, extension/sidepanel/components/onboarding-provider-step.js, provider-readiness.js, scripts/cdp/states.mjs, and pod-tab/styles.css. First obtain one selected option for each item; done means the UI contract is recorded and any resulting implementation or documentation work is separately actionable.