[Client P1] Cards show raw project codes/filenames instead of a merchandised title + summary

[jaysanderson]

Feedback (client + a side-by-side review agent - flagged as THE dominant issue)

Cards in the Fly portal show raw project codes/filenames ("Project 2014-001", "2013-052 DLD", "2014-001-DLD.pdf") instead of a human title + a two-sentence summary of what the document says. "To a non-technical FRDC stakeholder, the Bolt site looks like it understood the documents; the Fly site looks like a folder listing." This does more damage than everything else combined, and violates our own merchandising rule (CLAUDE.md: never raw filenames).

Root cause (two contributing factors)

1. Enrichment not yet run on FRDC. The DA merchandiser (title/summary/key-takeaways) has run on GRDC (all 1,070 resources render real titles) but NOT yet on FRDC - FRDC is mid-load; enrichment is queued to run after the load completes. So current FRDC codes are a sequencing state, not a pure rendering bug. GRDC cards already render correctly.
2. Possible un-rendered platform summary (INVESTIGATE - potentially a faster fix). The review agent notes the summaries "almost certainly exist in the KB; the portal just isn't rendering them." The platform likely generates its own per-resource summary on ingest (da-pagesummary / metadata.summary) that we do not read back - see docs/BACKLOG.md ARAG-roadmap item 3 (toSummary reads metadata.summary, not da-pagesummary-f-*).

Action

• Finish FRDC enrichment (tracked in [Client P1] Ingest the complete corpus for FRDC and GRDC (not a subset) #40 / the post-load plan) so cards get our merchandised fields.
• Add a fallback so a card is NEVER bare: when our enrichment is absent, render the platform's generated summary/title where present, only falling back to the code as a last resort. Cards then look "understood" immediately on ingest, without waiting for the enrichment pass.

Where

packages/retrieval/src/providers/arag (toSummary / resource mapping); card components in apps/web/src.

[jaketracey]

Update: GRDC has regressed, and both portals are now affected

This issue recorded GRDC as already merchandised (all 1,070 resources rendering real titles) with FRDC pending. That is no longer true.

The Cloudflare migration (#66) moved production off the fly.io rp_data volume onto Durable Object state. The merchandising enrichment records were app-side and keyed by tenant slug in EnrichmentStore, so they did not migrate. GRDC's merchandising is gone.

Live now on https://corpuskit.noice.net.au:

GET /api/t/grdc/search?q=wheat
  title='CSP2307-003RTX'   summary='CSP2307-003RTX'   enriched=false
  title='SCF2202-002SAX'   summary='SCF2202-002SAX'   enriched=false

GET /api/t/frdc/search?q=abalone
  title='Project 2002-200'                            enriched=false

So both portals currently show raw project codes - the exact 'looks like a folder listing' failure this issue was opened for, now on both tenants rather than one.

Related good news: FRDC's corpus load has finished. /api/t/frdc/counters reports 3,940 resources, against the ~2,690 of 3,920 recorded in #40. The enrichment pass that was waiting on that load is now unblocked.

Remedy (needs an admin credential, so it is not something an agent can run):

POST /api/admin/t/grdc/enrichments/run   {"scope":"missing"}
POST /api/admin/t/frdc/enrichments/run   {"scope":"missing"}

The admin surface is live and configured on the Worker (it returns 401 unauthorised rather than 503 disabled), so it needs the x-admin-passcode header or a signed-in admin session via Manage.

The daily auto-enrichment shipped in #58 will also drain this on its own schedule, but 'within a day' is not much use before a demo.

Worth noting for any future migration: enrichment records being app-side, slug-keyed and not covered by the migration is the underlying fragility here.