diff --git a/.changeset/audit-connectors-read-current.md b/.changeset/audit-connectors-read-current.md deleted file mode 100644 index 95970485..00000000 --- a/.changeset/audit-connectors-read-current.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"@proofoftech/breakwater": patch ---- - -Read required agent audit context values once before validating and recording them. Accessor-backed context cannot replace a validated `agentId` or `entryPath` during the copy. - -Document that `idempotencyKeyMigration` is validated at connector construction. Caller-held policies are read again when an execution reaches the absent-legacy migration gate and when a validated, ambiguous legacy migration reaches the acknowledgement gate; the single-tenant preset retains its frozen construction snapshot. Also clarify that the conformance harness reports `no-egress-declaration` after URL and host parsing succeeds before a subject is bound. diff --git a/.changeset/clear-causes-explain.md b/.changeset/clear-causes-explain.md deleted file mode 100644 index 21fa66ce..00000000 --- a/.changeset/clear-causes-explain.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@proofoftech/breakwater": minor ---- - -`ConnectorConformanceEscape` gains a required `cause` discriminator. Code that constructs escape records must supply the refusal cause. `NETWORK_IO_OUTSIDE_RUNTIME_FETCH` findings from `policies.fetch` identify URL parsing, host parsing, a missing egress declaration, or an undeclared host as the refused check. Trapped entry points record `outside-runtime-fetch` and retain their existing finding text. diff --git a/.changeset/lucky-moons-attend.md b/.changeset/lucky-moons-attend.md deleted file mode 100644 index 6101e9c3..00000000 --- a/.changeset/lucky-moons-attend.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -"@proofoftech/breakwater": minor -"@proofoftech/flowsafe": minor -"showcase": patch -"anchorage-agent-starter": patch ---- - -Require `@mastra/core` 1.67.0 exactly (previously 1.53.0). The peer is exact, so every consumer must move to 1.67.0 as well; this is breaking for consumers pinned to 1.53.0. 1.67.0 bundles for Cloudflare Workers and Vite again — mastra-ai/mastra#20638, the dynamic-import regression that held the pin at 1.53.0, closed upstream. - -`@mastra/cloudflare-d1` moves from 1.1.1 to 1.3.2, whose own peer requires a core newer than 1.53.0. FlowSafe's `@proofoftech/breakwater` peer floor rises to `>=0.15.0 <1.0.0` in step, that being the first Breakwater release built against the same core. - -The `@mastra/core` patch FlowSafe shipped under `patches/` is retired: 1.67.0 carries both fixes upstream (mastra-ai/mastra#23693, mastra-ai/mastra#23694). The patch file is gone from the published package, and so are the two refusals that required it — FlowSafe no longer refuses to construct a delivering notification dispatch tick, nor notification ingestion and dispatch requests, on an install whose core lacks the patch. Consequence for anyone running a core outside the declared peer without having applied the patch: a notification `source` named after an `Object.prototype` member is miscounted in the summary core renders, and its source delivery policy resolves the inherited member instead of the configured priority or default action. That configuration was unsupported before and remains so, but it now fails silently rather than loudly. Application roots that copied the patch into their own `patches/` should drop it along with the `patchedDependencies` entry or `postinstall` script that applied it. - -`createD1Storage({ domains })` composes the two storage domains 1.67.0 adds, `workflowDefinitions` and `knowledge`, through the same override seam as the other domains. `@mastra/cloudflare-d1` backs neither, so each resolves `undefined` unless a host supplies one through that seam. - -The workspace lockfile behind this release was resolved once with pnpm's seven-day minimum-release-age gate overridden for that resolution only. Five newly resolved versions were younger than the gate at resolution on 2026-09-19: `@mastra/core` 1.67.0 and `@mastra/schema-compat` 1.3.10 (published 2026-09-15), which the workspace's standing `@mastra/*` exclude admits with the gate on, and `posthog-node` 5.52.4 (2026-09-15), `@posthog/types` 1.412.2 (2026-09-17) and `@posthog/core` 1.55.0 (2026-09-18), which the override alone admitted. None of the five declares a lifecycle script or ships a native component; all five carry npm provenance attestations (SLSA v1, published from GitHub Actions); and `posthog-node`, with `@posthog/core` and `@posthog/types` beneath it, is a hard dependency of `@mastra/core` that ships inside a bundled Worker. - -The private `showcase` and `anchorage-agent-starter` packages move to the same core. diff --git a/.changeset/virtual-imports-refuse.md b/.changeset/virtual-imports-refuse.md deleted file mode 100644 index 63e0c562..00000000 --- a/.changeset/virtual-imports-refuse.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@proofoftech/flowsafe": patch ---- - -Keep `flowsafe-provision` inert when imported from stdin, eval or print programs, and virtual workers, even when an entry name aliases the script. Direct execution, file and directory symlinks, and file workers under eval parents continue to invoke the CLI. diff --git a/packages/agent-starter/CHANGELOG.md b/packages/agent-starter/CHANGELOG.md index 1d170050..853aecf6 100644 --- a/packages/agent-starter/CHANGELOG.md +++ b/packages/agent-starter/CHANGELOG.md @@ -1,5 +1,28 @@ # anchorage-agent-starter +## 0.0.18 + +### Patch Changes + +- 36c60c8: Require `@mastra/core` 1.67.0 exactly (previously 1.53.0). The peer is exact, so every consumer must move to 1.67.0 as well; this is breaking for consumers pinned to 1.53.0. 1.67.0 bundles for Cloudflare Workers and Vite again — mastra-ai/mastra#20638, the dynamic-import regression that held the pin at 1.53.0, closed upstream. + + `@mastra/cloudflare-d1` moves from 1.1.1 to 1.3.2, whose own peer requires a core newer than 1.53.0. FlowSafe's `@proofoftech/breakwater` peer floor rises to `>=0.15.0 <1.0.0` in step, that being the first Breakwater release built against the same core. + + The `@mastra/core` patch FlowSafe shipped under `patches/` is retired: 1.67.0 carries both fixes upstream (mastra-ai/mastra#23693, mastra-ai/mastra#23694). The patch file is gone from the published package, and so are the two refusals that required it — FlowSafe no longer refuses to construct a delivering notification dispatch tick, nor notification ingestion and dispatch requests, on an install whose core lacks the patch. Consequence for anyone running a core outside the declared peer without having applied the patch: a notification `source` named after an `Object.prototype` member is miscounted in the summary core renders, and its source delivery policy resolves the inherited member instead of the configured priority or default action. That configuration was unsupported before and remains so, but it now fails silently rather than loudly. Application roots that copied the patch into their own `patches/` should drop it along with the `patchedDependencies` entry or `postinstall` script that applied it. + + `createD1Storage({ domains })` composes the two storage domains 1.67.0 adds, `workflowDefinitions` and `knowledge`, through the same override seam as the other domains. `@mastra/cloudflare-d1` backs neither, so each resolves `undefined` unless a host supplies one through that seam. + + The workspace lockfile behind this release was resolved once with pnpm's seven-day minimum-release-age gate overridden for that resolution only. Five newly resolved versions were younger than the gate at resolution on 2026-09-19: `@mastra/core` 1.67.0 and `@mastra/schema-compat` 1.3.10 (published 2026-09-15), which the workspace's standing `@mastra/*` exclude admits with the gate on, and `posthog-node` 5.52.4 (2026-09-15), `@posthog/types` 1.412.2 (2026-09-17) and `@posthog/core` 1.55.0 (2026-09-18), which the override alone admitted. None of the five declares a lifecycle script or ships a native component; all five carry npm provenance attestations (SLSA v1, published from GitHub Actions); and `posthog-node`, with `@posthog/core` and `@posthog/types` beneath it, is a hard dependency of `@mastra/core` that ships inside a bundled Worker. + + The private `showcase` and `anchorage-agent-starter` packages move to the same core. + +- Updated dependencies [06b52a2] +- Updated dependencies [3f30616] +- Updated dependencies [36c60c8] +- Updated dependencies [36cfdc2] + - @proofoftech/breakwater@0.15.0 + - @proofoftech/flowsafe@0.22.0 + ## 0.0.17 ### Patch Changes diff --git a/packages/agent-starter/package.json b/packages/agent-starter/package.json index 9f3bda9f..520136e2 100644 --- a/packages/agent-starter/package.json +++ b/packages/agent-starter/package.json @@ -1,6 +1,6 @@ { "name": "anchorage-agent-starter", - "version": "0.0.17", + "version": "0.0.18", "private": true, "description": "Production-shaped Cloudflare Workers starter for durable, approval-gated Anchorage agents", "type": "module", diff --git a/packages/breakwater/CHANGELOG.md b/packages/breakwater/CHANGELOG.md index 61a52633..f30eeaa7 100644 --- a/packages/breakwater/CHANGELOG.md +++ b/packages/breakwater/CHANGELOG.md @@ -1,5 +1,28 @@ # @proofoftech/breakwater +## 0.15.0 + +### Minor Changes + +- 3f30616: `ConnectorConformanceEscape` gains a required `cause` discriminator. Code that constructs escape records must supply the refusal cause. `NETWORK_IO_OUTSIDE_RUNTIME_FETCH` findings from `policies.fetch` identify URL parsing, host parsing, a missing egress declaration, or an undeclared host as the refused check. Trapped entry points record `outside-runtime-fetch` and retain their existing finding text. +- 36c60c8: Require `@mastra/core` 1.67.0 exactly (previously 1.53.0). The peer is exact, so every consumer must move to 1.67.0 as well; this is breaking for consumers pinned to 1.53.0. 1.67.0 bundles for Cloudflare Workers and Vite again — mastra-ai/mastra#20638, the dynamic-import regression that held the pin at 1.53.0, closed upstream. + + `@mastra/cloudflare-d1` moves from 1.1.1 to 1.3.2, whose own peer requires a core newer than 1.53.0. FlowSafe's `@proofoftech/breakwater` peer floor rises to `>=0.15.0 <1.0.0` in step, that being the first Breakwater release built against the same core. + + The `@mastra/core` patch FlowSafe shipped under `patches/` is retired: 1.67.0 carries both fixes upstream (mastra-ai/mastra#23693, mastra-ai/mastra#23694). The patch file is gone from the published package, and so are the two refusals that required it — FlowSafe no longer refuses to construct a delivering notification dispatch tick, nor notification ingestion and dispatch requests, on an install whose core lacks the patch. Consequence for anyone running a core outside the declared peer without having applied the patch: a notification `source` named after an `Object.prototype` member is miscounted in the summary core renders, and its source delivery policy resolves the inherited member instead of the configured priority or default action. That configuration was unsupported before and remains so, but it now fails silently rather than loudly. Application roots that copied the patch into their own `patches/` should drop it along with the `patchedDependencies` entry or `postinstall` script that applied it. + + `createD1Storage({ domains })` composes the two storage domains 1.67.0 adds, `workflowDefinitions` and `knowledge`, through the same override seam as the other domains. `@mastra/cloudflare-d1` backs neither, so each resolves `undefined` unless a host supplies one through that seam. + + The workspace lockfile behind this release was resolved once with pnpm's seven-day minimum-release-age gate overridden for that resolution only. Five newly resolved versions were younger than the gate at resolution on 2026-09-19: `@mastra/core` 1.67.0 and `@mastra/schema-compat` 1.3.10 (published 2026-09-15), which the workspace's standing `@mastra/*` exclude admits with the gate on, and `posthog-node` 5.52.4 (2026-09-15), `@posthog/types` 1.412.2 (2026-09-17) and `@posthog/core` 1.55.0 (2026-09-18), which the override alone admitted. None of the five declares a lifecycle script or ships a native component; all five carry npm provenance attestations (SLSA v1, published from GitHub Actions); and `posthog-node`, with `@posthog/core` and `@posthog/types` beneath it, is a hard dependency of `@mastra/core` that ships inside a bundled Worker. + + The private `showcase` and `anchorage-agent-starter` packages move to the same core. + +### Patch Changes + +- 06b52a2: Read required agent audit context values once before validating and recording them. Accessor-backed context cannot replace a validated `agentId` or `entryPath` during the copy. + + Document that `idempotencyKeyMigration` is validated at connector construction. Caller-held policies are read again when an execution reaches the absent-legacy migration gate and when a validated, ambiguous legacy migration reaches the acknowledgement gate; the single-tenant preset retains its frozen construction snapshot. Also clarify that the conformance harness reports `no-egress-declaration` after URL and host parsing succeeds before a subject is bound. + ## 0.14.0 ### Minor Changes diff --git a/packages/breakwater/package.json b/packages/breakwater/package.json index 93ad4a02..b6bb5219 100644 --- a/packages/breakwater/package.json +++ b/packages/breakwater/package.json @@ -1,6 +1,6 @@ { "name": "@proofoftech/breakwater", - "version": "0.14.0", + "version": "0.15.0", "publishConfig": { "access": "public" }, diff --git a/packages/fleet-control/CHANGELOG.md b/packages/fleet-control/CHANGELOG.md index 0e70725b..c780e296 100644 --- a/packages/fleet-control/CHANGELOG.md +++ b/packages/fleet-control/CHANGELOG.md @@ -1,5 +1,13 @@ # @proofoftech/fleet-control +## 0.5.1 + +### Patch Changes + +- Updated dependencies [36c60c8] +- Updated dependencies [36cfdc2] + - @proofoftech/flowsafe@0.22.0 + ## 0.5.0 ### Minor Changes diff --git a/packages/fleet-control/package.json b/packages/fleet-control/package.json index 06e6c3e4..92bd0c34 100644 --- a/packages/fleet-control/package.json +++ b/packages/fleet-control/package.json @@ -1,6 +1,6 @@ { "name": "@proofoftech/fleet-control", - "version": "0.5.0", + "version": "0.5.1", "publishConfig": { "access": "public" }, diff --git a/packages/flowsafe/CHANGELOG.md b/packages/flowsafe/CHANGELOG.md index 8fb5327c..2a50ee5b 100644 --- a/packages/flowsafe/CHANGELOG.md +++ b/packages/flowsafe/CHANGELOG.md @@ -1,5 +1,25 @@ # @proofoftech/flowsafe +## 0.22.0 + +### Minor Changes + +- 36c60c8: Require `@mastra/core` 1.67.0 exactly (previously 1.53.0). The peer is exact, so every consumer must move to 1.67.0 as well; this is breaking for consumers pinned to 1.53.0. 1.67.0 bundles for Cloudflare Workers and Vite again — mastra-ai/mastra#20638, the dynamic-import regression that held the pin at 1.53.0, closed upstream. + + `@mastra/cloudflare-d1` moves from 1.1.1 to 1.3.2, whose own peer requires a core newer than 1.53.0. FlowSafe's `@proofoftech/breakwater` peer floor rises to `>=0.15.0 <1.0.0` in step, that being the first Breakwater release built against the same core. + + The `@mastra/core` patch FlowSafe shipped under `patches/` is retired: 1.67.0 carries both fixes upstream (mastra-ai/mastra#23693, mastra-ai/mastra#23694). The patch file is gone from the published package, and so are the two refusals that required it — FlowSafe no longer refuses to construct a delivering notification dispatch tick, nor notification ingestion and dispatch requests, on an install whose core lacks the patch. Consequence for anyone running a core outside the declared peer without having applied the patch: a notification `source` named after an `Object.prototype` member is miscounted in the summary core renders, and its source delivery policy resolves the inherited member instead of the configured priority or default action. That configuration was unsupported before and remains so, but it now fails silently rather than loudly. Application roots that copied the patch into their own `patches/` should drop it along with the `patchedDependencies` entry or `postinstall` script that applied it. + + `createD1Storage({ domains })` composes the two storage domains 1.67.0 adds, `workflowDefinitions` and `knowledge`, through the same override seam as the other domains. `@mastra/cloudflare-d1` backs neither, so each resolves `undefined` unless a host supplies one through that seam. + + The workspace lockfile behind this release was resolved once with pnpm's seven-day minimum-release-age gate overridden for that resolution only. Five newly resolved versions were younger than the gate at resolution on 2026-09-19: `@mastra/core` 1.67.0 and `@mastra/schema-compat` 1.3.10 (published 2026-09-15), which the workspace's standing `@mastra/*` exclude admits with the gate on, and `posthog-node` 5.52.4 (2026-09-15), `@posthog/types` 1.412.2 (2026-09-17) and `@posthog/core` 1.55.0 (2026-09-18), which the override alone admitted. None of the five declares a lifecycle script or ships a native component; all five carry npm provenance attestations (SLSA v1, published from GitHub Actions); and `posthog-node`, with `@posthog/core` and `@posthog/types` beneath it, is a hard dependency of `@mastra/core` that ships inside a bundled Worker. + + The private `showcase` and `anchorage-agent-starter` packages move to the same core. + +### Patch Changes + +- 36cfdc2: Keep `flowsafe-provision` inert when imported from stdin, eval or print programs, and virtual workers, even when an entry name aliases the script. Direct execution, file and directory symlinks, and file workers under eval parents continue to invoke the CLI. + ## 0.21.0 ### Minor Changes diff --git a/packages/flowsafe/package.json b/packages/flowsafe/package.json index 2772db52..a5036ff5 100644 --- a/packages/flowsafe/package.json +++ b/packages/flowsafe/package.json @@ -1,6 +1,6 @@ { "name": "@proofoftech/flowsafe", - "version": "0.21.0", + "version": "0.22.0", "publishConfig": { "access": "public" }, diff --git a/packages/showcase/CHANGELOG.md b/packages/showcase/CHANGELOG.md index ea235494..78739340 100644 --- a/packages/showcase/CHANGELOG.md +++ b/packages/showcase/CHANGELOG.md @@ -1,5 +1,28 @@ # showcase +## 0.0.24 + +### Patch Changes + +- 36c60c8: Require `@mastra/core` 1.67.0 exactly (previously 1.53.0). The peer is exact, so every consumer must move to 1.67.0 as well; this is breaking for consumers pinned to 1.53.0. 1.67.0 bundles for Cloudflare Workers and Vite again — mastra-ai/mastra#20638, the dynamic-import regression that held the pin at 1.53.0, closed upstream. + + `@mastra/cloudflare-d1` moves from 1.1.1 to 1.3.2, whose own peer requires a core newer than 1.53.0. FlowSafe's `@proofoftech/breakwater` peer floor rises to `>=0.15.0 <1.0.0` in step, that being the first Breakwater release built against the same core. + + The `@mastra/core` patch FlowSafe shipped under `patches/` is retired: 1.67.0 carries both fixes upstream (mastra-ai/mastra#23693, mastra-ai/mastra#23694). The patch file is gone from the published package, and so are the two refusals that required it — FlowSafe no longer refuses to construct a delivering notification dispatch tick, nor notification ingestion and dispatch requests, on an install whose core lacks the patch. Consequence for anyone running a core outside the declared peer without having applied the patch: a notification `source` named after an `Object.prototype` member is miscounted in the summary core renders, and its source delivery policy resolves the inherited member instead of the configured priority or default action. That configuration was unsupported before and remains so, but it now fails silently rather than loudly. Application roots that copied the patch into their own `patches/` should drop it along with the `patchedDependencies` entry or `postinstall` script that applied it. + + `createD1Storage({ domains })` composes the two storage domains 1.67.0 adds, `workflowDefinitions` and `knowledge`, through the same override seam as the other domains. `@mastra/cloudflare-d1` backs neither, so each resolves `undefined` unless a host supplies one through that seam. + + The workspace lockfile behind this release was resolved once with pnpm's seven-day minimum-release-age gate overridden for that resolution only. Five newly resolved versions were younger than the gate at resolution on 2026-09-19: `@mastra/core` 1.67.0 and `@mastra/schema-compat` 1.3.10 (published 2026-09-15), which the workspace's standing `@mastra/*` exclude admits with the gate on, and `posthog-node` 5.52.4 (2026-09-15), `@posthog/types` 1.412.2 (2026-09-17) and `@posthog/core` 1.55.0 (2026-09-18), which the override alone admitted. None of the five declares a lifecycle script or ships a native component; all five carry npm provenance attestations (SLSA v1, published from GitHub Actions); and `posthog-node`, with `@posthog/core` and `@posthog/types` beneath it, is a hard dependency of `@mastra/core` that ships inside a bundled Worker. + + The private `showcase` and `anchorage-agent-starter` packages move to the same core. + +- Updated dependencies [06b52a2] +- Updated dependencies [3f30616] +- Updated dependencies [36c60c8] +- Updated dependencies [36cfdc2] + - @proofoftech/breakwater@0.15.0 + - @proofoftech/flowsafe@0.22.0 + ## 0.0.23 ### Patch Changes diff --git a/packages/showcase/package.json b/packages/showcase/package.json index d9621898..82952179 100644 --- a/packages/showcase/package.json +++ b/packages/showcase/package.json @@ -1,6 +1,6 @@ { "name": "showcase", - "version": "0.0.23", + "version": "0.0.24", "private": true, "description": "Anchorage showcase — six runnable workflows and seven guardrail scenarios behind one React frontend", "type": "module",