Native P1S gateway preview (v0.3.0)

Bambu Bridge can expose a registered P1S to native Orca clients over a private LAN/Tailscale address. Settings → Orca · native P1S adds the “Expose to Orca as a P1S” checkbox, a separate one-time access code, rotation, disable and unicast discovery.

The gateway multiplexes the existing MQTT and camera sessions and proxies implicit FTPS. Native print commands preserve plate selection and per-print AMS mapping or external-spool selection. An upload receives success only after it reaches the printer. Physical printer/Orca limitations still apply; the gateway does not add automatic mixing of AMS and external spool. Native mode grants full printer control and uses the printer's validation path.

Server setup requires an explicit private bind address and access to TCP 8883/990/6000 plus passive FTPS data ports. Codes are hashed, management requires owner authentication over HTTPS, and disabling closes native sessions. No proprietary networking library or vendor credential is bundled.

Validation: real TLS protocol fixtures cover status, commands, camera, FTPS upload/download, authentication and disconnects. Owner authorization, Ruff, mypy and responsive Chromium setup checks pass. The full Python 3.12/3.13 CI matrix passed on this commit. A physical print and installed Orca UI acceptance remain unverified.

Setup: https://github.com/thereprocase/bambu-bridge/blob/feature/native-p1s-gateway/docs/NATIVE-P1S.md

Additional validation: 904 tests on each of Python 3.12 and 3.13; 895 passed,
9 skipped, zero failures and zero errors. Live protocol checks against a P1S
confirmed AMS/external-spool status, a read-only command acknowledgement,
camera JPEG framing and dimensions, and an FTPS file listing. Browser checks
confirmed the native checkbox at 320/1440/3840 pixels over normally verified
HTTPS, with no JavaScript errors. Temporary test access was disabled.
An actual print and installed Orca UI acceptance remain unverified.