fix(desktop): fan out managed agent profiles

[AaronGoldsmith]

Summary

Reconcile an existing managed agent's kind-0 profile on each community relay after that agent/community runtime pair starts successfully.

This fills the profile-transfer boundary left intentionally out of the per-community runtime work in #2083 and addresses the missing-name/avatar portion of #2366 without claiming to close the broader issue.

What changed

• Query and, when missing or stale, publish kind-0 on the originally requested community relay.
• Authenticate both operations with the managed agent's keys and auth tag.
• Run profile repair asynchronously so a slow or unavailable relay cannot delay runtime startup or the rest of the batch.
• Preserve the requested relay authority, including loopback aliases and explicit ports.
• Keep relay-local legacy-avatar resolution from mutating the single stored agent record during fan-out.

Behavioral guarantees

• Reconciliation starts only after the corresponding runtime pair starts successfully.
• A profile read or publication failure is logged but does not fail runtime startup.
• Query and publication use the same explicit relay authority and managed-agent credentials.
• Existing legacy single-relay reconciliation behavior remains intact.

Scope boundaries

This PR does not:

• mirror avatar/media blobs between relays;
• make identities portable through team snapshot import;
• deduplicate repeated team imports;
• change which agents or communities receive runtime fan-out;
• replace the adjacent profile-field preservation work in fix(profile): read-merge-write kind:0 so republish stops deleting unmodeled fields #2606.

Related avatar work remains in #2476 and #2507.

Manual verification

1. Start an existing managed agent in two configured communities.
2. Confirm each community continues using its own running runtime pair.
3. On a community relay missing that identity's kind-0, confirm the agent name/avatar metadata is republished there.
4. Make one destination relay unavailable and confirm runtime startup and other community pairs still complete.

Test plan

• Rebased onto origin/main at 76aeae703664a6a6741b82771df67c546886aafd.
• Full Desktop Rust suite: 1,616 passed, 0 failed, 14 ignored.
• Integration diagnostics: 3 passed.
• Commit hooks: sadscan, fmt, and desktop-tauri-fmt passed.
• Independent adversarial agent review: no findings after addressing a legacy-avatar backfill race.

Reviewer guide

Please focus on:

• managed_agents/runtime_commands.rs: the success-only, detached fan-out trigger;
• commands/agents_profile.rs: explicit relay validation and separation of global legacy backfill from relay-local fan-out;
• relay.rs: agent-authenticated profile query used by reconciliation.

Refs #2366.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 75bf466a7a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".