Admin: Force brand registry re-crawl tool needed + immediate fix for latinxctv.com

[geneticallymodifiedfoodforthought]

Problem

When a verified brand owner publishes a valid brand.json at /.well-known/brand.json, the AAO Brand Registry does not automatically promote the record from source: hosted to source: brand_json in a timely way. There is no admin tool to force a re-crawl, leaving verified owners blocked until the crawler picks it up on its own schedule.

Confirmed case

• Escalation Add unified content distribution system with The Latest section #477 — Gustavo Aparicio (gustavo@latinxctv.com / Spanglish Movies org)
• brand.json live at https://latinxctv.com/.well-known/brand.json (HTTP/2 200, valid schema, name: LatinX CTV, domain: latinxctv.com)
• Domain verified under correct WorkOS org
• save_brand returned success (revision 1)
• resolve_brand still returns brand_name: latinxctv.com, source: hosted — not promoted
• Business impact: Scope3/Interchange sandbox advertiser creation blocked (run ID: ab771fb9-3186-4345-b820-49773fb05595). Error: Brand latinxctv.com not found in AAO registry.

Immediate action needed (Brian)

Manually trigger a registry re-crawl for latinxctv.com to promote the record from source: hosted to source: brand_json.

Systemic fix needed

Add an admin tool (and ideally a self-serve trigger for verified domain owners) to force a brand registry re-crawl for a specific domain. Suggested interface:

force_brand_crawl(domain: string) → { status, previous_source, new_source }

This would unblock verified owners immediately without requiring engineering intervention every time the crawler lags.

Related

• Escalation Add unified content distribution system with The Latest section #477 (Gustavo Aparicio / latinxctv.com)
• adagents.json is separately valid — this is purely the brand-directory/brand-manifest layer

[bokelley]

Thanks for filing!

Triage

Classification: Bug (auto-crawl gate) + Feature request (admin tool)
Bucket(s): registry/discovery, admin/ops tools
Status: ready-to-implement
Priority: P0 — verified member blocked from advertiser creation

What the experts said:

• internal-tools-strategist: Admin endpoint is justified — the real gap is that the existing /api/registry/brand-crawl-request returns 202 with no confirmation that promotion happened. Synchronous POST /api/registry/brand/:domain/force-crawl (admin-only, returns { previous_source, new_source, promoted }) mirrors the existing adagents revalidate pattern. Brian can unblock latinxctv.com today via the self-serve endpoint.
• adtech-product-expert: Root bug in the auto-crawl gate: resolve_brand calls scanBrandForDomain only for never-crawled domains — brands registered via save_brand (source: hosted) fall through the gate and are never auto-promoted. Systemic fix: hook domain-verification completion → scanBrandForDomain, and fix the gate to also fire when source_type === 'hosted'.

My take: Two distinct issues bundled: (1) a code bug in the auto-crawl gate that causes any brand created via save_brand to stay hosted indefinitely, and (2) a missing admin confirmation path. Both are non-breaking server-side fixes. Immediate workaround: POST /api/registry/brand-crawl-request { "domain": "latinxctv.com" } with admin credentials — then verify via resolve_brand.

Implementation scope (no protocol/schema change, no changeset):

• Root bug — auto-crawl gate (server/src/routes/registry-api.ts, resolve_brand handler ~L8074): extend the brandNeverCrawled condition to also call scanBrandForDomain when source_type === 'hosted' and domain has a verified owner — eliminates this class of failure for all future brands
• Domain-verification hook (WorkOS verification callback): call crawler.scanBrandForDomain(domain) on completion so hosted → brand_json promotion happens before any downstream system observes the hosted state
• Admin endpoint (server/src/routes/registry-api.ts): add POST /api/registry/brand/:domain/force-crawl (admin-only, synchronous, returns { previous_source, new_source, promoted: boolean }) — mirrors /api/registry/publisher/:domain/adagents/revalidate
• Admin UI (server/public/admin-brands.html): "Force Re-crawl" button per row after endpoint lands

---

Triaged by Claude Code. Session: https://claude.ai/code/cse_012m3k7GSZXU963XpZnaAy4a

---

Generated by Claude Code