Clarify design intent: keep batch download enabled during busy states

[Copilot]

Responded to review feedback on PR #64 regarding the batch download button's behavior during busy states.

Design Decision

The batch download button intentionally remains enabled when isBusy is true, unlike batch delete and other mutating operations. Downloading auth files is a read-only operation that doesn't modify system state, so there's no risk in allowing it during account switches or other busy operations.

<!-- Batch delete: disabled when busy (modifies state) -->
<button :disabled="isBusy" @click="batchDeleteAccounts">

<!-- Batch download: always enabled (read-only) -->
<button @click="batchDownloadAccounts">

No code changes were needed—the current implementation already reflects this design.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.