agent-bios 0.8.0 → 0.9.0

package/claude/guides/tooling-gotchas.md

@@ -125,6 +125,13 @@ depends on it, pin it explicitly instead of trusting the environment.
   leaving stale, unreferenced definitions live. After updating, re-read the
   resource, check definitions and active references separately, and remove
   the orphans explicitly.
+- **A new revision is not live traffic**: on a runtime that pins traffic to a
+  named revision (e.g. Cloud Run with a fixed split), `gcloud run deploy` (or
+  the equivalent) creates the new revision but shifts no traffic to it — the
+  previous revision keeps serving until an explicit `gcloud run services
+  update-traffic`. Read the "deploy succeeded" message as "a revision exists",
+  not "the new code is serving"; verify the live traffic split before
+  concluding the deploy took effect.
 - **Perimeter controls need the enforcement point's own logs**: an agent-side
   fetch is not an independent external observer — its egress IP and caching
   path are opaque, and it may share the protected network or serve a stale

package/codex/guides/tooling-gotchas.md

@@ -125,6 +125,13 @@ depends on it, pin it explicitly instead of trusting the environment.
   leaving stale, unreferenced definitions live. After updating, re-read the
   resource, check definitions and active references separately, and remove
   the orphans explicitly.
+- **A new revision is not live traffic**: on a runtime that pins traffic to a
+  named revision (e.g. Cloud Run with a fixed split), `gcloud run deploy` (or
+  the equivalent) creates the new revision but shifts no traffic to it — the
+  previous revision keeps serving until an explicit `gcloud run services
+  update-traffic`. Read the "deploy succeeded" message as "a revision exists",
+  not "the new code is serving"; verify the live traffic split before
+  concluding the deploy took effect.
 - **Perimeter controls need the enforcement point's own logs**: an agent-side
   fetch is not an independent external observer — its egress IP and caching
   path are opaque, and it may share the protected network or serve a stale

package/config/promotions.json

@@ -1,4 +1,12 @@
 {
   "version": 1,
-  "promotions": []
+  "promotions": [
+    {
+      "learning_id": "a6feee41-2aeb-4fb6-acc6-4584c5c1336c",
+      "tier": "domain",
+      "domains": [
+        "builder-base"
+      ]
+    }
+  ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-bios",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "description": "A thin, low-level instruction layer for LLM CLI agents: one set of principles and behavior whichever model you run. Deploys into $HOME by copy via an explicit `agent-bios install`.",
   "bin": {
     "agent-bios": "scripts/install.sh"