@xynogen/pix-core 0.3.1 → 0.4.0

package/README.md

@@ -2,7 +2,11 @@
 
 Pi coding agent extension — core UI/UX meta-package.
 
-Installing `pix-core` pulls in all of the packages below as npm dependencies — no source code of its own.
+Installing `pix-core` pulls in all of the packages below as npm dependencies **and activates them**. A single `pi install npm:@xynogen/pix-core` boots every core extension — you do not need to install the members individually.
+
+## How it works
+
+Pi activates extensions per installed package via each package's `pi.extensions` manifest; it does not walk npm dependencies. So `pix-core` ships a thin aggregator (`src/extension.ts`) that imports each member's extension factory and invokes it against the same host. Each member also carries a `globalThis` idempotency guard, so installing `pix-core` **and** a member standalone activates that member only once.
 
 ## What's included
 
@@ -15,7 +19,7 @@ Installing `pix-core` pulls in all of the packages below as npm dependencies —
 | `pix-commands` | `/diff` and `/clear` slash commands |
 | `pix-diagnostics` | Compact LSP diagnostic widget |
 | `pix-prompts` | System-prompt injection (AGENTS.md + repo directive files) |
-| `pix-skills` | Agent skill loader (`read_skills` tool + 21 bundled skills) |
+| `pix-skills` | Agent skill loader (`read_skills` tool + 23 bundled skills) |
 | `pix-nudge` | Tool + capability nudge hooks |
 
 ## Install
@@ -24,7 +28,7 @@ Installing `pix-core` pulls in all of the packages below as npm dependencies —
 pi install npm:@xynogen/pix-core
 ```
 
-> Includes the core pix UI/UX packages and installs their dependencies.
+> Installs and activates the core pix UI/UX extensions in one command. Members are deduped if also installed directly.
 
 ## Full distro
 

package/package.json

@@ -1,12 +1,19 @@
 {
 	"name": "@xynogen/pix-core",
-	"version": "0.3.1",
-	"description": "Pi extension bundle — installs all core pix-* packages",
+	"version": "0.4.0",
+	"description": "Pi extension bundle — installs and activates all core pix-* extensions",
 	"type": "module",
+	"main": "src/extension.ts",
+	"pi": {
+		"extensions": [
+			"src/extension.ts"
+		]
+	},
 	"scripts": {
 		"test": "bun test"
 	},
 	"files": [
+		"src",
 		"README.md",
 		"LICENSE"
 	],
@@ -42,6 +49,7 @@
 		"@xynogen/pix-nudge": "*"
 	},
 	"peerDependencies": {
-		"@earendil-works/pi-coding-agent": "*"
+		"@earendil-works/pi-coding-agent": "*",
+		"@earendil-works/pi-tui": "*"
 	}
 }

package/src/extension.ts

@@ -0,0 +1,43 @@
+/**
+ * pix-core — aggregator extension.
+ *
+ * Pi activates extensions per installed package via its `pi.extensions`
+ * manifest; it does NOT walk npm dependencies. So a meta-package can only
+ * activate its members by importing each one's extension factory and invoking
+ * it against the same `pi` host.
+ *
+ * Every member ships a default-exported `(pi) => void` factory. We resolve them
+ * by subpath import (members have no `exports` map, so the full package dir is
+ * importable). One `pi install npm:@xynogen/pix-core` then boots all of them.
+ */
+
+import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
+import registerCommands from "@xynogen/pix-commands/src/extension.ts";
+import registerDiagnostics from "@xynogen/pix-diagnostics/src/extension.ts";
+import registerFooter from "@xynogen/pix-footer/src/extension.ts";
+import registerModels from "@xynogen/pix-models/src/extension.ts";
+import registerNudge from "@xynogen/pix-nudge/src/extension.ts";
+import registerPrompts from "@xynogen/pix-prompts/src/extension.ts";
+import registerSkills from "@xynogen/pix-skills/src/index.ts";
+import registerUpdate from "@xynogen/pix-update/src/extension.ts";
+import registerWelcome from "@xynogen/pix-welcome/src/extension.ts";
+
+type Factory = (pi: ExtensionAPI) => void;
+
+const MEMBERS: Factory[] = [
+	registerWelcome,
+	registerFooter,
+	registerModels,
+	registerUpdate,
+	registerCommands,
+	registerNudge,
+	registerDiagnostics,
+	registerPrompts,
+	registerSkills,
+];
+
+export default function (pi: ExtensionAPI): void {
+	for (const register of MEMBERS) {
+		register(pi);
+	}
+}

package/src/once.test.ts

@@ -0,0 +1,62 @@
+import { afterEach, describe, expect, it } from "bun:test";
+
+// Mirror of the per-member guard. pix-core does not own once.ts (each member
+// duplicates it to stay cross-dep-free), so we re-declare the contract here and
+// assert the dedupe semantics that the aggregator relies on.
+function once(key: string, fn: () => void): void {
+	const g = globalThis as { __pixLoaded?: Set<string> };
+	const loaded = (g.__pixLoaded ??= new Set<string>());
+	if (loaded.has(key)) return;
+	loaded.add(key);
+	fn();
+}
+
+afterEach(() => {
+	delete (globalThis as { __pixLoaded?: Set<string> }).__pixLoaded;
+});
+
+describe("once", () => {
+	it("runs the factory on first invocation", () => {
+		let calls = 0;
+		once("pix-footer", () => {
+			calls++;
+		});
+		expect(calls).toBe(1);
+	});
+
+	it("skips repeated invocations of the same key", () => {
+		let calls = 0;
+		const reg = () => {
+			calls++;
+		};
+		once("pix-footer", reg);
+		once("pix-footer", reg);
+		once("pix-footer", reg);
+		expect(calls).toBe(1);
+	});
+
+	it("isolates distinct keys", () => {
+		const seen: string[] = [];
+		once("pix-footer", () => seen.push("footer"));
+		once("pix-welcome", () => seen.push("welcome"));
+		expect(seen).toEqual(["footer", "welcome"]);
+	});
+
+	it("shares the registry across calls via globalThis", () => {
+		let calls = 0;
+		once("pix-skills", () => {
+			calls++;
+		});
+		// A second loader pass (e.g. standalone install after pix-core) reuses
+		// the same globalThis registry and must not re-run.
+		once("pix-skills", () => {
+			calls++;
+		});
+		expect(calls).toBe(1);
+		expect(
+			(globalThis as { __pixLoaded?: Set<string> }).__pixLoaded?.has(
+				"pix-skills",
+			),
+		).toBe(true);
+	});
+});