jerry/buzz

mirror of https://github.com/block/buzz.git synced 2026-11-01 06:51:17 +00:00

Files

Eva 692fdafa61 fix(desktop): export/card resolves through the 30179 overlay; snapshot respond_to falls back to instance fields

Relay-hosted agents made two gaps in the export/card resolvers user-visible:

- Gap B: a relay-only agent (30179 head, never started on this device) has
  no disk record, so materialize_snapshot_bytes / card_mint_key_status /
  mint_agent_card failed with "agent not found" until first START.
- Gap A: a follower device exported the stale disk snapshot instead of the
  effective 30179 config it actually runs.

Fold the private-config overlay onto the disk list at all three resolver
sites — the identical resolution the agent list already uses
(resolved_records: applies patches to disk records AND synthesizes
relay-only entries). Card mint then also inherits the correct live kind:0
avatar for free, since its existing profile fetch runs after resolution.

Also give build_snapshot's respond_to/allowlist the same instance fallback
parallelism already has: an overlay-materialized record carries its
enforced respond_to only on the instance fields, so without the fallback a
relay-hosted agent exported respond_to=None while actually enforcing an
allowlist — a shared agent that behaves differently than advertised. Mode
and list travel together (definition mode -> definition list, instance
fallback -> instance list, never mixed).

Deferred as fidelity-not-function (tracked for the relay-hosted cutover):
kind:0 avatar hydration for ordinary JSON/PNG manifests, name_pool.

Verified: cargo test in desktop/src-tauri — 2283 passed, 0 failed;
clippy --tests clean; fmt clean.

Co-authored-by: Eva <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@buzz.block.builderlab.xyz>
Signed-off-by: Eva <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@buzz.block.builderlab.xyz>

2026-08-07 12:10:56 -04:00