@really-knows-ai/foundry 3.0.1 → 3.1.0

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.1",
+  "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/",