fix(client): ignore stale dashboard details

[HandSonic]

Related issue

N/A - no matching issue was found.

Summary

Dashboard detail loads committed every response. Rapid A-to-B selection could let a slower A response overwrite the already selected B dashboard, and an older success could also commit after the latest request failed. This change assigns generation ownership to detail loads and invalidates pending details when the current dashboard is set directly.

Affected surfaces

• Frontend / Web
• Backend / API / Storage
• Database plugin / Driver
• JCEF / Desktop packaging
• CI / Build / Release
• Documentation only

Verification

• Commands and results:
  • Deferred ownership tests passed for reverse completion, direct invalidation, and latest failure.
  • Targeted ESLint: passed.
  • Full Community prebuild, Umi/Webpack build, and production bundle verifier: passed.
  • Fork code and CodeQL checks: passed.
  • Merge-tree with the current repair batch: passed.
  • Playwright: delayed B-to-A reverse completion and latest-failure/older-success ordering both preserved A.
• Manual verification: Passed in the Community dashboard UI with delayed and failed mocked detail responses.
• UI evidence: N/A

Risk and compatibility

• Public API or stored data: No API or persisted dashboard format changes.
• Database or driver compatibility: N/A.
• Network, privacy, or security: N/A.
• Community / Local / Pro boundary: Shared Community dashboard store.
• Backward compatibility: Latest successful loads and direct selection retain existing state shapes.

Reviewer map

• Start here: DashboardDetailRequestOwner and createCommonAction.getDashboardById.
• Failure condition: an older response commits after a newer request or direct selection.
• Rollback or disable path: Revert commit cd1e9f0b03d71b5601b6cc92eafe6fbf57fa9c69; no migration is required.

Contributor declaration

• I linked the Issue that defines this change.
• I tested the affected behavior and reported the actual results above.
• I did not include credentials, private data, or generated build output.
• I disclosed substantial AI assistance below, or this PR contains no substantial AI-generated code.

AI assistance: OpenAI Codex assisted with diagnosis, implementation, automated tests, verification, and adversarial review.