@hasna/machines 0.0.32 → 0.0.34

package/README.md

@@ -30,8 +30,8 @@ Endpoints on `127.0.0.1` only:
 ```bash
 machines manifest init
 machines manifest bootstrap
-machines manifest add --id spark01 --platform linux --workspace-path ~/workspace
-machines manifest add --id apple03 --platform macos --workspace-path ~/Workspace --app ghostty:cask
+machines manifest add --id linux-dev-01 --platform linux --workspace-path ~/workspace
+machines manifest add --id mac-lab-01 --platform macos --workspace-path ~/Workspace --app ghostty:cask
 machines manifest validate
 machines manifest list
 ```
@@ -39,11 +39,11 @@ machines manifest list
 ## Provision and reconcile
 
 ```bash
-machines setup --machine spark01 --json
-machines setup --machine spark01 --apply --yes
-machines sync --machine spark01 --json
-machines sync --machine spark01 --apply --yes
-machines doctor --machine spark01
+machines setup --machine linux-dev-01 --json
+machines setup --machine linux-dev-01 --apply --yes
+machines sync --machine linux-dev-01 --json
+machines sync --machine linux-dev-01 --apply --yes
+machines doctor --machine linux-dev-01
 machines self-test
 ```
 
@@ -68,9 +68,9 @@ import {
 console.log(MACHINES_CONSUMER_CONTRACT.schema_version);
 const topology = discoverMachineTopology();
 const local = getLocalMachineTopology();
-const route = resolveMachineRoute("spark01");
+const route = resolveMachineRoute("linux-dev-01");
 const workspace = resolveMachineWorkspace({
-  machineId: "spark01",
+  machineId: "linux-dev-01",
   projectId: "open-knowledge",
   repoName: "open-knowledge",
 });
@@ -115,7 +115,7 @@ CLI and MCP expose the same topology view:
 ```bash
 machines topology --json
 machines topology --no-tailscale --json
-machines route --machine spark01 --json
+machines route --machine linux-dev-01 --json
 ```
 
 ## Screen sharing
@@ -125,9 +125,9 @@ IP bookmarks. The route resolver picks the current LAN address or Tailscale name
 automatically, so it keeps working even when DHCP rotates a machine's IP.
 
 ```bash
-machines screen machine005                 # open Screen Sharing.app → vnc://<user>@<live-route>
-machines screen machine005 --print         # print the vnc:// URL instead of opening
-machines screen machine005 --json          # full resolution detail (route, confidence, user)
+machines screen demo-mac-01                # open Screen Sharing.app → vnc://<user>@<live-route>
+machines screen demo-mac-01 --print        # print the vnc:// URL instead of opening
+machines screen demo-mac-01 --json         # full resolution detail (route, confidence, user)
 machines screen --all                      # open every reachable machine
 machines screen --all --print              # list resolved vnc:// URLs for the whole fleet
 machines screen-credentials --all --check-secret
@@ -138,18 +138,19 @@ Enable Remote Management / Screen Sharing on a fresh macOS machine over SSH
 Screen Sharing.app and Apple Remote Desktop):
 
 ```bash
-secrets set hasna/xyz/opensource/machines/prod/screen-machine005-vnc-password "$VNC_PASSWORD" --type password
-machines screen-enable --machine machine005 --user jo \
-  --vnc-password-secret hasna/xyz/opensource/machines/prod/screen-machine005-vnc-password
-machines screen-enable --machine machine005 --user jo --print   # show the SSH command, don't run it
+secrets set machines/screen-sharing/screen-demo-mac-01-vnc-password "$VNC_PASSWORD" --type password
+machines screen-enable --machine demo-mac-01 --user operator \
+  --vnc-password-secret machines/screen-sharing/screen-demo-mac-01-vnc-password
+machines screen-enable --machine demo-mac-01 --user operator --print   # show the SSH command, don't run it
 ```
 
 The legacy VNC protocol honors only the first 8 password characters. The
 password is read through the `secrets` CLI and piped over SSH stdin; it is not
 embedded in generated command text. If `--vnc-password-secret` is omitted,
 machines defaults to
-`hasna/xyz/opensource/machines/prod/screen-<machine>-vnc-password`. The user
-comes from the manifest (`metadata.user`) when present, or `--user`.
+`machines/screen-sharing/screen-<machine>-vnc-password`, or the namespace set in
+`HASNA_MACHINES_SCREEN_SECRET_NAMESPACE`. The user comes from the manifest
+(`metadata.user`) when present, or `--user`.
 `screen-credentials` verifies the resolved user and secret key for a machine or
 the full fleet without printing secret values.
 
@@ -160,7 +161,7 @@ without importing the full machines app:
 import { resolveMachineWorkspace } from "@hasna/machines/consumer";
 
 const workspace = resolveMachineWorkspace({
-  machineId: "spark01",
+  machineId: "linux-dev-01",
   projectId: "open-knowledge",
   repoName: "open-knowledge",
 });
@@ -175,8 +176,8 @@ diagnostics. It uses explicit manifest metadata first and deterministic
 workspace inference second; consumers can still pass manual overrides.
 
 ```bash
-machines workspace resolve --machine spark01 --project open-knowledge --repo open-knowledge --json
-machines workspace doctor --machine spark01 --project open-knowledge --repo open-knowledge --json
+machines workspace resolve --machine linux-dev-01 --project open-knowledge --repo open-knowledge --json
+machines workspace doctor --machine linux-dev-01 --project open-knowledge --repo open-knowledge --json
 ```
 
 `workspace resolve` and `workspace doctor` include JSON-friendly
@@ -191,8 +192,8 @@ repair the manifest metadata explicitly. The command previews changes by
 default and only writes when `--apply` is passed:
 
 ```bash
-machines workspace repair --machine spark01 --project open-knowledge --repo open-knowledge --json
-machines workspace repair --machine spark01 --project open-knowledge --repo open-knowledge --apply --json
+machines workspace repair --machine linux-dev-01 --project open-knowledge --repo open-knowledge --json
+machines workspace repair --machine linux-dev-01 --project open-knowledge --repo open-knowledge --apply --json
 ```
 
 ## Compatibility SDK
@@ -204,13 +205,13 @@ attempting app-level sync:
 import { checkMachineCompatibility } from "@hasna/machines/consumer";
 
 const report = checkMachineCompatibility({
-  machineId: "spark01",
+  machineId: "linux-dev-01",
   commands: [{ command: "bun" }],
-  packages: [{ name: "@hasna/knowledge", command: "knowledge", expectedVersion: "0.2.29" }],
+  packages: [{ name: "@example/knowledge", command: "knowledge", expectedVersion: "0.2.29" }],
   workspaces: [{
     label: "open-knowledge",
-    path: "/home/hasna/workspace/hasna/opensource/open-knowledge",
-    expectedPackageName: "@hasna/knowledge",
+    path: "/srv/workspaces/open-knowledge",
+    expectedPackageName: "@example/knowledge",
     expectedVersion: "0.2.29",
   }],
 });
@@ -224,16 +225,16 @@ back to its own local checks if `@hasna/machines` is not installed.
 CLI and MCP expose the same shape:
 
 ```bash
-machines compatibility --machine spark01 \
+machines compatibility --machine linux-dev-01 \
   --command bun \
-  --package @hasna/knowledge:knowledge:0.2.29 \
-  --workspace open-knowledge=/home/hasna/workspace/hasna/opensource/open-knowledge:@hasna/knowledge:0.2.29 \
+  --package @example/knowledge:knowledge:0.2.29 \
+  --workspace open-knowledge=/srv/workspaces/open-knowledge:@example/knowledge:0.2.29 \
   --json
 ```
 
 ## Storage
 
-Machines stores runtime data locally in SQLite under the Hasna data directory and includes repo-owned PostgreSQL migrations for remote storage deployments.
+Machines stores runtime data locally in SQLite under its data directory and includes repo-owned PostgreSQL migrations for remote storage deployments.
 
 ```bash
 machines storage status --json
@@ -252,30 +253,30 @@ target can be explicit or environment-backed:
 
 ```bash
 machines backup --bucket fleet-backups --prefix machines --json
-HASNA_MACHINES_S3_BUCKET=hasna-xyz-opensource-machines-prod machines backup --json
+MACHINES_S3_BUCKET=fleet-backups machines backup --json
 ```
 
 `--bucket` and `--prefix` always win. Without `--bucket`, the backup command
 uses `HASNA_MACHINES_S3_BUCKET` or fallback `MACHINES_S3_BUCKET`; prefix uses
 `HASNA_MACHINES_S3_PREFIX`, fallback `MACHINES_S3_PREFIX`, or `machines`.
 This keeps the open-source CLI local/self-hosted by default while allowing
-Hasna deployments to route app-owned backups through canonical storage metadata.
+deployments to route app-owned backups through explicit storage metadata.
 
 ## Applications and tooling
 
 ```bash
-machines apps list --machine apple03
-machines apps status --machine apple03
-machines apps diff --machine apple03
-machines apps plan --machine apple03 --json
-machines apps apply --machine apple03 --yes
-
-machines install-claude status --machine spark01
-machines install-claude diff --machine spark01
-machines install-claude plan --machine spark01 --tool claude codex --json
-machines install-claude apply --machine spark01 --tool claude codex --yes
-
-machines install-tailscale --machine apple03 --json
+machines apps list --machine mac-lab-01
+machines apps status --machine mac-lab-01
+machines apps diff --machine mac-lab-01
+machines apps plan --machine mac-lab-01 --json
+machines apps apply --machine mac-lab-01 --yes
+
+machines install-claude status --machine linux-dev-01
+machines install-claude diff --machine linux-dev-01
+machines install-claude plan --machine linux-dev-01 --tool claude codex --json
+machines install-claude apply --machine linux-dev-01 --tool claude codex --yes
+
+machines install-tailscale --machine mac-lab-01 --json
 ```
 
 ## Notifications
@@ -295,7 +296,7 @@ machines notifications dispatch --event manual.test --message "hello fleet"
 ## Runtime Events
 
 `machines runtime tmux-watch` probes tmux with `display-message` and emits shared
-Hasna events without sending keys, killing panes, or changing tmux state.
+events without sending keys, killing panes, or changing tmux state.
 
 ```bash
 machines runtime tmux-watch %11 --once --json