[hivecommons-hive]

Test Improvement

Adds tests/refresh-script-wiring.test.mjs. The diff is one new file under tests/ — no behaviour, CI definition, or data file changes.

tests/workflow-scripts.test.mjs already asserts that every validate:*/check:* gate is run by CI or recorded in GATES_NOT_RUN_BY_CI with a written reason. Nothing made the same demand of the scripts on the other side of that contract — the collect:*, fetch:*, import:* and generate:* scripts that write the datasets those gates then validate.

tests/automation-workflow-ordering.test.mjs names the same four namespaces, but only constrains the order of steps in a job that already runs one of them, so a refresh script nothing schedules never appears in any job and that file has nothing to order. The failure that leaves open is silent: a collector stops being scheduled, its dataset stops being refreshed, and its validator keeps passing — because stale data is still valid data.

What the new file asserts

• Every collect:*/fetch:*/import:*/generate:* script is scheduled, or recorded in REFRESH_NOT_RUN_BY_CI with a reason.
• Resolution follows npm run chains through package.json, so generate:members counts as wired via import:architectures rather than forcing a false exemption. A dedicated test pins that this transitive step is load-bearing — it fails if generate:members ever becomes directly reachable, so the guard cannot quietly stop proving anything.
• Staleness guards: an exemption fails if it names a script package.json no longer defines, carries no reason, names a script outside the refresh namespaces, or names a script that is in fact scheduled.
• Vacuity guards: the detector must still recognise the known refresh scripts, and must still reach the five scheduled collectors.

Exemptions recorded

collect:case-studies and collect:launch-metrics are unscheduled on purpose. That decision previously lived only in prose (scripts/collect-case-studies.mjs, docs/resources/case-studies.md, CONTRIBUTING.md, ROADMAP.md); it is now on the record where a test can tell it apart from an accident.

Verification

• node --test tests/refresh-script-wiring.test.mjs — 8 passed, 0 failed.
• Mutation-checked twice, to confirm the guard is not vacuous:
  • renaming an exemption key to a script that does not exist → 3 tests fail;
  • removing npm run collect:radar-reports from refresh-radar-reports.yml → 2 tests fail, including the main wiring assertion.
• npm run test:unit:coverage:check — exit 0 with the new file included (src files 100.00% lines / 100.00% regions).
• npx prettier --check — clean.

Related Issue

Closes #1357

---

Filed by quality agent (hold-gated mode). 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. Non-outreach agents are held at ACMM L3–L5; the outreach agent is always held because it publishes project-facing communication.

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.