fix: prepare beta19 footer rows, JEV gateway and computer capture

[Obed0101]

Problem

The locally built 0.1.44-beta.19.local.1 carried three fixes that were never published:

• Prompt status scripts could only produce a single footer line, so richer status output was squeezed or truncated.
• Adaptive reasoning (JEV) evaluation only accepted OpenRouter as provider.
• computer_capture rejected null for region/windowID. Strict tool transports that require every key had no valid way to request a main-display capture (some models sent 0 as a placeholder window ID).

Solution

• Footer rows: a status script may return {"rows": [[...], [...]]} (max 4 rows, 32 segments, 240 chars, control characters stripped). Segments carry breakBefore; the TUI renders them through one shared PromptStatusLines component, replacing four duplicated inline renderers. Legacy JSON/TSV/text output remains single-line. Scripts receive MEND_TUI_STATUS_FORMAT=rows-v1.
• JEV provider: provider accepts openrouter or vercel-ai-gateway; each binding has its own endpoint, model and provider routing, and the gateway response is validated with its own schema and normalized to the existing shape. Consent, credential and redaction checks are unchanged.
• Computer capture: region and windowID accept null as absent; validation (positive window ID, integer crop bounds, no combined selectors) is unchanged.

Verification

• bun test on adaptive-reasoning (jev/policy/runtime), tui-prompt-chrome, computer, prompt-status and TUI prompt suites: 252 pass, 0 fail.
• tsgo --noEmit: clean.
• The same source was built and run locally as 0.1.44-beta.19.local.1.

Risks

• Vercel AI Gateway binding is covered by request/response unit tests with mocked fetch; no live gateway call was made.
• Multiline footer is opt-in via rows; existing scripts are unaffected.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}