@inixiative/config 0.5.36 → 0.5.38

package/README.md

@@ -76,7 +76,7 @@ bunx @inixiative/config train [root] [--lane=primitives|agentic] [--push]
 
 `train` is the release cascade, run from this repo's checkout. It walks every lane in order (primitives, then agentic), or only the lane `--lane` names. Origin is the truth: it refuses to run from a config checkout behind origin, and it fast-forwards clean checkouts to origin before working (dirty or diverged repos still skip). It only ships the default branch: a checkout on a feature branch is skipped whole — never re-locked, committed to, or published from.
 
-Lanes stand alone. A lane with a package missing a checkout, or claimed by ambiguous checkouts, does not run; a lane whose check, commit or publish fails stops there and leaves its BOM entries as they were. Neither holds back the other lane. Within a lane it walks checkouts in dependency order; per checkout it: bumps ecosystem ranges to the blessed sets → re-locks → runs the repo's `check` → commits only its own changes (`package.json` files + `bun.lock`) → publishes each lane package whose local version is ahead of npm, in dependency order, and waits until the registry serves it → records it in its lane's section of the BOM. A root package publishes with `npm publish`; a workspace member is packed with `bun pm pack`, which rewrites `workspace:` ranges to the versions being released, and the tarball is published with `npm publish`, so OTP prompts pass through either way. A package already on npm at its local version but not yet blessed — published by hand, or by a train whose lane later failed — is blessed on the next run.
+Lanes stand alone. A lane with a package missing a checkout, or claimed by ambiguous checkouts, does not run; a lane whose check, commit or publish fails stops there and leaves its BOM entries as they were. Neither holds back the other lane. Within a lane it walks checkouts in dependency order; per checkout it: bumps ecosystem ranges to the blessed sets → re-locks → runs the repo's `check` → commits only its own changes (`package.json` files + `bun.lock`) → publishes each lane package whose local version is ahead of npm, in dependency order, and waits until the registry serves it (up to 15 minutes, since npm holds new versions for processing) → records it in its lane's section of the BOM. A root package publishes with `npm publish`; a workspace member is packed with `bun pm pack`, which rewrites `workspace:` ranges to the versions being released, and the tarball is published with `npm publish`, so OTP prompts pass through either way. A package already on npm at its local version but not yet blessed — published by hand, or by a train whose lane later failed — is blessed on the next run.
 
 Consumers run once, after every selected lane, upstreams first, against the full blessed set: a consumer of both lanes ends coherent with both whichever lane ran. They get the same bump → re-lock → `check`, never a publish, and their changes go through review: the train commits them on a `train/ecosystem-sync-<date>` branch and leaves the checkout there until it is merged.
 

package/dist/cli.js

@@ -1147,12 +1147,15 @@ function freeBranch(cwd, name) {
   return candidate;
 }
 function servedByRegistry(name, version) {
-  for (let attempt = 0; attempt < 10; attempt++) {
-    const view = spawnSync2("npm", ["view", `${name}@${version}`, "version"], { encoding: "utf8" });
+  const deadline = Date.now() + 15 * 6e4;
+  while (true) {
+    const view = spawnSync2("npm", ["view", `${name}@${version}`, "version", "--prefer-online"], {
+      encoding: "utf8"
+    });
     if (view.status === 0 && view.stdout.trim() === version) return true;
-    Bun.sleepSync(3e3);
+    if (Date.now() >= deadline) return false;
+    Bun.sleepSync(1e4);
   }
-  return false;
 }
 function bumpPatch(version) {
   const [major, minor, patch] = version.split(".").map(Number);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inixiative/config",
-  "version": "0.5.36",
+  "version": "0.5.38",
   "description": "Shared toolchain for the inixiative ecosystem: tsconfig/biome/tsup presets, a version manifest (BOM), and a sync/check CLI",
   "type": "module",
   "license": "MIT",

package/versions.json

@@ -13,7 +13,7 @@
     "@types/bun"
   ],
   "ecosystem": {
-    "@inixiative/config": "0.5.36",
+    "@inixiative/config": "0.5.38",
     "@inixiative/json-rules": "2.25.0",
     "@inixiative/permissions": "0.3.2",
     "@inixiative/transitions": "0.1.0",
@@ -21,12 +21,12 @@
     "@inixiative/prisma-map": "0.2.0",
     "@inixiative/atlas": "0.1.1",
     "@inixiative/gloss": "0.0.4",
-    "@inixiative/archive": "0.2.1"
+    "@inixiative/archive": "0.4.0"
   },
   "agentic": {
     "@inixiative/agent-session": "0.2.0",
-    "@inixiative/foundry-core": "0.1.0",
-    "@inixiative/foundry": "0.1.0"
+    "@inixiative/foundry-core": "0.2.0",
+    "@inixiative/foundry": "0.2.0"
   },
   "consumers": {
     "inixiative/template": {