@tonyruan/dsh-bridge-host 0.1.1-beta.10 → 0.1.1-beta.11

package/README.md

@@ -1,10 +1,14 @@
-# beta.10 / build30: confirmed-pair automatic login and direct management
+# beta.11 / build31: restart recovery and actionable diagnostics
 
-After explicit local pairing confirmation authorizes automatic login, compatible clients can receive this DSH instance's native process-owner launch token only through the authenticated Noise-encrypted channel. Existing paired devices retain manual login; old trust does not silently gain token access. Revocation blocks future grants and trusted Noise access, but cannot retroactively revoke an already issued native token or cookie.
+Linux profile ownership now uses the kernel flock mutex. Normal close, process death and reboot release ownership while the format marker stays in place. Existing profile.json identity and pairing data are unchanged. Linux requires the existing /usr/bin/flock from util-linux; unsafe or ambiguous legacy empty locks remain preserved rather than being silently deleted. Older releases cannot reopen the new persistent lock marker on downgrade.
 
-Management requires verified physical LAN provenance or separately marked, pinned and paired LOCAL_DIRECT business transport. Relay, forged labels or headers, unpaired identities and the login-control channel cannot gain management authority. LAN-only transport remains independent of update and diagnostic service configuration. Existing identities, pairings and user configuration are not rewritten.
+An existing opted-in diagnostic identity loads before the business profile. Startup failures retain an authenticated read-only status/report surface and an independent uploader. The original validated deployment can supply the receiver before identity storage is available; a separate public receiver cache then keeps logging independent of backend changes. No new identity or opt-in is created during startup. A trusted receiver and registered diagnostic public key are still required.
 
-Focused source and real local TCP/Noise cross-feature checks passed. Real native credential/cookie exchange, physical-LAN NIC and cross-WSL acceptance were not exercised. No WSL or firewall setting is changed by this release.
+Fixed v1 events distinguish profile locks, transport refusal, TLS, native login and cookie failures without exception text, addresses, tokens or business content. Important records persist before upload, with one-second batches and bounded backoff; offline records replay under the same key. Opt-out still stops collection and upload. The native settings page has a support-report download with public state and allowed diagnostic events only.
+
+Actual native DSH 0.2.2-rc.1 testing upgraded the formal beta.10 installation, retained identity/pairing and diagnostic keys, reproduced an old empty lock, and located it from signed TLS1.3 records stored on an isolated cloud collector. Refused TCP, rejected token, expired cookie, offline replay and SIGKILL restart were verified. Windows runtime protocol testing used Linux with explicit loopback carrier adapters; it does not claim a second physical-device LAN or Windows GUI/DPAPI test. The production relay was not reconfigured or restarted.
+
+Diagnostic version 0.1.31 corresponds to Host build31. The existing signed v1 ingestion schema remains compatible with older clients.
 
 # DSH Bridge host beta