Add packaged DLP broker and protected Windows service foundation

docs/native-runtime/README.md

@@ -1,11 +1,39 @@
 # Chromium 152 WebRTC binder backport
 
+## Cancelled implementation path — stock runtime required
+
+The user explicitly rejected rebuilding Chromium/Electron on2026-10-14. The
+owned native build was stopped and its terminal failure/cancellation evidence
+retained. No custom binary was activated or shipped. This document's backport,
+compiler and source-checkout records are historical evidence, not instructions
+to resume that implementation. **Do not restart this build or make a custom
+Chromium runtime a product dependency.**
+
+The current direction is an unchanged official Electron/Chromium runtime plus
+an independently enforced Windows network boundary and separate controlled DLP
+broker. This alternative is not yet implemented or accepted. The existing relay
+allows opaque CONNECT forwarding and shares Electron's executable/process with
+upstream management traffic, so merely adding per-executable firewall blocking
+or removing the WebRTC header would not provide the required boundary. Retain
+the present protection until hostile native transport and DNS tests prove its
+replacement. A JavaScript constructor wrapper alone is insufficient.
+
 Status: source patch prepared and checked; **not compiled or runtime verified**.
 Do not distribute this patch as a proven security fix until the acceptance gates
 below pass against the resulting binary.
 
 ## Latest stable candidate checked
 
+On2026-10-14 the newer official Electron44.7.2 Windows x64 binary was also tested.
+Its ZIP matches the official SHA256 manifest:
+`10a89447ef64ac5cb9f782af48ffd83734a40ae91681259d1048ca3c9e6c5da4`.
+Both initialabout:blank andsrcdoc positive controls delivered exact synthetic
+RTC data and benign POSTs. Both corresponding managed-policy cases still
+crashed with missing MdnsResponder, bad IPC123 and renderer exit3. The earlier
+run's positive timeout remains preserved separately. Evidence:
+`artifacts/native-rtc-4472-second-proof.json`. No project dependency was upgraded.
+Thus this newly available binary does not replace the native backport either.
+
 The official [Electron44.7.1 release](https://github.com/electron/electron/releases/tag/v44.7.1)
 uses Chromium152.0.7977.149. Its Windows x64 ZIP was downloaded into an isolated
 ignored directory, checked against the official SHA256 manifest and extracted
@@ -254,6 +282,61 @@ is not identified as a compiler tool, but the official full sync remains failed.
 This read-only analysis authorizes neither skipping dependencies nor changing
 antivirus policy. ATL/MFC remains independently missing at the host check.
 
+## Alternative dependency installation, 2026-10-14
+
+The normal Microsoft installer subsequently completed. `vswhere` now finds
+`Microsoft.VisualStudio.Component.VC.ATLMFC` in the existing BuildTools instance
+and reports both `isComplete=true` and `isLaunchable=true`; the installer process
+has ended. Ignored evidence: `artifacts/native-build/atl-mfc-installed-proof.json`.
+Thus the earlier missing-component prerequisite is resolved. This does not by
+itself prove a generated GN graph or a working native compilation.
+
+The user's explicit alternative-build request was implemented without changing
+Defender. A reviewed CIPD ensure manifest preserves all forty original requested
+package/subdirectory/version bindings from the existing `.gclient_entries`,
+except the single rejected Chrome-x86 updater fixture described above. The
+thirty-nine remaining bindings were processed by the official CIPD client with
+exit0 in119.7seconds. No new antivirus error occurred. Original version tags
+were preserved; this is not a claim that every tag was resolved offline to an
+immutable instance ID. The source entries and both manifests retain their
+verified hashes. Native Chromium/Electron HEADs and captured references remained
+unchanged before/after; no full Git sync or patch replay occurred.
+
+Ignored evidence: `cipd-manifest-offline-proof.json`,
+`cipd-reviewed-ensure-journal.json` and `cipd-reviewed-ensure.log` under
+`artifacts/native-build`. The original failed full sync remains retained.
+Updater regression tests using the omitted fixture are not accepted. A generated
+Electron/native-test GN dependency graph must confirm that the omitted target is
+not needed before compiling. Required hooks, ATL/MFC, compilation and real native
+acceptance remain separate gates. The signed Microsoft installer was launched
+through normal Windows UAC; installation is not confirmed by starting it.
+
+The selected original RC and four version-generation hooks subsequently exited0.
+RC matches its checked-in SHA1 and has recorded SHA256 provenance. Electron's
+Yarn4.18.0 immutable install also completed with unchanged lockfile and config.
+`enableScripts:false` stayed set, but the upstream workspace fixtures and explicit
+`dependenciesMeta.built:true` entries executed their permitted builds; this is
+not an all-scripts-disabled claim. All native HEAD/reference snapshots remained
+unchanged, with no Defender modification or new antivirus error. Evidence:
+`selected-hooks-journal.json` and per-action logs. The official local toolchain
+check also exited0, recognizing VS2022 and Windows SDK10.0.26100.0 without a Google
+toolchain download (`local-toolchain-proof.json`). GN generation, target-graph
+verification and product compilation remain separate steps.
+
+GN generation subsequently succeeded in the fresh `out/SafetyNetTestingPython314`
+directory with the supported explicit Python interpreter switch; the original
+Windows-Store-alias failure remains retained. Actual recursive GN graphs for
+Electron and content_unittests contain no omitted updater-fixture dependency.
+Both NoOp test sources are present and `enable_mdns`/`is_p2p_enabled` are true.
+Evidence: `gn-generation-python314-proof.json` and `gn-target-graph-proof.json`.
+Physical Ninja aliases were also checked. The initial compile launch was
+controlled-stopped before observed compiler progress for insufficient memory;
+that failed attempt remains retained. A fresh continuation started only after
+the measured available commit memory exceeded4GiB, using one compiler job,
+bounded disk/memory guards and no remote execution. This running build is not
+yet a completed compilation or native acceptance. The shipped runtime remains
+unchanged until the required real tests pass.
+
 ### Patch readiness before compilation
 
 ATL/MFC is required for the native toolchain, not for the Python patch import