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

package/LICENSE

@@ -0,0 +1,131 @@
+# PolyForm Noncommercial License 1.0.0
+
+<https://polyformproject.org/licenses/noncommercial/1.0.0>
+
+## Acceptance
+
+In order to get any license under these terms, you must agree
+to them as both strict obligations and conditions to all
+your licenses.
+
+## Copyright License
+
+The licensor grants you a copyright license for the
+software to do everything you might do with the software
+that would otherwise infringe the licensor's copyright
+in it for any permitted purpose.  However, you may
+only distribute the software according to [Distribution
+License](#distribution-license) and make changes or new works
+based on the software according to [Changes and New Works
+License](#changes-and-new-works-license).
+
+## Distribution License
+
+The licensor grants you an additional copyright license
+to distribute copies of the software.  Your license
+to distribute covers distributing the software with
+changes and new works permitted by [Changes and New Works
+License](#changes-and-new-works-license).
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of
+the software from you also gets a copy of these terms or the
+URL for them above, as well as copies of any plain-text lines
+beginning with `Required Notice:` that the licensor provided
+with the software.  For example:
+
+> Required Notice: Copyright Yoyodyne, Inc. (http://example.com)
+
+## Changes and New Works License
+
+The licensor grants you an additional copyright license to
+make changes and new works based on the software for any
+permitted purpose.
+
+## Patent License
+
+The licensor grants you a patent license for the software that
+covers patent claims the licensor can license, or becomes able
+to license, that you would infringe by using the software.
+
+## Noncommercial Purposes
+
+Any noncommercial purpose is a permitted purpose.
+
+## Personal Uses
+
+Personal use for research, experiment, and testing for
+the benefit of public knowledge, personal study, private
+entertainment, hobby projects, amateur pursuits, or religious
+observance, without any anticipated commercial application,
+is use for a permitted purpose.
+
+## Noncommercial Organizations
+
+Use by any charitable organization, educational institution,
+public research organization, public safety or health
+organization, environmental protection organization,
+or government institution is use for a permitted purpose
+regardless of the source of funding or obligations resulting
+from the funding.
+
+## Fair Use
+
+You may have "fair use" rights for the software under the
+law. These terms do not limit them.
+
+## No Other Rights
+
+These terms do not allow you to sublicense or transfer any of
+your licenses to anyone else, or prevent the licensor from
+granting licenses to anyone else.  These terms do not imply
+any other licenses.
+
+## Patent Defense
+
+If you make any written claim that the software infringes or
+contributes to infringement of any patent, your patent license
+for the software granted under these terms ends immediately. If
+your company makes such a claim, your patent license ends
+immediately for work on behalf of your company.
+
+## Violations
+
+The first time you are notified in writing that you have
+violated any of these terms, or done anything with the software
+not covered by your licenses, your licenses can nonetheless
+continue if you come into full compliance with these terms,
+and take practical steps to correct past violations, within
+32 days of receiving notice.  Otherwise, all your licenses
+end immediately.
+
+## No Liability
+
+***As far as the law allows, the software comes as is, without
+any warranty or condition, and the licensor will not be liable
+to you for any damages arising out of these terms or the use
+or nature of the software, under any kind of legal claim.***
+
+## Definitions
+
+The **licensor** is the individual or entity offering these
+terms, and the **software** is the software the licensor makes
+available under these terms.
+
+**You** refers to the individual or entity agreeing to these
+terms.
+
+**Your company** is any legal entity, sole proprietorship,
+or other kind of organization that you work for, plus all
+organizations that have control over, are under the control of,
+or are under common control with that organization.  **Control**
+means ownership of substantially all the assets of an entity,
+or the power to direct its management and policies by vote,
+contract, or otherwise.  Control can be direct or indirect.
+
+**Your licenses** are all the licenses granted to you for the
+software under these terms.
+
+**Use** means anything you do with the software requiring one
+of your licenses.

package/README.md

@@ -1,3 +1,26 @@
-# Temporary Holding Version
+# beta.11 / build31: restart recovery and actionable diagnostics
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+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.
+
+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.
+
+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
+
+A community DSH-compatible phone-access plugin, not an official DeepSeek product. Requires Node.js >=24.9.0 and DSH0.2.2-rc.1.
+
+Package: @tonyruan/dsh-bridge-host. Use the official DSH plugin manager for installation; stop the target profile before package-name migration. Cordis ID dsh-phone-access, plugin name phone-access, API routes and existing profileDirectory/identity remain stable. The default profile is the existing .dsh-phone-profile; changing an npm name does not authorize replacing data.
+
+This generic build contains no personal relay preset or update root/feed. Without relay configuration, new and existing profiles use LAN-only while preserving their identity and paired devices. Existing saved relay configuration is reused. To retain relay access when replacing an old private code-only preset, use the previously supplied local deployment migration helper before replacing it. LAN-only alone neither enables nor blocks independently configured update or diagnostic services.
+
+Own project code is licensed under the standard PolyForm Noncommercial License1.0.0 in LICENSE. This is not OSI open-source; permitted purposes and exceptions are governed by that exact text, not a blanket promise about every business/payment scenario. Third-party components retain their own permission, copyright and NOTICE terms in THIRD-PARTY-NOTICES.txt and oss-licenses/. These own-code terms do not restrict upstream rights. The complete own development project/Git repository is not included; npm runtime JavaScript is publicly readable. Native platform download assets are not included in this npm release.
+
+
+Beta6/build26 retains the original validated persisted connection realm across upgrades and LAN-only restarts, including previously paired WSS realms without an unused relay leaf. Existing trusted deployment is reused without import or rewrite. AUTO still requires trusted TLS material. Legacy private code-only presets require the separately delivered Linux pre-upgrade migration helper before replacement; it statically validates the original local package and pin, never executes old code or fetches a new network leaf. No identity/pairing/schema reinitialization or client update-source JSON is required. 
+
+Beta7/build27 fixes the setting sidebar icon through the native settings.section.icon slot, without changing the phone-connection name or the general settings icon. An already-native-authenticated hostname may be used only for independently proven direct LAN sockets; the private internal flag cannot authorize relay, unknown, virtual/VPN or unverified interfaces, or bypass native Cookie/Host/Origin. The UI distinguishes native admission403 from the plugin fixed management403, and both remain blocked. Targeted raw-LAN positives use synthetic interface facts; the actual rc.1 browser/navigation checks use an isolated loopback profile. The real user Ubuntu version and route were not inspected, so site-specific resolution and a real physical-LAN success are not claimed.