Import an exact inventory identity from its selected source with retry

[loganj]

🤖

Summary

• An identity under Available to import now has an Import action on its card. It opens the existing import review with that exact identity and its local source already selected.
• If the source cannot be read, the card shows the error and a retry. You can still change the source.

Details

• Import appears once for each public key. If more than one old installation has the identity, you choose the source explicitly.
• Import keeps the selected identity and private key. It needs a destination and a new preview. The saved agent is configured and stopped. Import does not start the agent, invite it anywhere, or change the old installation.
• If this computer already has the identity, you cannot import it again into another community. The card does not offer Import for it. Clone for this case arrives in Clone inventory identities through reviewed text and fresh identity creation #289. Native code checks this rule both when it prepares an import and when it saves one.
• The card Import replaces the old installation browser. One case keeps it: if an imported agent is missing its team instructions, Repair team import from another installation stays available. It lists only agents that need that repair, and it never offers an ordinary import.
• Based on Set up incomplete inventory identities through a working Use here dialog #287.

Screenshots

Captured from the browser test fixture at this PR's head.

Agents from another installation appear as cards with Import

Import review names the source and the destination community

With no selected community, import review asks for a destination community first

[wesbillman]

Star Lord automated source review, posted via Wes’s account.

Reviewed head 60716f033eecd5cd82c48c087e2a758eb1a5aa95 against base/merge-base d2b916ea213bad986ac561d93dcd93a3ca2a8887.

One P2 finding: the new selected-identity dialog removes the destination-entry path when no community is selected (inline below). Preserve an explicit destination choice and obtain a fresh preview before enabling Import.

I inspected the complete 13-file delta and traced inventory selection, source retry/switching, preview/write fencing, repair-only fallback, and the existing native import boundary. The native path retains source/destination binding, duplicate-key checks at preparation and save, and configured/stopped persistence. Earlier stacked-base findings are not duplicated here.

Validation: source-only review of immutable, hash-verified extracts; no dirty working-tree inputs. No tests, builds, PR-code execution, app launches, credential access or CI checks. Browser/native behavior and human acceptance remain unverified. This is a non-blocking COMMENT, not approval or merge authorization.

[wesbillman]

Carl, an automated reviewer, commenting via Wes’s GitHub account.

No actionable code blockers found; ready for code approval. Reviewed head d9d83f2069bd397bfdd22c5852a1a01d6ba3d5d0 against base/merge-base 31a89276a48d254ff550aef3c8689b5a6dee51f0 (#287).

The previous destination-entry finding is addressed: Personal space now permits an explicit destination, edits invalidate the old preview, and the mounted card-to-dialog regression reaches import after a fresh preview. Rechecked exact-key/source selection, retry, destination-change cleanup, repair-only fallback, and the unchanged native duplicate-custody/source-binding checks. Imports remain configured and stopped. Independent bounded UI/lifecycle review found no additional blocker.

Validation: successful hosted CI tested merge f21f7a3eeaabda1f415add08e3bf4b9eea5c18b8 with exactly those head/base parents. JavaScript passed 433 files / 5,162 tests, including the repaired flow; native import-boundary tests, Rust/tool integration, Chromium/WebKit journeys, measurements, DCO and security checks passed. Windows validation was skipped. The older failed aggregate belongs to a superseded cancelled workflow. No broad suites rerun locally.

Merge caveats: this still targets the open #287 feature branch, not main; land/retarget in stack order and recheck the resulting base. Browser fixtures and CI do not establish real native credential/storage import or human acceptance; confirm that required acceptance before treating this as fully validated. I did not launch the app or touch credentials. Inspected the full feature diff, PR text and three attached screenshots.

This is a readiness COMMENT, not approval or merge authorization.