* fix(docs): load the player from latest, not a pinned minor
The catalog pages pinned the player CDN URL to a minor line, and that pin
sat one line behind after the last release. Every page kept rendering, on
the older build, so nothing surfaced it: the only symptom was that a fix
published to npm never appeared on the docs.
The generator derived its pin from the player's package.json, which is
correct only if every page is regenerated on the release that moves it.
That is the step that did not happen, and it has to happen across 175
generated pages plus three hand-written files for the pin to be true.
A version carried in step across 178 places will be stale, and stale here
is silent. Ask for latest instead and there is nothing to carry.
This costs the ability to hold the docs back from a bad player release.
Paid deliberately: the pin did not buy that either, it only delayed the
good releases too.
A test asserts no pinned version comes back, and fails if it stops finding
the references at all, so it cannot pass by matching nothing.
* refactor(scripts): list tracked files instead of walking the tree
The pin guard hand-rolled a recursive directory walk with its own skip
list and size cap, which the audit flagged: helpers living in a test file
earn no coverage, so their complexity lands straight on the CRAP score.
git already knows which files to read, and ignores node_modules and build
output for us, so one call replaces the walker and both findings go away.
