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>

libs/beheer/src/application/stamdata.store.spec.ts

@@ -44,7 +44,7 @@ function setup(blobPresenter?: BlobPresenter): StamdataStore {
   return TestBed.inject(StamdataStore);
 }
 
-describe('StamdataStore undo/redo (WP-32)', () => {
+describe('StamdataStore undo/redo', () => {
   it('records a cell edit, undoes and redoes it', async () => {
     const store = setup();
     await store.load();
@@ -82,10 +82,10 @@ describe('StamdataStore undo/redo (WP-32)', () => {
   });
 });
 
-// --- RB-28 (TE-006): download() ends in BLOB_PRESENTER.download, not raw DOM calls,
+// --- TE-006: download() ends in BLOB_PRESENTER.download, not raw DOM calls,
 // so the seam makes both the guard's branches and the success path assertable. ---
 
-describe('StamdataStore.download (RB-28)', () => {
+describe('StamdataStore.download', () => {
   it('does not call the presenter while the two-clause guard blocks (nothing dirty yet)', async () => {
     // Given a freshly loaded table with no edits — canDownload() is false.
     const { presenter, downloaded } = fakeBlobPresenter();