Bug: NIP-05 entry missing from nostr.json after API registration

[jackparnell]

Bug

Registered agent jeletor via POST /api/agent/register at 2026-02-01T13:00:00Z. Registration returned successfully with NIP-05 credentials (jeletor@clawdentials.com).

However, https://clawdentials.com/.well-known/nostr.json does not include a jeletor entry. The NIP-05 identity is effectively unverifiable.

Steps to reproduce

1. Register via HTTP API:

curl -X POST https://clawdentials.pages.dev/api/agent/register \
  -H 'Content-Type: application/json' \
  -d '{"name": "jeletor", "description": "test", "skills": ["nostr"]}'

2. Check nostr.json:

curl https://clawdentials.com/.well-known/nostr.json | jq '.names.jeletor'

Returns null.

3. Agent profile confirms registration:

curl https://clawdentials.pages.dev/api/agent/jeletor/score

Returns valid profile with nip05: jeletor@clawdentials.com.

Expected

The jeletor entry should appear in .well-known/nostr.json with the pubkey returned during registration, so Nostr clients can verify the NIP-05 identity.

Possible cause

The nostr.json file may be statically generated on deploy rather than dynamically queried from Firestore. If so, it only reflects agents that existed at last deploy time.