refactor: strip WP-/RB- ticket refs from apps and libs (RD-18)

204 WP-NN/RB-NN comments named a closed ticket instead of the code they
sit next to. git blame already records history and stays correct when
code moves; the comment does not. This sweep removes the reference and
keeps the sentence, across 95 files in apps/ and libs/ plus the
behaviour-spec generator's header text.

Eleven references stay: five story files justify an a11y disable per
the README's rule, and one line in a11y.mdx documents that convention.
Two sentences needed a rewrite, not a deletion, so the reference's
meaning survives its removal. behaviour-spec.mdx is regenerated, not
hand-edited.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

scripts/gen-behaviour-spec.mjs

@@ -180,7 +180,7 @@ const beSections = beClasses.map(renderBeSection).join('\n\n');
 const mdx = `{/* GENERATED by \`npm run gen:behaviour-spec\` (scripts/gen-behaviour-spec.mjs) — do not
 edit. Every bullet below is a real \`it()\` title or backend test method name, extracted
 verbatim from the suite. The team rejected Cucumber/Gherkin for BDD scenarios (runtime string
-matching undoes the compile-time guarantees WP-70 bought, and needs two frameworks for
+matching undoes the compile-time guarantees the TypeScript compiler bought, and needs two frameworks for
 .NET+TS) — this page is the replacement: business-readable documentation generated FROM test
 names, so it can never drift from what the suite actually asserts. A test name changing (or a
 test being added/removed) is the only way this page changes; hand-editing it is pointless,