@oas-framework/pi 0.9.1 → 0.10.0

package/README.md

@@ -1,27 +1,29 @@
 # @oas-framework/pi
 
-Minimal pi adapter for [OAS](https://github.com/OAS-Framework/oas).
+Pi runtime bridge for [OAS](https://github.com/OAS-Framework/oas).
 
 The runtime-neutral kernel and universal `oas` CLI live in
-`@oas-framework/oas`. This adapter registers no operational tools. It only:
+`@oas-framework/oas`. This bridge registers no operational tools. It only:
 
-- exposes `oas-getting-started` before an OAS workspace exists;
-- points spawned sessions at their exact instance-local `.agents/skills` set;
+- exposes `oas-getting-started` before an OAS workspace exists (the
+  acquisition funnel);
+- contributes the instance-local `.agents/skills` set inside a spawned
+  instance;
 - journals compaction summaries and sends resume nudges when the active
-  knowledge capability created `STATE.md`/`log.md`.
+  knowledge capability created `STATE.md`/`log.md` — the OKF session
+  protocol enforced at runtime.
 
-The kernel launches pi with `--no-skills --skill <instance>/.agents/skills`,
-so user, project, settings, ancestor, and pi-package skill discovery cannot
-pollute one soul's selected runtime surface.
+Skill resolution itself is owned by the kernel: spawn materializes the exact
+kernel + soul + active-capability set into each instance's `.agents/skills`
+and launches pi with that directory as an explicit skill path. Ambient
+skills (user-level, packages, work tree) coexist with the OAS-composed set.
 
 ```bash
 npm install -g @oas-framework/oas
 pi install npm:@oas-framework/pi
 ```
 
-Install matching versions and upgrade both packages together. Exact isolation
-needs the new kernel launch flags and this adapter's instance-only discovery.
-An older adapter still contributes workspace and package skill roots. OAS
+OAS
 publishes both packages from the same version tag. Reload pi after an adapter
 install or upgrade.
 

package/extension/index.ts

@@ -1,9 +1,10 @@
 /**
- * OAS pi adapter — minimal runtime glue.
+ * OAS pi runtime bridge — minimal glue.
  *
- * Skill visibility is deliberately instance-local. Outside an instance, only
- * oas-getting-started is contributed as pre-workspace bootstrap. The kernel
- * materializes every spawned instance's exact set in .agents/skills.
+ * The kernel materializes every spawned instance's exact set in
+ * .agents/skills; this bridge contributes it inside an instance, plus the
+ * pre-workspace oas-getting-started bootstrap outside one, and drives the
+ * memory session events. Ambient skills coexist with the OAS-composed set.
  */
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
 import { appendLogEntry, PACKAGED_SKILLS_DIR } from "./core-loader.mjs";

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@oas-framework/pi",
-  "version": "0.9.1",
-  "description": "Minimal OAS pi adapter — instance-local skill discovery and memory session events over the runtime-neutral @oas-framework/oas kernel",
+  "version": "0.10.0",
+  "description": "OAS pi runtime bridge — memory session events and pre-workspace bootstrap over the runtime-neutral @oas-framework/oas kernel",
   "keywords": [
     "pi-package",
     "agents",