Surface test count in node-ci output (Fable 'count-as-canary' practice)

[ArchonVII]

Umbrella: ArchonVII/archon-setup#244 (Fable-practices discussion — full context there).

Implementation lane for the CI-side inclusion (Tier 4) from the Fable process review.

Status: proposed. Owner authorizes before build.

Scope

• Make the test count a prominent, greppable line in the reusable node-ci output, so the "count-as-canary" instinct is cheap to act on (a passing run whose count silently drops, or that finishes suspiciously fast, is worth a second look).

Explicitly out of scope

• No hard test-count ratchet gate. It punishes legitimate test removals and fights solo-dev velocity, and it misreads the behavior we're adopting: Fable's move was suspicion (read the run log, check the count/timing against the head SHA), not a gate. Surface the signal; let the agent be suspicious. A ratchet is a someday-maybe at most.

Source-repo first (github-workflows), then snapshot into repo-template and distribute via archon-setup per the usual reusable-workflow rollout (permissions block + tag-ref alignment + integration-test review apply). Rationale: C:\Users\josep\fable-archive\reviews\2026-06-13-fable-incorporation-plan.md (Tier 4) and the evidence (cluster-E: "19 seconds is suspiciously fast for a 517-test suite"; the 519→499 silent test-count drop).