Bug: present registered VM agents through native Hive identity surfaces

[100yenadmin]

Parent: #36
Related: #7, #41

Problem

Registered Company VM agents currently have several presentation sources: company catalog data, native signed profile data, native room membership, and relay liveness. The installed canary showed ATRIS in the company catalog while a DM/profile header exposed a raw public key, the Channels tab omitted visible memberships, and presence indicators disagreed.

The relay public key is protocol identity and must remain available for diagnostics, but it must not be the primary visible name.

Current-canary outcome

Native Hive surfaces render one coherent registered-agent name, visible room set, avatar fallback, and truthful presence without adding a second profile system or changing the VM agent's private identity or Hermes configuration.

Acceptance

• Native signed profile data is used when valid.
• Company catalog display name is the managed fallback when the signed profile is missing, stale, or a raw-key placeholder.
• Raw public keys remain available only in an explicit identity/details surface.
• DM header, profile panel, Agents card, mentions, search, and member lists display the same name.
• Visible channels come from actual native room membership filtered by the current user's visibility grants.
• A native signed avatar may be displayed; otherwise use a deterministic non-key fallback.
• Presence is online, offline, or unknown and is never inferred from catalog registration alone.
• Cross-company names, avatars, agents, and memberships remain undiscoverable.
• Focused profile/catalog/membership tests, exact-head CI, and one bounded semantic review pass.

Non-goals

• A Hive-only avatar/profile metadata service or admin upload UI.
• Editing Hermes model, memory, tools, provider, permissions, instructions, name, or private key.
• Rewriting native Buzz profile or channel protocols.

Proof boundary

Source tests prove mapping and filtering only. Installed proof must show ATRIS consistently by name, accurate visible rooms, truthful presence, and no raw-key primary labels.

[100yenadmin]

Issue #39 reached its stable source gate and is integrated into the #36 staging branch.

• Exact reviewed PR head: 519d4dc6e15a9824f5ea288a90249251b0237247
• Staging merge commit: 34f7ace7090904f9758f1393ed3dcef5316298a2
• PR: fix(hive): unify company VM agent identity surfaces #48
• Canonical exact-head CI: https://github.com/electricsheephq/evaOS-Hive/actions/runs/30246913664 (PASS, attempt 2)
• Independent semantic review: PASS on the initial exact head plus a targeted final delta review; no remaining P0/P1 or realistic supported-path P2 finding

Focused exact-lineage proof:

• company identity/catalog tests: 11/11
• focused agent, mention, profile, and channel-eligibility tests: 87/87
• full desktop helper suite: 3561/3561
• post-review focused tests: 95/95
• desktop typecheck/check and E2E build: PASS
• viewer-owned relay-agent activity Playwright regression: 1/1 PASS
• unrelated virtualization timing assertion that failed once in CI: unchanged source path, focused local rerun PASS, canonical failed-shard rerun PASS

Terminal finding dispositions:

1. Static liveness outside the Agents card: fixed now with presence-derived status.
2. Company-agent channels shown before native membership resolution: fixed now by failing closed until actual visible membership resolves.
3. React Query/reference churn: fixed now with stable memoized transforms and unchanged unmanaged references.
4. Company authority inferred from self-declared capability: fixed now; only the tenant catalog pubkey set selects the company transform.
5. Viewer-owned relay-agent activity regression: fixed now in the profile activity adapter without weakening tenant, owner, pubkey, or liveness gates.
6. One CI-only virtualization wheel-travel timing failure: false/not applicable to Bug: present registered VM agents through native Hive identity surfaces #39 after unchanged focused and canonical reruns passed.

This proves source behavior, exact-head CI, review, and staging integration only. The rebuilt signed artifact and installed primary operator/Benjamin/ATRIS canary remain separate gates under #36/#38; no customer rollout or default-branch merge is claimed.

[100yenadmin]

Closed at the stable source gate recorded above. Installed artifact/runtime proof remains owned by #36/#38 and is not claimed here.