@pixelkit-labs/cli 1.4.3 → 1.5.1

package/README.md

@@ -1,6 +1,6 @@
 # @pixelkit-labs/cli
 
-Command-line diagnostics for [PixelKit](https://www.npmjs.com/package/pixelkit). Its only command,
+Command-line diagnostics for [PixelKit](https://www.npmjs.com/package/@pixelkit-labs/sdk). Its only command,
 `pixelkit doctor`, answers "why is everything showing —?" before you file an issue.
 
 PixelKit hooks report `source: 'unavailable'` and render an em dash when a reading cannot be taken
@@ -40,7 +40,7 @@ npx pixelkit doctor
 6. **Whether `adb reverse tcp:8081 tcp:8081` is set**, so a development client can reach Metro on
    localhost.
 
-Each check is reported as `PASS`, `FAIL`, `N/A`, or `????` ("could not be determined" — the check
+Each check is reported as `PASS`, `FAIL`, `N/A` or `UNKN` ("could not be determined" — the check
 itself could not be run, for example because adb is missing or the device went offline).
 `doctor` never guesses a result: an inconclusive check is reported as such, the same discipline
 PixelKit hooks use for `source: 'unavailable'`.
@@ -61,4 +61,9 @@ pixelkit doctor [--package <id>] [--serial <serial>]
 `0` when every check passed or was not applicable. `1` when any check failed, or could not be
 determined at all.
 
+## Documentation
+
+[https://pixelkit-labs.github.io/pixelkit-docs/](https://pixelkit-labs.github.io/pixelkit-docs/) covers the hooks this command
+diagnoses: each one's inputs, outputs, and what `source: 'unavailable'` means for it.
+
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pixelkit-labs/cli",
-  "version": "1.4.3",
+  "version": "1.5.1",
   "description": "pixelkit doctor: tells you why a PixelKit hardware reading is unavailable instead of leaving you guessing.",
   "keywords": [
     "pixelkit",