@debugbundle/cli 1.14.0 → 1.16.0

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.
Files changed (3) hide show
  1. package/README.md +18 -0
  2. package/dist/main.cjs +667 -289
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -63,6 +63,24 @@ Portable plugin skills complement the project's profile and workflows. Setup doe
63
63
 
64
64
  The CLI reads local project configuration from `.debugbundle/` and can use member-token authentication for connected cloud operations. Use `debugbundle connect` to configure cloud access, or pass `--auth-file` to commands that support explicit auth state.
65
65
 
66
+ ## Public status pages
67
+
68
+ Owners can publish selected health checks from their own projects through a stable public link:
69
+
70
+ ```sh
71
+ debugbundle health status get --project-id <id> --json
72
+ debugbundle health status options --project-id <id> --json
73
+ debugbundle health status save --project-id <id> --settings-json '<settings>' --json
74
+ debugbundle health status preview --project-id <id> --json
75
+ ```
76
+
77
+ Settings contain `title`, `enabled` and explicit `projects` entries with `project_id`
78
+ and `check_ids`. Save with `enabled: false` to unpublish while retaining the URL.
79
+ Only selected names and aggregate availability are public; endpoint URLs and
80
+ diagnostics stay private. New checks remain private. Use member authentication
81
+ and publish only on the owner's instruction. See the
82
+ [status-page guide](https://debugbundle.com/docs/availability-checks/).
83
+
66
84
  ## AnalyticsBundle
67
85
 
68
86
  Public project flows support customer-defined acquisition and activation steps across sites,