@really-knows-ai/foundry 3.2.4 → 3.2.6

package/README.md

@@ -103,9 +103,18 @@ Add the plugin to `opencode.json`:
 }
 ```
 
-Restart OpenCode so the plugin registers its tools and skills. You will see new
-tools and skills become available in OpenCode's command palette once the restart
-completes. Flow-management tools are now ready to use.
+Restart OpenCode so the plugin registers. On startup, Foundry bootstraps the
+directory structure, generates stage agents, and installs the Foundry guide
+agent automatically.
+
+After restart, type **hello foundry**. The assistant will tell you whether a
+further restart is needed and when to switch to the Foundry agent.
+
+Optionally, to make the package available to your project's local `node_modules`:
+
+```sh
+pnpm add -D @really-knows-ai/foundry
+```
 
 ---
 
@@ -121,29 +130,17 @@ The upgrade process asks clarifying questions for ambiguous routing, input contr
 
 ### Phase 1 — Install
 
-Add the plugin to `opencode.json` (see Install section above):
-
-```json
-{
-  "$schema": "https://opencode.ai/config.json",
-  "plugin": ["@really-knows-ai/foundry"]
-}
-```
-
-Then restart OpenCode so the plugin registers its tools and skills. You will see new
-tools and skills become available in OpenCode's command palette once the restart
-completes. Flow-management tools are now ready to use.
+Add the plugin to `opencode.json` (see Install section above), then restart
+OpenCode.
 
-### Phase 2 — Initialise
+Type **hello foundry**. The assistant will guide you through any remaining
+setup. If Foundry was just initialised, it will ask you to restart and switch
+to the **Foundry** agent. If Foundry is already set up, it will tell you to
+switch to the Foundry agent directly.
 
-Restart OpenCode after adding the plugin. On boot, the plugin's config hook runs
-a decision tree: if `foundry/` is missing or its VERSION does not match the
-installed plugin version, it bootstraps the directory structure, generates
-`foundry-<model>` stage agent files, installs the user-facing `Foundry` guide
-agent, and tells you to restart again.
+### Phase 2 — Switch to the Foundry agent
 
-Restart OpenCode a second time so the new agents register. After the restart,
-switch to the **Foundry** agent. The Foundry agent is the normal interface for
+Switch to the **Foundry** agent. The Foundry agent is the normal interface for
 authoring and running Foundry workflows.
 
 ### Phase 3 — Ask the Foundry agent for a flow

package/dist/.opencode/plugins/foundry-tools/helpers.js

@@ -92,9 +92,11 @@ export function listFlows(foundryDir) {
 
 function buildFoundryNotInitializedMessage() {
   return `<FOUNDRY_CONTEXT>
-Foundry is installed but not initialised in this project. There is no foundry/ directory.
-
-To set up Foundry, initialise the project first. Initialisation creates the foundry/ directory structure, installs the user-facing Foundry agent, and generates model-routing stage agents. After initialisation, restart OpenCode and switch to the Foundry agent.
+Foundry is installed but not yet initialised in this project — there is no foundry/ directory.
+The plugin will bootstrap the directory structure, generate stage agents, and install the
+Foundry guide agent automatically on the next startup. The user may just need to restart
+OpenCode for this to happen. Once initialised, direct the user to restart again so the new
+agents register, then switch to the Foundry agent.
 </FOUNDRY_CONTEXT>`;
 }
 
@@ -110,8 +112,9 @@ function buildFlowList(flows) {
 
 function buildFoundryInitializedMessage(flowList, packageRoot) {
   return `<FOUNDRY_CONTEXT>
-Foundry is active in this project. The foundry/ directory contains the project's artefact definitions,
-laws, appraisers, cycles, and flows.
+Foundry is active in this project. The foundry/ directory contains the project's artefact
+definitions, laws, appraisers, cycles, and flows. The user should switch to the Foundry agent
+to author and run workflows.
 
 Foundry is a skill-driven framework for governed artefact generation and evaluation.
 The pipeline: assay (populate memory) → forge (produce) → quench (deterministic checks) → appraise (subjective evaluation) → human-appraise (human review) → iterate.
