@really-knows-ai/foundry 3.0.2 → 3.1.0

package/dist/skills/init-memory/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: init-memory
 type: atomic
-description: Initialize flow memory by creating the foundry/memory/ and foundry-memory/ directory structures
+description: Initialise flow memory by creating the foundry/memory/ and foundry-memory/ directory structures
 ---
 
-# Initialize Flow Memory
+# Initialise Flow Memory
 
 Scaffold `foundry/memory/` (config) and `foundry-memory/relations/` (row data)
 in the current project. `foundry/memory/` holds entity-type and edge-type
@@ -27,19 +27,12 @@ Before running this skill, verify all of the following:
    `git rev-parse --abbrev-ref HEAD` and confirm it matches
    `config/<description>`.
 
-3. If the branch does not start with `config/`, instruct the user to
-   create one before continuing:
-
-   > Foundry configuration changes must be made on a config/* branch.
-   > From a clean main branch, call:
-   >
-   > `foundry_git_branch({ kind: "config", description: "<short-name>" })`
-   >
-   > Then re-run this skill.
-
-   If the user is on a `dry-run/*/*` branch, they must finish
-   that dry-run first (`foundry_git_finish({ message, confirm: true })`)
-   before re-running this skill on the parent `config/*`.
+3. If the branch does not start with `config/`, move to a suitable
+   `config/*` branch internally when the current branch is safe. If
+   the current branch is `work/*` or `dry-run/*/*`, stop and explain
+   the active work must be finished first. When unrelated uncommitted
+   changes could be affected by branching or writing files, ask before
+   proceeding.
 
 Neither `foundry/memory/` nor `foundry-memory/` may already exist.
 
@@ -82,11 +75,7 @@ Neither `foundry/memory/` nor `foundry-memory/` may already exist.
    git commit -m "feat: initialise flow memory"
    ```
 
-5. **Tell the user what is next**:
+5. **Continue the user's original request**:
 
-   > Flow memory is scaffolded. Next steps:
-   >
-   > - Use `add-memory-entity-type` to declare entity types (e.g. `class`,
-   >   `method`, `table`).
-   > - Use `add-memory-edge-type` to declare edge types (e.g. `calls`,
-   >   `writes`, `references`).
+   > Flow memory is scaffolded. The Foundry agent will continue to define
+   > memory entity and edge types as needed to support your goal.

package/dist/skills/list-agents/SKILL.md

@@ -21,4 +21,4 @@ foundry-<provider>-<model>  →  <provider>/<model>
 
 If no `foundry-*.md` files are found, output:
 
-> No foundry agent files found. Run the `refresh-agents` skill to generate them.
+> No foundry agent files found. Call `foundry_refresh_agents()` to generate them.

package/dist/skills/refresh-agents/SKILL.md

@@ -9,35 +9,13 @@ Regenerate `.opencode/agents/foundry-*.md` files from the currently available mo
 
 ## Protocol
 
-1. Run `opencode models` to get all available `provider/model` IDs
-2. Create `.opencode/agents/` directory if it does not exist
-3. Delete all existing `.opencode/agents/foundry-*.md` files (stale agents from removed providers)
-4. For each model line in the output, generate a markdown agent file
+Call the `foundry_refresh_agents` tool. It runs `opencode models`, deletes stale agent files, and generates fresh ones.
 
-### Agent file format
+## Output
 
-Filename: `.opencode/agents/foundry-<slug>.md`
+The tool returns `{ ok: true, count: <n> }` on success.
 
-Where `<slug>` is the model ID with **both** `/` and `.` replaced by `-`. This keeps filenames shell-safe and unambiguous.
-
-Examples:
-- `opencode/claude-sonnet-4` → `.opencode/agents/foundry-opencode-claude-sonnet-4.md`
-- `github-copilot/claude-sonnet-4.6` → `.opencode/agents/foundry-github-copilot-claude-sonnet-4-6.md`
-- `github-copilot/gpt-5.4` → `.opencode/agents/foundry-github-copilot-gpt-5-4.md`
-
-Content:
-
-```markdown
----
-description: "Foundry stage agent using <provider>/<model-key>"
-mode: subagent
-model: "<provider>/<model-key>"
-hidden: true
----
-You are a Foundry stage agent. Follow the skill instructions provided in your task prompt exactly.
-```
-
-5. After writing all files, output:
+After the tool completes, tell the user:
 
 > Generated `<count>` foundry agent files in `.opencode/agents/`.
 > **Restart OpenCode** for the new agents to take effect.

package/dist/skills/rename-memory-edge-type/SKILL.md

