@really-knows-ai/foundry 3.3.7 → 3.3.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -113,7 +113,7 @@ export function createOrchestrateTool({ tool, pending }) {
113
113
  },
114
114
 
115
115
  async execute(args, context) {
116
- const { runOrchestrate } = await import('../../scripts/orchestrate.js');
116
+ const { runOrchestrate } = await import('../../../scripts/orchestrate.js');
117
117
  const io = makeIO(context.worktree);
118
118
  const cwd = context.worktree;
119
119
  const secret = readOrCreateSecret(context.worktree);
package/dist/CHANGELOG.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # Changelog
2
2
 
3
+ ## [3.3.8] - 2026-05-19
4
+
5
+ ### Fixed
6
+
7
+ - **Build script now rewrites dynamic `import()` paths.** The `rewriteImports`
8
+ function only handled static `from '...'` imports, missing `await import()`
9
+ calls in `orchestrate-tool.js`. Added a second regex pass for dynamic imports.
10
+ - **New packaging test** verifies every relative import in `dist/` resolves.
11
+ - **add-flow now offers next steps after building.** After creating a flow on a
12
+ `config/*` branch, the skill presents dry-run / merge / leave options instead
13
+ of telling the LLM to auto-merge.
14
+
3
15
  ## [3.3.7] - 2026-05-18
4
16
 
5
17
  ### Fixed
@@ -145,7 +145,17 @@ After all dependencies are built, create the flow itself:
145
145
 
146
146
  If the tool returns `{ ok: false, errors }` because the target file already exists, read the existing flow file, incorporate the user's requested changes into the current body, propose the merged result for review, then write and commit the updated file.
147
147
 
148
- 3. **Report**: Show the user the flow file and the commit hash. Also summarise each dependency that was created, with its commit hash. Tell the user they can now ask the Foundry agent to run the flow.
148
+ 3. **Report and offer next steps**: Show the user the flow file and the commit hash. Summarise each dependency that was created, with its commit hash. Then present these options:
149
+
150
+ > The flow is built on the `config/*` branch. Before merging to main, you can:
151
+ >
152
+ > 1. **Dry-run the flow** — test it safely from the config branch without touching main. I'll run a dry-run: `dry-run/haiku-flow/01`.
153
+ > 2. **Merge to main** — commit the configuration and make the flow available for normal runs.
154
+ > 3. **Leave it on this branch** — you can review the configuration or come back later.
155
+ >
156
+ > Which would you like?
157
+
158
+ Do NOT automatically merge or call `foundry_git_finish` unless the user explicitly asks for it.
149
159
 
150
160
  ## Safety Rules
151
161
 
@@ -153,3 +163,4 @@ After all dependencies are built, create the flow itself:
153
163
  - Do not skip dependency validation.
154
164
  - Do not expose internal tool-call syntax to the user.
155
165
  - Do not continue when a branch or worktree state could overwrite user changes.
166
+ - Do not merge or call `foundry_git_finish` unless the user explicitly asks — always offer to dry-run first.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@really-knows-ai/foundry",
3
- "version": "3.3.7",
3
+ "version": "3.3.8",
4
4
  "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.",
5
5
  "type": "module",
6
6
  "main": "dist/.opencode/plugins/foundry.js",