Force a freshness check each time the user enters the Checks tab (open sidebar, switch to Checks tab, or switch active worktree/branch) so stale PR metadata, cached-null "no PR" results, stale checks, and stale comments are surfaced immediately rather than waiting for the cache TTL. - Extracts entry-refresh logic into `checks-entry-refresh.ts` with a 30 s grace window to suppress rapid show/hide duplicate fetches. - Adds a `shouldEntryRefresh` effect in `ChecksPanel` keyed by `activeWorktreeId::repo.path::branch`; resets on panel hide so close-and-reopen re-evaluates freshness. - Fixes a stale-closure bug in `handleRefresh`: `fetchPRChecks` is now called directly with the freshly resolved `headSha` after PR refresh instead of reusing the pre-refresh closure's captured sha. - Adds 11 unit tests in `checks-entry-refresh.test.ts`. - Design doc: `docs/refresh-on-checks-tab.md`. Co-authored-by: Orca <help@stably.ai> |
||
|---|---|---|
| .. | ||
| assets | ||
| README.es.md | ||
| README.ja.md | ||
| README.md | ||
| README.zh-CN.md | ||
| STYLEGUIDE.md | ||
| gh-work-item-drawer-cache-flash.md | ||
| gh-work-item-drawer-cache.md | ||
| manual-repo-reorder.md | ||
| mobile-prefer-renderer-scrollback.md | ||
| mobile-presence-lock.md | ||
| mobile-shared-client-per-host.md | ||
| refresh-on-checks-tab.md | ||
| resource-usage-merge-spec.md | ||
| sidebar-filter-redesign.md | ||
| sidekick-animation-state-mapping.md | ||
| tasks-page-resume-state.md | ||
README.md
Orca CLI Docs
Keep this folder focused on the durable references for Orca's public CLI and runtime model.
Keep These Docs
orca-cli-focused-v1-status.md- What is actually implemented and intentionally in scope now.
orca-cli-v1-spec.md- The public CLI contract, selector grammar, JSON envelope, and command semantics.
orca-runtime-layer-design.md- Why the runtime layer exists and which boundaries it owns.
orca-cli-bundled-distribution.md- How the bundled desktop-app distribution and PATH registration model works.
Why The Folder Is Small
Earlier design and implementation work produced several planning and evaluation docs. Those were useful while the feature was taking shape, but they were intentionally removed once the implementation converged so future readers are not forced to choose between multiple overlapping sources of truth.