perf(repos): serialize repository list refreshes

[beruro]

Summary

• share one repository-list IPC request across concurrent consumers
• queue exactly one trailing list read when force refresh or a repository mutation supersedes an active response
• fence stale responses so they cannot overwrite the post-mutation list
• let useRepoLoader start a force generation without falsifying the global in-flight flag
• release failed flights so later loads can retry

Validation

• repository coordinator Vitest suite: 4 passed
• pnpm exec tsc --noEmit --pretty false
• Prettier and ESLint on all changed files
• git diff --check

Performance guard

Pass. No timer, polling loop, or retained result cache is added. There is at most one active list IPC plus one generation-triggered trailing read; mutation invalidation is demand-driven and all in-flight state is released on success or error.

Architecture audit

Covered compilation, single ownership of list-flight state, generation semantics, mutation parity, failure recovery, and hook/API boundary behavior. Wire payloads and repository mapping remain unchanged.