@@ -25,15 +25,13 @@ Before running this skill, verify all of the following:
    create one before continuing:
 
    > Foundry configuration changes must be made on a config/* branch.
-   > From a clean main branch, call:
+   > If configuration changes are needed, move to a suitable `config/*`
+   > branch internally when the current branch is safe. If the current
+   > branch is `work/*` or `dry-run/*/*`, stop and explain the active
+   > work must be finished first.
    >
-   > `foundry_git_branch({ kind: "config", description: "<short-name>" })`
-   >
-   > Then re-run this skill.
-
-   If the user is on a `dry-run/*/*` branch, they must finish
-   that dry-run first (`foundry_git_finish({ message, confirm: true })`)
-   before re-running this skill on the parent `config/*`.
+   > After the prerequisite is handled, continue the user's original
+   > request from the current context.
 
 4. Memory is initialised. The `from` edge type must exist; the `to`
    name must be free.

package/dist/skills/rename-memory-entity-type/SKILL.md

@@ -25,15 +25,13 @@ Before running this skill, verify all of the following:
    create one before continuing:
 
    > Foundry configuration changes must be made on a config/* branch.
-   > From a clean main branch, call:
+   > If configuration changes are needed, move to a suitable `config/*`
+   > branch internally when the current branch is safe. If the current
+   > branch is `work/*` or `dry-run/*/*`, stop and explain the active
+   > work must be finished first.
    >
-   > `foundry_git_branch({ kind: "config", description: "<short-name>" })`
-   >
-   > Then re-run this skill.
-
-   If the user is on a `dry-run/*/*` branch, they must finish
-   that dry-run first (`foundry_git_finish({ message, confirm: true })`)
-   before re-running this skill on the parent `config/*`.
+   > After the prerequisite is handled, continue the user's original
+   > request from the current context.
 
 4. Memory is initialised. The `from` entity type must exist; the `to`
    name must be free (no existing entity or edge).

package/dist/skills/reset-memory/SKILL.md

@@ -24,22 +24,16 @@ Before running this skill, verify all of the following:
    `git rev-parse --abbrev-ref HEAD` and confirm it matches
    `config/<description>`.
 
-3. If the branch does not start with `config/`, instruct the user to
-   create one before continuing:
-
-   > Foundry configuration changes must be made on a config/* branch.
-   > From a clean main branch, call:
-   >
-   > `foundry_git_branch({ kind: "config", description: "<short-name>" })`
-   >
-   > Then re-run this skill.
-
-   If the user is on a `dry-run/*/*` branch, they must finish
-   that dry-run first (`foundry_git_finish({ message, confirm: true })`)
-   before re-running this skill on the parent `config/*`.
-
-4. Memory is initialised (`foundry/memory/` exists; run `init-memory`
-   if not).
+3. If the branch does not start with `config/`, move to a suitable
+   `config/*` branch internally when the current branch is safe. If
+   the current branch is `work/*` or `dry-run/*/*`, stop and explain
+   the active work must be finished first. When unrelated uncommitted
+   changes could be affected by branching or writing files, ask before
+   proceeding.
+
+4. Memory is initialised (`foundry/memory/` exists; initialise it
+   internally if not). After the reset completes, continue the user's
+   original request from context.
 
 ## Steps
 

package/dist/skills/upgrade-foundry/SKILL.md

@@ -20,7 +20,7 @@ Verify a safe base state before making changes:
 
 - The worktree is clean, or the user explicitly chooses how to handle dirty files.
 - `WORK.md` is absent from the repository root.
-- The upgrade runs from a config branch such as `config/upgrade-foundry`, or you create one with `foundry_git_branch({ kind: 'config', description: 'upgrade-foundry' })` before making config changes.
+- The upgrade runs from a config branch such as `config/upgrade-foundry`. If configuration changes are needed, move to a suitable `config/*` branch internally when the current branch is safe. If the current branch is `work/*` or `dry-run/*/*`, stop and explain the active work must be finished first.
 - Use an isolated worktree where practical, matching the normal config-edit workflow.
 
 If `WORK.md` exists, stop and tell the user:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@really-knows-ai/foundry",
-  "version": "3.0.2",
+  "version": "3.1.0",
   "description": "A skill-driven framework for governed artefact generation with AI coding tools. Define your own artefact types, laws, and flows — Foundry handles the forge → quench → appraise pipeline with deterministic routing, quality gates, and iterative refinement.",
   "type": "module",
   "main": "dist/.opencode/plugins/foundry.js",
@@ -34,6 +34,7 @@
   },
   "files": [
     "dist/.opencode/",
+    "dist/agents/",
     "dist/skills/",
     "dist/scripts/",
     "dist/docs/",