Add opt-in Jev advice with users' own OpenRouter keys

[NellInc]

Scope

• Add optional Jev incident-queue advice to desktop and mobile AI Partner views.
• Users supply their own OpenRouter key. Credentials remain in memory while the Advisory tab is open, never in browser storage or the shipped bundle.
• Require explicit consent and manual submission. No automatic requests, retries, alert clearance, or machine commands.
• Validate provider/model/output, cancel outstanding work on edits or close, and expire suggestions.
• Permit the fixed OpenRouter endpoint through the existing CSP.
• Add built-assembly desktop/mobile browser acceptance to CI using synthetic credentials and intercepted responses.

Release-blocking repair

Exact v0.40 browser acceptance exposed the existing batcher's traversal of React ownership metadata. Include the small existing development fix that excludes __r3f from material signatures, plus two regression tests. Both tests failed before the repair; all 26 batching tests pass afterward. The built release now finishes batching and completes both Jev UI flows.

Verification

The Jev implementation and acceptance harness were authored in this task. The batching repair was adopted from local development and independently reproduced and verified.

• 1,392 tests passed, zero failures (baseline 1,354; 36 Jev tests and two batching regressions added).
• Build, typecheck, lint, formatting, release matrix, bundle budget and reachability passed locally.
• Exact v0.40 built assembly passed desktop 1440px and mobile 390px submissions, consent gating, no unsolicited calls, key forgetting and no key persistence. No browser exceptions, console errors, failed requests or CSP violations.
• A real synthetic provider request with the same Jev client returned HTTP 200 in prior development-assembly validation. Live-domain verification follows deployment.
• Final hosted CI must pass before merge, including depth/shader contracts and agent checks.

Thirteen files are included: nine Jev integration files, two browser-CI files, and the narrow two-file batching repair. Other v0.50 development, model assets, dependencies and the deployment workflow remain excluded.