@garaje/base 0.1.4 → 0.2.0

package/extensions/protected-paths.ts

@@ -35,6 +35,10 @@ const PROTECTED_PATTERNS = [
 	// recipes and running `garaje park` — never by hand-editing compose.
 	"compose.framework.yaml",
 	"compose.bays.yaml",
+	// The COMMITTED generated pi-image toolchain: same contract as
+	// compose.bays.yaml — the agent shapes it by editing a bay's recipe and
+	// running `garaje park`, never by hand-editing the artifact.
+	"pi/toolchain/",
 	"pi/Dockerfile",
 	"pi/entrypoint.sh",
 	// Framework substrate now ships as the @garaje/base package.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@garaje/base",
-  "version": "0.1.4",
+  "version": "0.2.0",
   "license": "MIT",
   "repository": {
     "type": "git",

package/rules/00-workspace.md

@@ -13,6 +13,15 @@
   endpoint) to prove the change took effect.
 - `compose.framework.yaml` and `docker-compose.yml` are the framework
   substrate and are write-protected — propose changes, don't edit them.
+- Pi extensions are **codified in the repo**, not installed ad hoc. Run
+  `pi install -l npm:<pkg>@<version>` — the `-l` writes the committed
+  `.pi/settings.json`, and teammates get the package automatically on their next
+  `garaje up`. Without `-l` the install lands in user scope on the pi-config
+  volume, where nobody else can see it. Always pin the version, then commit
+  `.pi/settings.json`. (`.pi/npm/` holds the artifacts and is gitignored.)
+- Inference credentials live in `.env`, which compose forwards into this
+  container; that is the only surface. A key stored by `/login` is written to
+  `/root/.pi/agent/auth.json` on the pi-config volume and OVERRIDES `.env`.
 - `packages/` holds the garaje **framework** being extracted from this repo:
   `packages/cli` (the TypeScript `garaje` CLI) and `packages/base` (the
   `@garaje/base` pi package), as npm workspaces. The recipe→compose codegen now

package/rules/20-self-modification.md

@@ -11,7 +11,8 @@ the change first:
   — propose the exact diff to the developer instead of editing them.
 - **Cold** — anything the container is built from or defined by: the pi
   image and entrypoint, the framework's runtime topology, a pi or
-  `@garaje/base` version pin. These only take effect through a rebirth.
+  `@garaje/base` version pin, and the generated `pi/toolchain/` (parking a bay
+  changes the pi image's runtimes). These only take effect through a rebirth.
 
 Cold protocol (you cannot rebirth the container you live in):