Chatbot: the field map has a card view – stop denying it

A user asked if the map has a list view and the bot said the page is
visual-only, offering feedback instead of the "View cards" button that
sits on the map. New prompt section states the card view plainly
(searchable, Category/Status filters, button scrolls to it) and bars
the bot from claiming the map has no list view. The /map page purpose
line in pages.ts now mentions both views too.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: bryceerobertson

src/lib/assistant/pages.ts

@@ -167,7 +167,7 @@ export const PAGES: PageInfo[] = [
     path: '/map',
     title: 'Field map',
     purpose:
-      'An overview of the key organizations, programs, and projects operating in the AI safety space.',
+      'An overview of the key organizations, programs, and other resources in the AI safety space – an illustrated map, with a searchable card view of the same listings below it (the "View cards" button scrolls there).',
     audience: 'Anyone who wants a bird-eye view of the ecosystem.',
     greeting:
       'Exploring the AI safety landscape? I can find orgs, projects, media, and more by category or focus.',

src/lib/assistant/prompt.ts

@@ -2,7 +2,7 @@ import { PAGES, greetingFor } from './pages'
 
 /** Stamp on every conversation log row. Bump manually when you ship a
  *  meaningful prompt change so historical conversations stay attributable. */
-export const PROMPT_VERSION = '2026-07-20-01'
+export const PROMPT_VERSION = '2026-07-20-02'
 
 /** The production system prompt. Edited only via code (not via the admin
  *  panel). Exported so the admin "use production prompt as draft" reset
@@ -338,6 +338,9 @@ The Field map (/map) is laid out as named regions, one per org \`category\`. Whe
 
 (Inactive orgs sit in **Gone Graveyard** – never refer to that area to users; per the inactive-listing rule, drop them silently.)
 
+# Field map: card view
+The /map page is not only the illustrated map – below it, the same page has a card view of every map listing, just like the other resource pages: a searchable card list with Category and Status filters. The "View cards" button on the map (bottom left) scrolls down to it. When a user wants the map's content as a browsable list – "is there a list version", "can I see these as cards", "the map is hard to read" – point them to this card view on the [Field map](/map) page itself. Never tell users the map is visual-only or has no list view.
+
 # Field map: printable copies and merch
 The Field map (/map) is an interactive page, with no self-serve print or PDF download on the site. But a printable version is NOT simply unavailable – two routes exist, so never tell users flatly that there's no printable/physical version:
 - **Printed map on request.** The team produces a printed version of the map by hand on request, always using the latest version. When someone asks for a printable, physical, or wall copy of the map, tell them this and point them to the team to arrange it: \`[[suggest:contact:USER_QUERY_HERE]]\`.