#3995 Registry: bump @swamp-club/extension-scoring to the version carrying #3983 (and #3845) before the v5 rescore

Repo: swamp-club. Follow-up to #3977, #3845 and #3983.

Problem

#3977 pinned the registry to jsr:@swamp-club/extension-scoring@0.20261026.1. Since then:

• #3845 published 0.20261026.2. It changes the scoring formula for provisional points and moves two provisional test vectors (100 → 87). The registry's grades are unaffected today, because the registry never produces a provisional row. But its vectors test no longer checks the same cases as the CLI.
• #3983 will publish a later version that moves the shared import scan from tokens to Babel. That scan is part of what rubric v5 scores.

What to do

• Bump the pin, and the vectors imported from that same version, to the first package version that carries #3983. Not .2 on its own: #3980's bulk rescore must run on the final v5 scanner, or a re-push would score differently from the stored rows.
• Run the shared vectors through the registry's client and analyzer wrappers, as #3977 set up.

Ordering

#3983 → this issue → #3980 (rescore every current version under v5). #3979 (the scoring-queue claim race) and #3863 (the sensitive fallback on rescore) also land before #3980. If #3863 changes the package, pin a version that carries it too.

Acceptance

• The pin and the vectors both name the same package version, and that version includes #3983.
• The shared vectors pass in the registry test.