foundry-design-protocol 0.2.0-beta.20 → 0.2.0-beta.22
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/dist/index.d.ts +2696 -23
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +383 -33
- package/dist/index.js.map +1 -1
- package/dist/verification-value.d.ts +3 -0
- package/dist/verification-value.d.ts.map +1 -0
- package/dist/verification-value.js +250 -0
- package/dist/verification-value.js.map +1 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -10,7 +10,7 @@ Design Branches keeps parallel visual directions isolated inside one local sessi
|
|
|
10
10
|
|
|
11
11
|
Foundry is distributed through npm, so testers do not need GitHub access.
|
|
12
12
|
|
|
13
|
-
> **Current
|
|
13
|
+
> **Current beta release:** `0.2.0-beta.22`. After publication, both npm `latest` and `beta` resolve to this release.
|
|
14
14
|
|
|
15
15
|
Full documentation is available at [withfoundry.ai](https://withfoundry.ai).
|
|
16
16
|
|
|
@@ -141,7 +141,7 @@ If an npm mirror or existing `npx` cache reports an old tag, bypass it with a te
|
|
|
141
141
|
|
|
142
142
|
```bash
|
|
143
143
|
FOUNDRY_NPX_CACHE="$(mktemp -d)"
|
|
144
|
-
npx --yes --prefer-online --registry=https://registry.npmjs.org --cache "$FOUNDRY_NPX_CACHE" --package=foundry-design@0.2.0-beta.
|
|
144
|
+
npx --yes --prefer-online --registry=https://registry.npmjs.org --cache "$FOUNDRY_NPX_CACHE" --package=foundry-design@0.2.0-beta.22 foundry-design
|
|
145
145
|
```
|
|
146
146
|
|
|
147
147
|
The beta supports Node.js 20 or newer. Read the [local-first safety model](https://withfoundry.ai/#safety) before using it with sensitive work.
|
|
@@ -158,7 +158,7 @@ Foundry remains local-first. Installing the plugin does not create an account, e
|
|
|
158
158
|
|
|
159
159
|
### Cursor one-click connection
|
|
160
160
|
|
|
161
|
-
[Add the Foundry MCP bridge to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=foundry-design-control&config=
|
|
161
|
+
[Add the Foundry MCP bridge to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=foundry-design-control&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIi0tcHJlZmVyLW9ubGluZSIsImZvdW5kcnktZGVzaWduLW1jcC1zZXJ2ZXJAMC4yLjAtYmV0YS4yMiJdLCJlbnYiOnsiRk9VTkRSWV9ERVNJR05fUlVOVElNRV9VUkwiOiJodHRwOi8vMTI3LjAuMC4xOjQzODcifX0%3D), then run `npx foundry-design` inside the project. The repository's Cursor plugin additionally bundles the Foundry skill and session-start hook for marketplace distribution.
|
|
162
162
|
|
|
163
163
|
## Current capabilities
|
|
164
164
|
|
|
@@ -195,7 +195,7 @@ Foundry remains local-first. Installing the plugin does not create an account, e
|
|
|
195
195
|
|
|
196
196
|
The review surface explains the blast radius of every proposed change, including component instance count, token versus literal use, responsive and theme scope, and unresolved mapping risk. It never applies a source change merely because a preview override looks correct.
|
|
197
197
|
|
|
198
|
-
Foundry protocol `1.
|
|
198
|
+
Foundry protocol `1.3.0` reads existing `1.0.0`, `1.1.0`, and `1.2.0` sessions with migration defaults. All graph, operation, run, and verification data remains local and is available through `foundry-design export --format full`.
|
|
199
199
|
|
|
200
200
|
### Delivery export
|
|
201
201
|
|