chore(broadcast-client): document deep-link diagnostics

What changed:

- Keep broadcast deep-link warnings for host app integration failures.

- Add narrow lint justifications for the two intentional console diagnostics.

Warning impact:

- @bytelyst/broadcast-client no-console: 2 warnings -> 0 warnings.

Verification:

- pnpm --filter @bytelyst/broadcast-client build

- pnpm --filter @bytelyst/broadcast-client test

- pnpm --filter @bytelyst/broadcast-client exec eslint . --ext .ts,.tsx

- pnpm typecheck

- pnpm test

- pnpm lint

Co-Authored-By: GPT-5 Codex <noreply@openai.com>

packages/broadcast-client/src/deep-link.ts

@@ -95,6 +95,7 @@ export class DeepLinkRouter {
       return true;
     }
 
+    // eslint-disable-next-line no-console -- Deep-link consumers need an opt-in diagnostic when a route is dropped.
     console.warn(`[DeepLink] No handler for screen: ${route.screen}`);
     return false;
   }
@@ -105,6 +106,7 @@ export class DeepLinkRouter {
   process(url: string): boolean {
     const route = this.parseDeepLink(url);
     if (!route) {
+      // eslint-disable-next-line no-console -- Parse failures are intentionally surfaced to host apps during integration.
       console.warn(`[DeepLink] Failed to parse: ${url}`);
       return false;
     }