foundry-design-protocol 0.2.0-beta.10 → 0.2.0-beta.11
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.
- package/README.md +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -6,7 +6,7 @@ Foundry is a local-first precision design workbench for Codex, Cursor, and Claud
|
|
|
6
6
|
|
|
7
7
|
Foundry is distributed through npm, so testers do not need GitHub access.
|
|
8
8
|
|
|
9
|
-
> **Current public beta:** `0.2.0-beta.
|
|
9
|
+
> **Current public beta:** `0.2.0-beta.11`. Both npm `latest` and `beta` point to the same tested release. Use the unqualified command below for normal installation.
|
|
10
10
|
|
|
11
11
|
Full documentation is available at [withfoundry.ai](https://withfoundry.ai).
|
|
12
12
|
|
|
@@ -48,7 +48,7 @@ Then restart the coding agent, reopen the same project folder, and ask:
|
|
|
48
48
|
Start Foundry for this project and keep listening for Apply with agent requests.
|
|
49
49
|
```
|
|
50
50
|
|
|
51
|
-
You do not need to run a second terminal command when the agent starts Foundry for you. Apply requests remain queued safely when the agent is offline. Run `npx foundry-design doctor --repair` if the connection or generated integration needs repair.
|
|
51
|
+
You do not need to run a second terminal command when the agent starts Foundry for you. Apply requests remain queued safely when the agent is offline. After an active agent claims a batch, the MCP bridge keeps that handoff alive while the agent inspects source and begins the edit. If the agent process exits, Foundry releases the abandoned claim back to the queue instead of losing it. Run `npx foundry-design doctor --repair` if the connection or generated integration needs repair.
|
|
52
52
|
|
|
53
53
|
Update an existing installation with:
|
|
54
54
|
|
|
@@ -72,7 +72,7 @@ If an npm mirror or existing `npx` cache reports an old tag, bypass it with a te
|
|
|
72
72
|
|
|
73
73
|
```bash
|
|
74
74
|
FOUNDRY_NPX_CACHE="$(mktemp -d)"
|
|
75
|
-
npx --yes --prefer-online --registry=https://registry.npmjs.org --cache "$FOUNDRY_NPX_CACHE" --package=foundry-design@0.2.0-beta.
|
|
75
|
+
npx --yes --prefer-online --registry=https://registry.npmjs.org --cache "$FOUNDRY_NPX_CACHE" --package=foundry-design@0.2.0-beta.11 foundry-design
|
|
76
76
|
```
|
|
77
77
|
|
|
78
78
|
The beta supports Node.js 20 or newer. Read the [local-first safety model](https://withfoundry.ai/#safety) before using it with sensitive work.
|
|
@@ -104,7 +104,7 @@ Foundry remains local-first. Installing the plugin does not create an account, e
|
|
|
104
104
|
- Persistent, coalescing change ledger with JSON and consolidated prompt export
|
|
105
105
|
- Center-workspace review with editable approved batches, grouped targets, and unresolved-target blocking
|
|
106
106
|
- Persistent Apply with agent runs across Codex, Cursor, and Claude Code through MCP
|
|
107
|
-
-
|
|
107
|
+
- Automatically renewed agent handoffs that remain claimed during source inspection and safely return abandoned work to the queue
|
|
108
108
|
- Live source, rebuild, validation, retry, and rendered-verification progress
|
|
109
109
|
- Rendered verification that resumes after refresh and does not depend on Review remaining open
|
|
110
110
|
- Local MCP bridge for agent access
|