@crvouga/personal 0.1.2 → 0.1.4

package/releasing.md

@@ -81,7 +81,7 @@ publish-time web 2FA and trusted-publisher setup. npm update notices/progress ar
 disabled too; keep npm versions owned by the shared mise lock, not a global
 `npm install -g`. After cancellation or expiry, rerun the command and use its new
 URL, not an earlier session's URL. Treat approval links as private; never paste
-them into reports or shared logs. Registry verification retries version and latest-tag propagation with 100 seconds of bounded propagation waits without republishing. Transient read failures are retried within that same bound. The browser approval is not proof of publication;
+them into reports or shared logs. Registry verification retries version and latest-tag propagation with 310 seconds of bounded propagation waits without republishing. Transient read failures are retried within that same bound. The browser approval is not proof of publication;
 wait for registry-integrity and trusted-publisher verification to finish.
 
 ## Vault username/password login
@@ -130,7 +130,8 @@ with anonymous registry configuration and running it on real Node. The required
 4. Builds, allowlist-checks, packs and consumer-tests the exact tarball.
 5. Publishes using npm's **GitHub OIDC trusted publishing**, without npm secrets.
 6. Confirms the content hash, SHA-512 integrity and latest tag, with bounded
-   read-only retries for registry propagation. Unconfirmed outcomes fail rather
+   read-only retries for registry propagation. Registry reads bypass stale CDN
+   cache entries and verification waits for matching content and integrity. Unconfirmed outcomes fail rather
    than blindly republish.
 
 Publishing is serialized with non-cancelling concurrency. Dispatch **CI** on main
@@ -164,3 +165,12 @@ npx --yes @crvouga/personal@latest fleet doctor --all --json
 Do not claim release or green CI based on local checks. Deployment of the CI
 workflow requires these source changes to land on main, and remote fleet coverage
 requires actual locally configured SSH aliases and checkout paths.
+
+## Fleet-sync release gate
+
+The Ubuntu fleet-sync flow is not yet a complete machine-convergence release.
+Read `../fleet/docs/ubuntu-sync.md` before publication. The package build embeds
+an automatically approvable source SHA only for a clean checkout; dirty builds
+retain provenance metadata but require an explicit reviewed revision. The anonymous
+consumer smoke covers both `fleet-sync` and `fleet converge` previews without a
+checkout. Passing those checks is not Ubuntu/service/provider acceptance.

package/schema.json

@@ -5,8 +5,12 @@
   "additionalProperties": false,
   "required": ["version", "nodes"],
   "properties": {
-    "$schema": { "type": "string" },
-    "version": { "const": 1 },
+    "$schema": {
+      "type": "string"
+    },
+    "version": {
+      "const": 1
+    },
     "nodes": {
       "type": "array",
       "minItems": 1,
@@ -16,7 +20,10 @@
         "additionalProperties": false,
         "required": ["id", "ssh", "workspace"],
         "properties": {
-          "id": { "type": "string", "pattern": "^[a-z][a-z0-9-]{0,62}$" },
+          "id": {
+            "type": "string",
+            "pattern": "^[a-z][a-z0-9-]{0,62}$"
+          },
           "ssh": {
             "type": "string",
             "pattern": "^[a-zA-Z0-9][a-zA-Z0-9._-]{0,252}$"
@@ -48,6 +55,15 @@
                 "workstation"
               ]
             }
+          },
+          "tailscaleId": {
+            "type": "string",
+            "pattern": "^[a-zA-Z0-9:_-]{1,128}$",
+            "description": "Explicitly enrolled stable Tailscale device ID; replacements require reenrollment."
+          },
+          "bootstrapViaSsh": {
+            "type": "boolean",
+            "description": "Explicit permission to bootstrap an enrolled node over its trusted SSH route while Tailscale is unavailable; does not accept host keys or replace device identities."
           }
         }
       }