@warlock.js/core 4.4.0 → 4.5.0

package/llms-full.txt

@@ -79,8 +79,13 @@ Lower number = earlier. The built-in ordering, from `ConnectorPriority` in `@war
 | `http`        | 5        | **Late**|
 | `storage`     | 6        | Early   |
 | `socket`      | 7        | **Late**|
+| `notifications`| 8       | Early   |
+| `access`      | 9        | Early   |
+| `ai`          | 10       | Early   |
 
-Pick a number that places your connector where it belongs. If your queue needs the database, set `priority > 2` (e.g. `10`). If you replace the cache, set `< 4` to win.
+Pick a number that places your connector where it belongs. If your queue needs the database, set `priority > 2` (e.g. `11`). If you replace the cache, set `< 4` to win.
+
+> **Built-in `AiConnector` (priority `ConnectorPriority.AI = 10`, Early).** A reference example of a config-driven, lazy-import connector: it reads the ejected `src/config/ai.ts` and applies it via `ai.config(...)`, lazy-importing `@warlock.js/ai` only when the config is present (so core carries no hard dependency). The config file (ejected by `warlock add ai`) holds an auto-managed `// >>> warlock:ai-packages` import block where the `ai-tools` / `ai-panoptic` / `ai-workspace` satellite features link their side-effect imports. See `src/connectors/ai-connector.ts`.
 
 Negative priorities are fine for "start before everything" — the project's `src/connectors/custom-connector.ts` example uses `priority: -10`.
 
@@ -1085,6 +1090,29 @@ That's the contract. Filename → config key. No registration, no manifest, no s
 
 Some subsystems need to do extra work when their config loads (e.g. set the active locale, register a driver). Those have a special handler attached internally — for the most part you don't see them. The takeaway: changing a config file at dev time fires the handler again automatically.
 
+## The `config/ai.ts` eject + auto-import block
+
+`warlock add ai` ejects `src/config/ai.ts` — a declarative `Partial<AIConfig>` default export applied on boot by the `ai` connector (`ai.config(...)`), the same special-handler pattern as above. Two things make it unusual:
+
+1. **An auto-managed import block at the top.** The ejected file opens with a marker pair:
+
+   ```ts title="src/config/ai.ts"
+   import type { AIConfig } from "@warlock.js/ai";
+
+   // >>> warlock:ai-packages (auto-managed) >>>
+   // <<< warlock:ai-packages <<<
+
+   const ai: Partial<AIConfig> = {
+     // defaultStore, panoptic, …
+   };
+
+   export default ai;
+   ```
+
+2. **Satellite features link side-effect imports into that block.** `warlock add ai-tools | ai-panoptic | ai-workspace` inserts e.g. `import "@warlock.js/ai-workspace";` right after the marker (idempotent — re-running is a no-op). Those side-effect imports register the satellites' surface on the `ai` object (`ai.tools` / `ai.mcp`, `ai.workspace`, panoptic's wiring) **before** the connector applies the config, so a single `ai.config(...)` call sees the full augmented surface. Keep the marker block and don't hand-reorder it.
+
+The five provider features (`ai-openai`, `ai-google`, `ai-anthropic`, `ai-bedrock`, `ai-ollama`) only add their package — they don't touch `config/ai.ts`; you wire a provider's model in your agent code.
+
 ## Multi-file or conditional config
 
 A config file is just a TS module. Branch on `env(...)` if production should differ from development:

package/package.json

@@ -36,13 +36,13 @@
     "@mongez/slug": "^1.0.7",
     "@mongez/supportive-is": "^2.1.3",
     "@mongez/time-wizard": "^1.0.6",
-    "@warlock.js/auth": "4.4.0",
-    "@warlock.js/cache": "4.4.0",
-    "@warlock.js/cascade": "4.4.0",
-    "@warlock.js/context": "4.4.0",
-    "@warlock.js/logger": "4.4.0",
-    "@warlock.js/seal": "4.4.0",
-    "@warlock.js/fs": "4.4.0",
+    "@warlock.js/auth": "4.5.0",
+    "@warlock.js/cache": "4.5.0",
+    "@warlock.js/cascade": "4.5.0",
+    "@warlock.js/context": "4.5.0",
+    "@warlock.js/logger": "4.5.0",
+    "@warlock.js/seal": "4.5.0",
+    "@warlock.js/fs": "4.5.0",
     "chokidar": "^5.0.0",
     "dayjs": "^1.11.19",
     "es-module-lexer": "^2.0.0",
