Add governed paired-worker Remote Assist

[Chris-ObtuseAI]

What changed

• adds optional paired-owner Remote Assist for opted-in Windows workers
• adds a dedicated authenticated QUIC protocol for bounded JPEG frames and ordered mouse, keyboard, and wheel input
• binds signed authority to the worker, pinned controller, session, mode, epoch, expiry, dimensions, and frame rate
• limits authority to renewable 30-second leases and one visible session per worker
• persists replay fencing across worker-agent restart
• adds worker opt-in, active tray/app warning, close/revoke, and local STOP behavior
• adds the native owner viewer with View desktop and Control desktop modes
• bumps every public release surface to 0.3.0
• updates the README, landing page, download route, platform matrix, release notes, evidence ledger, checksums, and source-current UI showcase

Why

A paired worker should not become a black box once it joins the fabric. The owner can now inspect or help that worker from the main Rampage desktop without adding a separate remote-access account or giving the autonomous intelligence layer desktop authority.

Security boundary

Remote Assist is off by default and can be enabled only on a paired Windows worker. Requests are accepted only from the pinned controller identity and only while the exact shipped capability is fresh. The intelligence service has no controller key, lease-signing key, desktop API, enrollment authority, or STOP bypass.

This is not elevation or unattended administration. It exposes no shell or file-transfer primitive and cannot cross Windows UAC, the lock screen, the secure desktop, or higher-integrity applications. Toggle-off, viewer close, lease expiry, or local STOP revokes access.

Validation

• scripts/Test-Rampage.ps1 -SkipOllama — PASS, uninterrupted full repository campaign
• strict cargo clippy --workspace --all-targets -- -D warnings — PASS
• desktop, edge, TypeScript SDK builds/tests — PASS
• Python lint, typing, intelligence tests, and SDK tests — PASS
• controller lifecycle, authenticated QUIC mesh/storage, and universal model-gateway e2e — PASS
• scripts/Build-Rampage.ps1 -Profile release — PASS
• NSIS installation, six payloads, desktop shortcut, Rampage Shell, packaged startup, close-to-tray, clean exit, uninstall, and no sidecar leak — PASS
• MSI and NSIS SHA-256 hashes recorded in docs/RELEASE_EVIDENCE_0.3.0.md
• scripts/Assert-RampageVersion.ps1 -Tag v0.3.0 — PASS across nine surfaces
• scripts/Validate-Showcase.ps1 — PASS

Honest boundary

The landing screenshot is a source-current showcase, not a physical two-machine receipt. The owner-to-laptop interactive control campaign remains explicitly pending until 0.3.0 is installed on both physical machines. Windows release binaries remain unsigned until Authenticode credentials exist and verification succeeds.