Display README title as primary heading with repo slug as subtitle

[Copilot]

Repository slugs are acronym-heavy and difficult to scan. Cards now display the first H1 from each repo's README as the primary title, with the slug as a monospace subtitle.

Changes

• Workflow: Modified .github/workflows/refresh-data.yml to fetch README content and extract first H1 heading into readmeTitle field

  • Regex supports both # Title and #Title formats
  • Gracefully handles missing READMEs (continues with null)

• Type system: Extended Repository interface with readmeTitle?: string | null in src/utils/categorize.ts

• UI: Updated RepoCard.astro to prioritize README title over slug

  • Primary: readmeTitle (line-clamp-2, semibold)
  • Subtitle: repo.name (10px, monospace, gray-400)
  • Fallback: slug only when no README title exists

Result

Cards now show "IP Atlas - Repository Catalog" instead of "devexpgbb.github.io", with the slug visible as context. Next scheduled data refresh will populate titles for all repos.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• telemetry.astro.build
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/devexpgbb.github.io/devexpgbb.github.io/node_modules/.bin/../astro/astro.js build (dns block)
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/devexpgbb.github.io/devexpgbb.github.io/node_modules/.bin/../astro/astro.js preview --host 0.0.0.0 --port 4321 (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Should IP titles = repo title? Or semantic name</issue_title>
<issue_description>Currently, IP titles are equal to the repo slugs.

Repo slugs are not human friendly and typically contain many acronyms and shortcuts. For IP adoption and quick scanning, a semantic name per IP may make more sense, on top of the repo slug.

This is how it looks like today:

A possibility here could be to fetch the README.md's title as semantic title if it exists and then just below, as subtitle, the repo slug. </issue_description>

<agent_instructions>Make sure to use Playwright MCP to ensure we do not break UI </agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Should IP titles = repo title? Or semantic name #21

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.