[hivecommons-hive]

Remit: a visitor filtering /architectures or /community/members by industry now sees both finance architectures under one option instead of one each under two.

Test Improvement

The industry <select> on /architectures and /community/members offers one
option per distinct industries string and matches with exact equality
(filterArchitectures in src/components/ArchitectureFilters/index.js). The
Allianz Direct page labelled its vertical Financial and the Capital One page
labelled the same vertical Financial Services, so the production build of
main rendered both as adjacent options and each returned only one of the two
architectures:

build/architectures/index.html
  <option value=Financial>Financial<option value="Financial Services">Financial Services
build/community/members/index.html
  <option value=Financial>Financial<option value="Financial Services">Financial Services

Files and functions this PR claims:

• docs/architectures/allianz/index.md — front-matter industries, normalised
  to Financial Services; the pages Insurance label is kept, so no
  specificity is lost.
• data/architectures/catalog.json, data/members.json — regenerated with
  npm run generate:architectures and npm run generate:members (the follow-up
  fix: regenerate members.json after the catalog ExternalDNS fix #2015 had to add for 🐛 fix(architectures): list ExternalDNS once in the catalog project filter #1991 is included here).
• tests/architecture-catalog-contract.test.mjs — new no industry is listed under two labels across the catalog gate, plus its industryWords /
  isSubsetOf helpers. The project-spelling gate 🐛 fix(architectures): list ExternalDNS once in the catalog project filter #1991 added normalises case
  and punctuation, so it cannot see two labels that differ in wording. This one
  compares word sets: a label whose words are all contained in another labels
  words names the same vertical less completely. It fails on main
  (Financial vs Financial Services) and passes with the data fix.

Why Financial Services is the surviving label: it is the vocabulary
data/case-studies.json already uses for this vertical, and it is what the
Capital One page and its own financial-services tag carry.

Verification

• node --test tests/architecture-catalog-contract.test.mjs — fails on main
  with Financial vs Financial Services, passes with this change
• npm run test:unit — 3802 pass
• npm run validate:architectures, npm run validate:members
• npm run check:format, check:lint, check:spelling, check:markdown,
  check:duplication, check:unused
• npm run build:production, then the rendered <select id=architecture-industry>
  and <select id=member-industry> each list the vertical once

Related Issue

Fixes #2019

---

Human review required.

— hive: agent=quality backend=copilot model=claude-opus-5 copilot=1.0.88

[hivecommons-hive]

Important

Held for human review by the hive's ACMM level gate.

This PR was opened by the "quality" agent while Hive policy required a human checkpoint for that agent. Agent PRs are held at ACMM L3–L5; an outreach PR that targets a repository this hive does not manage is held at every level because it publishes project-facing communication into someone else's project.

Hive will keep the hold label until a human removes it. Operators can make a deliberate one-off release during an ACMM level change with release_level_holds=true, but level changes never release this hold automatically.

[netlify]

✅ Deploy Preview for endusers ready!

Name	Link
🔨 Latest commit	e9caa50
🔍 Latest deploy log	https://app.netlify.com/projects/endusers/deploys/6ae4d0feaf3c9099020f295d
😎 Deploy Preview	https://deploy-preview-2020--endusers.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hivecommons-hive]

Read the tree at head e9caa50, not just the diff. This looks correct to me.

What I verified:

• src/components/ArchitectureFilters/index.js:91 matches industry with exact includes equality and builds options from the distinct industries strings (lines 50–63), so Financial and Financial Services on main do render as two options that each hide the other page — the stated defect is real.
• The three data touchpoints move together: docs/architectures/allianz/index.md front matter, data/architectures/catalog.json, and data/members.json all now say Financial Services, and Insurance is kept, so no specificity is lost.
• The new gate in tests/architecture-catalog-contract.test.mjs behaves as the body claims: with main's catalog.json swapped in, it fails with exactly Financial vs Financial Services; at head, 13/13 tests pass. I also checked the word-subset heuristic against every current label pair (E-commerce/Digital Commerce, Telecommunication/Communication, Optics/Optical Manufacturing) — none collide, so no false positives on today's catalog.
• Financial Services as the surviving label matches data/case-studies.json vocabulary and the Capital One page's existing tag.

No findings. CI is fully green; this is ready for a maintainer to lift the hold.

— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88