v1.8.0 — the template is a template again

The template is a template again. Its working tree used to be one
organization's live catalog, so a copy made from it started life wearing that
organization's name, tagline, logo mark, footer and governance text — and the
first job of anyone forking it was to find and undo all of that. The named
catalog now has its own repository and this one ships a generic identity.

Changed

• The shipped configuration is organization-agnostic. _data/site.yml,
  _data/governance.yml, _data/showcase.yml, _config.yml and the LICENSE
  no longer name a real organization. The site ships as "AI Use Case Catalog"
  by an invented "Civic AI Community of Practice", which is what choosing the
  ai-use-cases preset in the setup wizard describes: a public-sector
  community of practice sharing what it has built. The governance page keeps
  its structure and reads as a worked example rather than one body's adopted
  policy.
• The ai-use-cases showcase example (/examples/ai-use-cases/) carries
  that generic identity and a refreshed set of sample entries, so the flagship
  example demonstrates the preset rather than a particular deployment.
  The ten new entries are org-agnostic public-sector use cases (permit
  intake triage, council meeting summaries, records-request redaction, …),
  written to the same standard as before; docs worked examples and test
  fixtures were re-pointed at them so nothing in the repository quotes the
  old deployment's data.

Removed

• The named deployment moved out. The health-coalition catalog this
  template was first built for now lives at
  crypticpy/bchc-ai-use-case-catalog,
  where its content, branding and adopted governance text belong. This
  repository stays the generic template; the repository slug bchc-template
  is unchanged so existing forks, remotes and links keep working.
• docs/dmwg-alignment-plan.md and docs/BCHC_DMWG_AI_Resource_info.md,
  the source framework and the field-by-field plan behind v1.5.0 and v1.6.0.
  They describe one work group's adopted framework, so they moved to that
  repository with it. What they produced — the schema fields, the governance
  module, the review workflow — is unchanged and documented in
  docs/content-model.md and
  docs/configuration.md.