Found in the adversarial review of #120.
CommunityMech '15 categories' disagrees with the Browse and 'Published site' link, which shows 16
Where: _fleet/mechs_template.md:32
The card says '422 community records · 15 categories', and the paragraph above it says 'Each Browse link is the source for its card.' communitymech.md:14 says 'The published site lists 422 communities across 15 categories' and links to the landing page. That landing page, which is also the card's Browse link, shows a '16 categories' tile. 15 is the substantively right number (schema enum, records and browser facet all have 15), but no page tells the reader that the landing tile is stale. The PR does disclose the CultureMech landing tile's stale figure in the same way.
Failure scenario. A reader clicks Browse on the CommunityMech card or '[Published site]' on /communitymech/ and sees '16 categories' next to 422 communities. The page promised that link as the source, so the figure looks wrong.
Evidence. curl -sL https://culturebotai.github.io/CommunityMech/ → line 81: '16categories'. On browser.html there are 422 .community-card elements carrying 15 distinct data-category values. CommunityCategoryEnum at 8505a56 has 15 values. site_audit.json notes the '16 categories' tile is hard-coded upstream, but that note never reaches the page. Same '15 categories' wording appears in fleet_fragment.html:446, communitymech.md:14 and resources.md:177.
Verifier (confirmed, low). The finding is accurate as stated, with one addition: the mismatch is new in this PR. On main, the card and communitymech.md said 16, which matched the landing tile.
Suggested fix. Say the 15 comes from the browser facet (or schema) and that the landing tile still reads 16, the same way the CultureMech stale-tile note is handled. Alternatively, point the Browse link at browser.html.
Found in the adversarial review of #120.
CommunityMech '15 categories' disagrees with the Browse and 'Published site' link, which shows 16
Where:
_fleet/mechs_template.md:32The card says '422 community records · 15 categories', and the paragraph above it says 'Each Browse link is the source for its card.' communitymech.md:14 says 'The published site lists 422 communities across 15 categories' and links to the landing page. That landing page, which is also the card's Browse link, shows a '16 categories' tile. 15 is the substantively right number (schema enum, records and browser facet all have 15), but no page tells the reader that the landing tile is stale. The PR does disclose the CultureMech landing tile's stale figure in the same way.
Failure scenario. A reader clicks Browse on the CommunityMech card or '[Published site]' on /communitymech/ and sees '16 categories' next to 422 communities. The page promised that link as the source, so the figure looks wrong.
Evidence. curl -sL https://culturebotai.github.io/CommunityMech/ → line 81: '16categories'. On browser.html there are 422 .community-card elements carrying 15 distinct data-category values. CommunityCategoryEnum at 8505a56 has 15 values. site_audit.json notes the '16 categories' tile is hard-coded upstream, but that note never reaches the page. Same '15 categories' wording appears in fleet_fragment.html:446, communitymech.md:14 and resources.md:177.
Verifier (confirmed, low). The finding is accurate as stated, with one addition: the mismatch is new in this PR. On main, the card and communitymech.md said 16, which matched the landing tile.
Suggested fix. Say the 15 comes from the browser facet (or schema) and that the landing tile still reads 16, the same way the CultureMech stale-tile note is handled. Alternatively, point the Browse link at browser.html.