@@ -142,7 +145,10 @@ Scripts are located at: ${path.join(packageRoot, 'scripts')}
 export function getBootstrapContent(directory, packageRoot, restartNeeded = false) {
   if (restartNeeded) {
     return `<FOUNDRY_CONTEXT>
-Foundry initialised. Restart OpenCode so the Foundry agent and model-routing agents register. After restart, switch to the Foundry agent to author and run workflows.
+Foundry has just been initialised in this project. The directory structure, stage agent files,
+and Foundry guide agent have all been created. Tell the user to restart OpenCode now so the new
+agents register. After restarting, the user should switch to the Foundry agent to author and
+run workflows.
 </FOUNDRY_CONTEXT>`;
   }
 

package/dist/.opencode/plugins/foundry.js

@@ -153,44 +153,6 @@ function runPluginBootstrap(worktree, pkgRoot) {
   }
 }
 
-const defaultSleep = ms => new Promise(resolve => { setTimeout(resolve, ms); });
-
-function resolveOpt(opts, key, fallback) {
-  return (opts && opts[key] !== undefined) ? opts[key] : fallback;
-}
-
-const STARTUP_MSG_MAX_MS = 3000;
-
-async function retryUntilReady(fn, opts) {
-  const sleep = resolveOpt(opts, 'sleep', defaultSleep);
-  const now = resolveOpt(opts, 'now', Date.now);
-  const maxMs = resolveOpt(opts, 'maxMs', STARTUP_MSG_MAX_MS);
-  const deadline = now() + maxMs;
-  while (now() < deadline) {
-    try {
-      await fn();
-      return;
-    } catch {
-      await sleep(500);
-    }
-  }
-}
-
-async function showStartupMessage(needsRestart, directory, client, timerFns) {
-  if (!client) return;
-  if (needsRestart) {
-    await retryUntilReady(() => client.tui.appendPrompt({
-      body: { text: 'Foundry initialised. Restart OpenCode so the Foundry agent registers, then switch to it to author and run workflows.' },
-    }), timerFns);
-    return;
-  }
-  if (existsSync(path.join(directory, 'foundry'))) {
-    await retryUntilReady(() => client.tui.showToast({
-      body: { message: 'Foundry is active', variant: 'info' },
-    }), timerFns);
-  }
-}
-
 export { buildCyclePromptExtras } from './foundry-tools/helpers.js';
 
 function buildTools(createTool, pending) {
@@ -227,7 +189,7 @@ function getFirstUserWithParts(output) {
   return firstUser;
 }
 
-export const FoundryPlugin = async ({ directory, client }) => {
+export const FoundryPlugin = async ({ directory }) => {
   // Pending store is per-plugin-instance (shared across all tool invocations).
   const pending = createPendingStore();
 
@@ -242,8 +204,6 @@ export const FoundryPlugin = async ({ directory, client }) => {
       }
 
       restartNeeded = runPluginBootstrap(directory, packageRoot);
-      // Fire-and-forget: don't block startup. messages.transform is the fallback.
-      showStartupMessage(restartNeeded, directory, client);
     },
 
     'experimental.chat.messages.transform': async (_input, output) => {

package/dist/CHANGELOG.md

@@ -1,5 +1,31 @@
 # Changelog
 
+## [3.2.6] - 2026-05-14
+
+### Fixed
+
+- **Bootstrap context messages confused the AI.** The injected `FOUNDRY_CONTEXT`
+  messages were written as direct user instructions ("Restart OpenCode..."),
+  but the AI reads them as system context and interprets them as commands to
+  itself. Rewritten as AI-facing framing: "Tell the user to restart...",
+  "The user should switch to the Foundry agent...".
+
+## [3.2.5] - 2026-05-14
+
+### Changed
+
+- **Startup flow simplified to "hello foundry".** Removed the TUI client
+  retry approach for startup messages. Users now type **hello foundry**
+  after restarting; the AI reads the injected `FOUNDRY_CONTEXT` and responds
+  with restart instructions or readiness confirmation. This replaces the
+  silent double-restart dance.
+- **E2E tests no longer depend on Python or `dd`.** The SIGTERM trap test
+  now uses shell builtins (`trap`/`echo`/`while`). The output cap tests use
+  small Node.js scripts instead of `dd` piped to `tr`. Tests are faster and
+  have no external dependencies.
+- **Install docs updated** (`README.md`, `docs/getting-started.md`) to
+  reflect the "hello foundry" flow.
+
 ## [3.2.4] - 2026-05-14
 
 ### Fixed

package/dist/README.md

@@ -103,9 +103,18 @@ Add the plugin to `opencode.json`:
 }
 ```
 
-Restart OpenCode so the plugin registers its tools and skills. You will see new
-tools and skills become available in OpenCode's command palette once the restart
-completes. Flow-management tools are now ready to use.
+Restart OpenCode so the plugin registers. On startup, Foundry bootstraps the
+directory structure, generates stage agents, and installs the Foundry guide
+agent automatically.
+
+After restart, type **hello foundry**. The assistant will tell you whether a
+further restart is needed and when to switch to the Foundry agent.
+
+Optionally, to make the package available to your project's local `node_modules`:
+
+```sh
+pnpm add -D @really-knows-ai/foundry
+```
 
 ---
 
@@ -121,29 +130,17 @@ The upgrade process asks clarifying questions for ambiguous routing, input contr
 
 ### Phase 1 — Install
 
-Add the plugin to `opencode.json` (see Install section above):
-
-```json
-{
-  "$schema": "https://opencode.ai/config.json",
-  "plugin": ["@really-knows-ai/foundry"]
-}
-```
-
-Then restart OpenCode so the plugin registers its tools and skills. You will see new
-tools and skills become available in OpenCode's command palette once the restart
-completes. Flow-management tools are now ready to use.
+Add the plugin to `opencode.json` (see Install section above), then restart
+OpenCode.
 
-### Phase 2 — Initialise
+Type **hello foundry**. The assistant will guide you through any remaining
+setup. If Foundry was just initialised, it will ask you to restart and switch
+to the **Foundry** agent. If Foundry is already set up, it will tell you to
+switch to the Foundry agent directly.
 
-Restart OpenCode after adding the plugin. On boot, the plugin's config hook runs
-a decision tree: if `foundry/` is missing or its VERSION does not match the
-installed plugin version, it bootstraps the directory structure, generates
-`foundry-<model>` stage agent files, installs the user-facing `Foundry` guide
-agent, and tells you to restart again.
+### Phase 2 — Switch to the Foundry agent
 
-Restart OpenCode a second time so the new agents register. After the restart,
-switch to the **Foundry** agent. The Foundry agent is the normal interface for
+Switch to the **Foundry** agent. The Foundry agent is the normal interface for
 authoring and running Foundry workflows.
 
 ### Phase 3 — Ask the Foundry agent for a flow

package/dist/docs/getting-started.md

@@ -21,7 +21,12 @@ Add Foundry to `opencode.json`:
 }
 ```
 
-OpenCode resolves the package itself — `npm install` is **not** required. Restart OpenCode (or reload plugins) so the plugin registers its tools and skills.
+Restart OpenCode so the plugin registers. On startup, Foundry bootstraps the
+directory structure, generates stage agents, and installs the Foundry guide
+agent automatically.
+
+After restart, type **hello foundry**. The assistant will tell you whether a
+further restart is needed and when to switch to the Foundry agent.
 
 Optionally, if you want the package available to your project's local node_modules (for editor tooling or scripts), run:
 
@@ -31,11 +36,20 @@ pnpm add -D @really-knows-ai/foundry
 
 ## Initialise
 
-Restart OpenCode after adding the plugin. On boot, the plugin's config hook checks project state: if `foundry/` is missing or its VERSION does not match the installed plugin version, it bootstraps the directory structure, generates model-routing `foundry-*` stage agents, installs the user-facing `Foundry` guide agent, and prompts a second restart.
+After restarting OpenCode with the plugin, type **hello foundry**. The
+assistant will read the Foundry bootstrap context and respond with guidance:
+
+- If Foundry was just initialised: it will tell you to restart again and switch
+  to the Foundry agent.
+- If Foundry is already set up: it will tell you to switch to the Foundry agent
+  directly.
 
-Restart OpenCode again so the new agents register. Then switch to the **Foundry** agent before authoring flows. The Foundry agent understands Foundry's authoring workflow and handles dependent setup such as artefact types, laws, validators, appraisers, cycles, and config branches.
+switch to the **Foundry** agent before authoring flows. The Foundry agent
+understands Foundry's authoring workflow and handles dependent setup such as
+artefact types, laws, validators, appraisers, cycles, and config branches.
 
-The `.foundry/` runtime directory (holding `.secret` for stage tokens) is created automatically on first plugin boot and added to `.gitignore`.
+The `.foundry/` runtime directory (holding `.secret` for stage tokens) is
+created automatically on first plugin boot and added to `.gitignore`.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@really-knows-ai/foundry",
-  "version": "3.2.4",
+  "version": "3.2.6",
   "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",