@@ -68,12 +68,12 @@
     "react": "^19.2.3",
     "react-dom": "^19.2.3",
     "@react-email/render": "^2.0.5",
-    "@warlock.js/herald": "4.4.0"
+    "@warlock.js/herald": "4.5.0"
   },
   "bin": {
     "warlock": "bin/warlock.js"
   },
-  "version": "4.4.0",
+  "version": "4.5.0",
   "type": "module",
   "main": "./esm/index.mjs",
   "module": "./esm/index.mjs",

package/skills/add-connector/SKILL.md

@@ -71,8 +71,13 @@ Lower number = earlier. The built-in ordering, from `ConnectorPriority` in `@war
 | `http`        | 5        | **Late**|
 | `storage`     | 6        | Early   |
 | `socket`      | 7        | **Late**|
+| `notifications`| 8       | Early   |
+| `access`      | 9        | Early   |
+| `ai`          | 10       | Early   |
 
-Pick a number that places your connector where it belongs. If your queue needs the database, set `priority > 2` (e.g. `10`). If you replace the cache, set `< 4` to win.
+Pick a number that places your connector where it belongs. If your queue needs the database, set `priority > 2` (e.g. `11`). If you replace the cache, set `< 4` to win.
+
+> **Built-in `AiConnector` (priority `ConnectorPriority.AI = 10`, Early).** A reference example of a config-driven, lazy-import connector: it reads the ejected `src/config/ai.ts` and applies it via `ai.config(...)`, lazy-importing `@warlock.js/ai` only when the config is present (so core carries no hard dependency). The config file (ejected by `warlock add ai`) holds an auto-managed `// >>> warlock:ai-packages` import block where the `ai-tools` / `ai-panoptic` / `ai-workspace` satellite features link their side-effect imports. See `src/connectors/ai-connector.ts`.
 
 Negative priorities are fine for "start before everything" — the project's `src/connectors/custom-connector.ts` example uses `priority: -10`.
 

package/skills/configure-app/SKILL.md

@@ -133,6 +133,29 @@ That's the contract. Filename → config key. No registration, no manifest, no s
 
 Some subsystems need to do extra work when their config loads (e.g. set the active locale, register a driver). Those have a special handler attached internally — for the most part you don't see them. The takeaway: changing a config file at dev time fires the handler again automatically.
 
+## The `config/ai.ts` eject + auto-import block
+
+`warlock add ai` ejects `src/config/ai.ts` — a declarative `Partial<AIConfig>` default export applied on boot by the `ai` connector (`ai.config(...)`), the same special-handler pattern as above. Two things make it unusual:
+
+1. **An auto-managed import block at the top.** The ejected file opens with a marker pair:
+
+   ```ts title="src/config/ai.ts"
+   import type { AIConfig } from "@warlock.js/ai";
+
+   // >>> warlock:ai-packages (auto-managed) >>>
+   // <<< warlock:ai-packages <<<
+
+   const ai: Partial<AIConfig> = {
+     // defaultStore, panoptic, …
+   };
+
+   export default ai;
+   ```
+
+2. **Satellite features link side-effect imports into that block.** `warlock add ai-tools | ai-panoptic | ai-workspace` inserts e.g. `import "@warlock.js/ai-workspace";` right after the marker (idempotent — re-running is a no-op). Those side-effect imports register the satellites' surface on the `ai` object (`ai.tools` / `ai.mcp`, `ai.workspace`, panoptic's wiring) **before** the connector applies the config, so a single `ai.config(...)` call sees the full augmented surface. Keep the marker block and don't hand-reorder it.
+
+The five provider features (`ai-openai`, `ai-google`, `ai-anthropic`, `ai-bedrock`, `ai-ollama`) only add their package — they don't touch `config/ai.ts`; you wire a provider's model in your agent code.
+
 ## Multi-file or conditional config
 
 A config file is just a TS module. Branch on `env(...)` if production should differ from development: