fix(ui): 本会话内延后提供商配置提示

[Cooper-X-Oak]

摘要

关联 fork 验证：Cooper-X-Oak#12。

本 PR 是从 fork/dev 已验证批次拆出的 UI 状态修复：提供商配置提示不再用 localStorage 永久记住“已看过”，而是只在本 session 内延后，避免用户未完成配置后后续启动再也不提示。

fork/dev 先行验证

• fork PR：test(windows): 收敛 fork dev 真机回归批次 Cooper-X-Oak/openless#12 test(windows): 收敛 fork dev 真机回归批次 Cooper-X-Oak/openless#12
• fork PR 状态：已 merge，merge commit b9ee8b8。
• fork CI：Windows Tauri checks SUCCESS，Sourcery review SUCCESS。
• fork 自审评论：test(windows): 收敛 fork dev 真机回归批次 Cooper-X-Oak/openless#12 (comment)

修复 / 新增 / 改进

• PROVIDER_SETUP_PROMPT_SEEN_KEY 改为 PROVIDER_SETUP_PROMPT_DEFERRED_KEY。
• provider prompt 状态从 localStorage 改为 sessionStorage。
• “稍后”只在当前会话内延后提示，下次启动若凭据仍未配置会再次提示。
• 更新 providerSetup 测试文案，明确 deferred 语义。

兼容

• 不包含：启动路径、热键 core、ASR、插入 fallback、权限状态、凭据字段保存。
• 对现有用户 / 本地环境 / 构建流程的影响：只影响未配置 provider 时的提示频率；不会读写真实凭据。

测试计划

• 命令：npm run build
• 结果：TypeScript + Vite build 通过。
• 命令：git diff --check
• 结果：通过。
• 命令：node --loader ts-node/esm src/lib/providerSetup.test.ts
• 结果：未运行，当前项目未安装 ts-node。
• fork PR CI：test(windows): 收敛 fork dev 真机回归批次 Cooper-X-Oak/openless#12 Windows Tauri checks / Sourcery review 均通过。

Summary by Sourcery

Limit provider setup prompts to be deferred only within the current session instead of being permanently suppressed.

Enhancements:

• Switch provider setup prompt state from localStorage to sessionStorage using a new deferred-key name and semantics.
• Clarify provider setup test description to reflect session-scoped deferral of the prompt.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the provider setup reminder so that deferring the prompt is tracked only for the current session via sessionStorage, instead of persisting a "seen" state in localStorage, and refreshes the associated key name and test wording accordingly.

Sequence diagram for provider setup prompt using sessionStorage

sequenceDiagram
  actor User
  participant App
  participant FloatingShellBody
  participant CredentialStore
  participant SessionStorage
  participant ProviderSetup

  User->>App: Launch app
  App->>FloatingShellBody: Mount component
  FloatingShellBody->>CredentialStore: getCredentials()
  CredentialStore-->>FloatingShellBody: CredentialsStatus
  FloatingShellBody->>SessionStorage: getItem(PROVIDER_SETUP_PROMPT_DEFERRED_KEY)
  SessionStorage-->>FloatingShellBody: promptDeferredValue
  FloatingShellBody->>ProviderSetup: shouldShowProviderSetupPrompt(credentials, promptDeferredValue)
  ProviderSetup-->>FloatingShellBody: boolean
  alt Prompt should be shown
    FloatingShellBody-->>User: Show provider setup prompt
    User->>FloatingShellBody: Click defer button
    FloatingShellBody->>SessionStorage: setItem(PROVIDER_SETUP_PROMPT_DEFERRED_KEY, 1)
    FloatingShellBody-->>User: Close prompt
  else Prompt should not be shown
    FloatingShellBody-->>User: No provider prompt this session
  end

Loading

File-Level Changes

Change	Details	Files
Track provider setup prompt deferral in sessionStorage for the current session instead of persisting a seen state in localStorage.	Replace localStorage access with sessionStorage when reading the provider setup prompt state on shell initialization. Replace localStorage access with sessionStorage when persisting the provider setup prompt state after the user chooses to defer. Rename the storage key constant to reflect session-scoped deferral semantics and update its value string.	openless-all/app/src/components/FloatingShell.tsx openless-all/app/src/lib/providerSetup.ts
Align provider-setup logic and tests with the new deferred-this-session semantics.	Update shouldShowProviderSetupPrompt parameter naming and logic to use the new deferred value instead of seen value. Adjust the providerSetup test description to state that the prompt is not repeated after being deferred in the current session.	openless-all/app/src/lib/providerSetup.ts openless-all/app/src/lib/providerSetup.test.ts

Possibly linked issues

• #[settings] 提供商未配置提示被永久压住: PR switches prompt state to session-only deferral, ensuring users see provider setup again while unconfigured

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since the storage key has been renamed and moved from localStorage to sessionStorage, consider cleaning up the old ol.providerSetupPromptSeen entry (e.g., on first run after upgrade) to avoid leaving stale keys around in existing installations.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since the storage key has been renamed and moved from localStorage to sessionStorage, consider cleaning up the old `ol.providerSetupPromptSeen` entry (e.g., on first run after upgrade) to avoid leaving stale keys around in existing installations.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}