fix(search): repin on b44d7a5 — B = 0.3, found by a consumer's smoke test

@imqueue/mcp asserts that no blog post outranks a doc page for "How do I expose
a method on an @imqueue service?". At B = 0.85 it failed, because
/api/#service-and-client is a long section and the length correction took it
257 -> 226, under a blog answer record at 229 that never moved — tier-1 records
have no length normalisation.

The gated intent set is unaffected: recall@6 84.2% either way, and its accuracy
peaks at 0.3 (micro +3.68, macro +3.19 against 27e5b35, 5 better / 0 worse). The
question set gives back half its gain. Full suite green with the watcher
stopped: build:all exit 0, npm test exit 0 / 218 checks, kpi:intent at its floor.

Worth noting for the next ranker change: this regression was invisible to
imqueue.com's own suite, because the assertion that caught it lives in the MCP
repo. Run `npm run verify` there before pushing a ranker repin.

Author: Mikhus