[Shpuntyara]

The protected broker previously had no admitted operation context for remote workers, and a lost Windows reply had no Windows-side outcome boundary. This adds opt-in context-v2 worker input and a fixed HTTPS/PSRP bridge to an owner-registered finite-task JEA endpoint. Windows records intent and exact input/operation bindings before dispatch, replays completed receipts, and quarantines uncertain outcomes instead of repeating a write.

Owner bundle preparation and byte-bound bootstrap remain separate from execution admission. The endpoint privately loads OS-owned dependencies while exporting only three functions. Legacy broker worker input remains byte-compatible. Platform version is 0.16.0, with core/contracts 0.8.0 and Windows module 0.5.0.

Validation at d36b944:

• All 34 CI check runs completed successfully, including native Linux worker isolation and actual certificate-authenticated HTTPS/JEA on a disposable non-domain Windows runner.
• Native Windows acceptance covers controlled writes, exact replay, genuine CA/hostname verification failures, hidden bare and module-qualified commands, default PS/WinRS certificate-URI refusals, lost replies, failure-after-write quarantine, and verified cleanup of owned resources and service configuration.
• Fresh-process/no-autoload regressions verify private dependencies and exactly three public functions. Two independent agent reviews completed; material findings were fixed.
• Deterministic 339-file release candidate built and verified: SHA256 42b6b1afd556c25f04008f17f2c71cf4fed89e4c9d1991290ae765807630c1a2.

This is a transport and endpoint foundation. It installs no AD task, real credential, signing authority, broker deployment or protected desktop session. Kerberos/gMSA delegation, actual requester isolation and the live AD/GPO recovery matrix remain not_run until independent owner provisioning and acceptance. Certificate-URI refusals in CI do not establish a deployed Kerberos/default-endpoint ACL. PR #34 remains separate and draft.