BioLinkPipe is standalone

Two pipes share the name

There are two classes called BioLinkPipe.

cast-link.pipe.ts exports the one named bioLink. Creator profiles use it on the bio. It was already standalone.
isLink.pipe.ts exports the one named isLink. It wraps URLs in empty <a> tags. No template uses it, and no file imports the class. It still sat next to pipes that posts and messages do use, with standalone: false.

This commit only drops that flag from the unused pipe, so it matches the other pipes in the same file. I did not delete it. Deleting unused files is a later follow-up.

Commit 27d6a631e0: make BioLinkPipe standalone

1 file, +1 −2

What changed

Removed standalone: false from the isLink pipe.

How I checked it

Check	Result
Compiled template dependencies against PR 10841	All 646 components match. No component's template referenced this pipe before or after.
QA and development builds	Both pass. QA has the same 42 warnings as before.
Initial bundle and lazy routes	Unchanged. Initial JS is 7,123,873 bytes with 276 files. Profile, messages, post detail and dashboard match byte for byte.
Server rendering, 145 URLs	All match PR 10841.
ESLint on the changed file	No errors.

I did not run a logged-in white-label sweep. No page renders this pipe, so a browser walk would not touch the change.

What's left

AppModule and AppServerModule are the last NgModules. The app still starts with bootstrapModule.
Four unused components only the deleted SharedModule used are still in the tree, plus the other dead files in the follow-ups.

Verification checklist

Use a creator account on its white-label site. Keep the console open. Checks are saved in this browser.

0 of 0 checked

Medium The profile pipe that still runs

Open a creator profile with URLs in the bio. Links still wrap and open.
Open a post and a message that contain URLs. Those still use the isURL pipe from the same file, and they still link.