@marcoscale98/pi-extensible-workflows 5.19.1-fork.1 → 6.2.1-fork.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@marcoscale98/pi-extensible-workflows",
-  "version": "5.19.1-fork.1",
-  "description": "Deterministic multi-agent workflow orchestration for Pi",
+  "version": "6.2.1-fork.1",
+  "description": "Deterministic multi-agent workflow orchestration and codemode scripts for Pi",
   "homepage": "https://vekexasia.github.io/pi-extensible-workflows/",
   "repository": {
     "type": "git",
@@ -15,7 +15,8 @@
     "workflow",
     "multi-agent",
     "orchestration",
-    "automation"
+    "automation",
+    "codemode"
   ],
   "exports": {
     ".": "./dist/src/index.js",
@@ -24,7 +25,6 @@
     "./utils": "./dist/src/utils.js",
     "./budget": "./dist/src/budget.js",
     "./validation": "./dist/src/validation.js",
-    "./roles": "./dist/src/roles.js",
     "./registry": "./dist/src/registry.js",
     "./runtime": "./dist/src/runtime/index.js",
     "./trajectory": "./dist/trajectory/index.js"
@@ -48,7 +48,7 @@
     "CHANGELOG.md"
   ],
   "scripts": {
-    "build": "rm -rf dist && tsc -p tsconfig.json && cp -R starter/roles dist/starter/roles && cp -R trajectory/src/assets dist/trajectory/src/assets && cp -R trajectory/src/assets dist/trajectory/assets && esbuild src/index.ts starter/index.ts subagents/index.ts trajectory/index.ts --bundle --format=esm --platform=node --packages=external --sourcemap --sources-content=false --outbase=. --outdir=dist && esbuild trajectory/src/server.ts --bundle --format=esm --platform=node --sourcemap --sources-content=false --outfile=dist/trajectory/src/server.js",
+    "build": "rm -rf dist && tsc -p tsconfig.json && cp -R trajectory/src/assets dist/trajectory/src/assets && cp -R trajectory/src/assets dist/trajectory/assets && esbuild src/index.ts starter/index.ts subagents/index.ts trajectory/index.ts --bundle --format=esm --platform=node --packages=external --sourcemap --sources-content=false --outbase=. --outdir=dist && esbuild trajectory/src/server.ts --bundle --format=esm --platform=node --sourcemap --sources-content=false --outfile=dist/trajectory/src/server.js",
     "lint": "eslint .",
     "test": "npm run test:layout && npm run build && npm run test:widget && npm run test:run && npm run test:herdr && npm run test:subagents",
     "test:layout": "node --test --test-timeout=10000 --test-force-exit test/workspace-layout.test.mjs",

package/skills/pi-extensible-workflows/SKILL.md

@@ -74,11 +74,11 @@ For a failed run, call `workflow_status({ runId })` first: a compact authoritati
 export interface AgentOptions {
   label?: string; // display name
   model?: string; // provider/model:thinking, or alias[:thinking]
-  role?: string; // role file name
   contextFiles?: Array<"global" | "project" | "cwd">; // which Pi context files to load
-  skills?: string[]; // minimatch overlay after the role list
-  extensions?: string[]; // minimatch overlay after the role list
-  tools?: string[]; // minimatch overlay after the role list
+  skills?: string[]; // minimatch selector, ordered defaults then call options
+  extensions?: string[]; // minimatch selector, ordered defaults then call options
+  tools?: string[]; // minimatch selector, ordered defaults then call options
+  excludeTools?: string[]; // exact tool names removed after preparation; no patterns or workflow_result; never widens the parent ceiling
   outputSchema?: JsonSchema; // structured result for a later phase
   retries?: number; // extra same-run retries for this agent
   timeoutMs?: number | null; // attempt timeout; null = none
@@ -86,9 +86,9 @@ export interface AgentOptions {
 }
 ```
 
-A `role` already sets model, tools, skills, extensions, and context files; call-level options silently override them. Pass `{ role }` alone unless an override is indispensable for that call. When overriding, selectors overlay the role list: restrict with `["!*", "read", "grep"]`; `["*"]` turns everything back on.
+Restrict resource selectors with `["!*", "read", "grep"]`; `["*"]` selects every resource allowed by the parent ceiling.
 
-Extensions may add JSON-compatible agent options such as `advisor: true`; core keys retain validation and role constraints. Extension options go to setup hooks/native setup and are not inherited by child agents.
+Extensions may add JSON-compatible agent options such as `advisor: true`; core keys retain validation and parent ceilings. Extension options go to setup hooks/native setup and are not inherited by child agents.
 
 Agent calls are unnamed. Direct calls receive hidden source call-site identity; aliases are unsupported, and calls from one source site must not race outside `parallel` or `pipeline`, whose structural keys make replay deterministic.
 
@@ -97,7 +97,7 @@ Agent calls are unnamed. Direct calls receive hidden source call-site identity;
 Use `agent.create(...)` when one agent must keep its transcript across several turns; use plain `agent(...)` calls for independent work.
 
 ```js
-const author = agent.create({ name: "author", role: "developer" });
+const author = agent.create({ name: "author" });
 const draft = await author.send("Create the first draft");
 const revised = await author.send(
   prompt("Apply these findings:\n\n{findings}", { findings }),
@@ -145,12 +145,14 @@ const results = await parallel("implementation", {
 });
 ```
 
+Registered extension functions also get `context.agent.create({ name, ... })` with the same handle rules as scripts. Handle journal identity is scoped by function invocation, branch, worktree, and name, so repeated or nested invocations and script handles never share a transcript; the prefix `function-handle/` is reserved in script names. Each turn is a separate agent node, with no automatic grouping.
+
 Registered extension functions receive `withWorktree` in context and can compose other registered functions with `context.invoke("reviewRepository", { focus: "security" }, "security-review")`. The optional label is presentation-only; journal identity remains the function name and occurrence. Their public inputs and outputs remain JSON; callbacks cannot cross the extension boundary.
 
 ## Rules
 
 - Workflow run does not inherit any of the main agent context. Keep that in mind when creating agent's prompts.
-- `model` must be a configured alias or the canonical `provider/model:thinking` form. Aliases are listed by `workflow_catalog`; prefer a suitable alias over a hardcoded model. Never guess a model identifier: verify unknown names with `pi --list-models "search term"` first, then use the fully qualified identifier it returns.
+- If `model` is specified, it must be a configured alias or the canonical `provider/model:thinking` form. Aliases are listed by `workflow_catalog`; prefer a suitable alias over a hardcoded model. Never guess a model identifier: verify unknown names with `pi --list-models "search term"` first, then use the fully qualified identifier it returns.
 - Use `log(messageString)` for brief operator status and `phase(phaseName)` to signal the start of another phase.
 - Use `parallel()` for independent tasks with different flows and `pipeline()` when every keyed item follows the same ordered stages; do not duplicate identical chains in `parallel()`. Signatures are `parallel(operationName, tasksRecord)` and `pipeline(operationName, itemsRecord, stagesRecord)`; keys are stable task, item, and stage names.
 - Use a JavaScript loop for repeated work; each direct `agent(...)` call gets deterministic call-site and occurrence identity.