@hunsu/bridge 0.1.3 → 0.2.0-next.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md ADDED
@@ -0,0 +1,39 @@
1
+ # @hunsu/bridge
2
+
3
+ The headless Hunsu Bridge daemon and its authenticated CLI client.
4
+
5
+ > The headless prerelease is experimental. An exact candidate is published
6
+ > under `candidate-next` and reaches `next` only after registry, service, and
7
+ > production verification.
8
+
9
+ ```sh
10
+ npx @hunsu/bridge@next setup
11
+ npx @hunsu/bridge@next status
12
+ npx @hunsu/bridge@next open
13
+ ```
14
+
15
+ Preview QA uses the same canonical package with an explicit durable profile:
16
+
17
+ ```sh
18
+ npx @hunsu/bridge@candidate-next setup --profile preview
19
+ ```
20
+
21
+ `production` is the default profile. A populated `HUNSU_HOME` cannot switch
22
+ profiles; use a clean QA OS user or home for preview. The installed service
23
+ persists the selected profile and ignores ambient Web and Connect endpoint
24
+ overrides.
25
+
26
+ The installed user service runs an exact package version from `HUNSU_HOME`, not
27
+ from the npm cache. Use `hunsu-bridge dev --port 0` for an isolated foreground
28
+ development daemon. Development mode may use explicit endpoint overrides;
29
+ installed daemons use only the profile endpoint allowlist.
30
+
31
+ For advanced local package verification only, run setup from an absolute
32
+ tarball path:
33
+
34
+ ```sh
35
+ hunsu-bridge setup --runtime-package /absolute/path/hunsu-bridge-0.2.0-next.10.tgz
36
+ ```
37
+
38
+ This option rejects URLs, dist-tags, ranges, Git specs, relative paths, and
39
+ packages other than the exact `@hunsu/bridge` candidate.