Add packaged DLP broker and protected Windows service foundation

README.md

@@ -11,20 +11,29 @@ SafetyNet combines an Electron/Chromium desktop browser, an administrator web co
 The current milestone is the [Windows DLP MVP](docs/windows-dlp-mvp.md): enforce
 confidential-content checks before browser clipboard release and outbound text
 or file transmission, with central policy and local semantic inspection.
-Native public/blocked transfer and restart fixtures pass. Final acceptance is
-still open: a reproducible Chromium WebRTC renderer crash in initial blank
-iframes requires a verified native fix. Other platforms and broader features
-remain outside this milestone.
+S Browser uses official, unchanged Electron/Chromium releases. It does not require
+a custom Chromium build or changes to installed Chrome. Browser, DLP broker,
+private runtimes, scanners and models are intended to ship in one Windows
+installer; the new broker component package is verified separately.
+
+Final acceptance is still open: the main browser must be connected to the
+protected Windows service, with verified installation and network enforcement.
+A reproducible WebRTC renderer crash remains; the existing restriction stays
+until its replacement is tested. See the [current acceptance matrix](docs/core-dlp-current-status.md)
+for completed component tests and remaining integration work. Other platforms
+and broader features remain outside this milestone.
 
 [Native transport auditing](docs/native-transport-observability.md) records
 tested WebTransport lifecycle attempts without exposing raw browser debugging
-APIs. Its observation channel preserves clipboard protection; unsupported
-transport payloads remain blocked by the native relay boundary.
+APIs. Its observation channel preserves clipboard protection. These tests do
+not establish the new Windows network boundary or complete transport coverage.
 
 [Bounded diagnostics](docs/diagnostics-backpressure.md) preserve authorized
 exports through policy-version updates and cancel them when permissions change.
-Current native clipboard, upload, restart, local Gemma and transport fixtures
-pass with zero lifetime export failures; historical failures remain documented.
+Controlled clipboard, upload, restart, local Gemma and transport fixtures have
+export evidence; historical failures remain documented. Production broker
+diagnostics, durable audit delivery and final installer acceptance remain separate
+requirements.
 
 S Browser uses translucent materials, rounded controls, light/dark themes, and a content-first layout inspired by Safari. Website content is left unchanged.
 
@@ -194,7 +203,14 @@ npm run package:win
 npm run verify:package
 ```
 
-The packaging workflow produces an unpacked evaluation build in `dist/win-unpacked`. Distribute the complete folder, not the executable alone. Code signing, a production installer and a trusted update service remain unfinished.
+The existing evaluation build is an unpacked application in `dist/win-unpacked`.
+The required release deliverable is one Windows installer containing the browser,
+its separate DLP broker and private runtime, local scanners and semantic models.
+It must require no separately installed Node/Python or manual broker startup.
+That complete installation and automatic browser-to-broker integration are still
+being implemented and verified. An unpacked folder or broker payload alone does
+not prove this deliverable. Code signing and a trusted update service remain
+unfinished.
 
 ## Current boundaries