chore(baseline): app-version meta absent site-wide (§6.7) + generated JSON artifacts drift ungated #81

Found while shipping the flywheel protocol page (PR #80, merged 6a167e76). Both are pre-existing on
main — neither was introduced by that PR. Filing together because they share one root cause: a
generated/required artifact that nothing gates.

1. <meta name="app-version"> is missing site-wide — CLAUDE.md §6.7 requires it

§6.7 makes the app semver mandatory on every DIG frontend, in all three forms, specifically so
bug reports carry build attribution:

• a subtle on-page display (small, muted — e.g. v1.4.2 in the footer)
• <meta name="app-version" content="…">
• a window.__APP_VERSION__ string global

<BugReportButton> auto-detects in that priority order (explicit appVersion prop → meta tag →
global). docs.dig.net has none of the three on any page, so every bug report from this site arrives
without a version — which is the one field that makes a report reproducible.

Inject it at build time from package.json; never a hardcoded literal, which drifts from the
package version silently. Docusaurus idiom is a customFields/plugin injection — see the
frontend-baseline skill for the per-stack pattern.

2. Generated JSON artifacts drift because nothing rebuilds them on merge

static/knowledge-graph.json and static/openrpc*.json were stamped 0.15.0 while package.json
was at 0.16.1 — i.e. a PR merged without running the build. Realigned to 0.17.0 in PR #80, but
nothing prevents it recurring, so it will.

A stale knowledge graph is worse than an absent one: it is the machine-readable index (§6.2), so an
agent reading it gets a confidently wrong answer about what this site documents. The same argument
applies to openrpc*.json — a published API description that lags the code is a contract that lies.

Fix: regenerate in CI and fail the build if the committed artifacts differ from the regenerated
ones, so the check is the generator itself rather than a reviewer remembering.

Also seen, not worth its own ticket

The id locale emits a plural-forms build warning (2 forms supplied where 1 is expected) on every
build. Pre-existing, non-fatal, but it trains readers to ignore build warnings — which is how a real one
gets missed.

Parent: https://github.com/DIG-Network/dig_ecosystem/issues/1425 (closed — this is its residue, not a
blocker of it).