chore(layering): drop unused agent-knowledge peerDep + correct the layering diagram by drewstone · Pull Request #383 · tangle-network/agent-runtime

drewstone · 2026-06-24T20:25:19Z

What

Makes agent-runtime's layering truly one-way.

Remove the unused @tangle-network/agent-knowledge peerDependency (and its peerDependenciesMeta entry) from package.json, plus the matching pnpm-lock.yaml entries.
Correct the CLAUDE.md repo-layering diagram to the real dependency shape.

Why

agent-runtime's src imports @tangle-network/agent-knowledgezero times — it deliberately avoids it to prevent a dependency cycle. Domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (see src/mcp/feedback-store.ts: "The substrate cannot import @tangle-network/agent-knowledge … consumers wire their own adapter").

The declared peerDep had nothing importing it. The real, correct direction is agent-knowledge → agent-runtime: agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops.

The old diagram drew the two packages as siblings both sitting on agent-eval, which is wrong — agent-knowledge sits above agent-runtime. Corrected, and added the rule: the runtime stays domain-clean by taking domain stores/tools as injected adapters, never importing a domain package. The existing "agent-eval MUST NOT import from agent-runtime" rule is left intact.

Verification (all green)

Gate	Result
`CI=true pnpm install --frozen-lockfile`	exit 0, lockfile up to date
`pnpm run build`	exit 0
`pnpm run typecheck`	exit 0 (src + examples)
`pnpm run lint`	exit 0 (339 files, no fixes)
`pnpm test`	117 files, 1131 passed / 2 skipped
`pnpm run docs:check`	0 errors; freshness OK — 3 substrate peers present + accurate

Removing an unused peerDep breaks nothing; the lockfile delta only drops the agent-knowledge resolution.

…yering diagram agent-runtime's src imports @tangle-network/agent-knowledge zero times — it deliberately avoids it to prevent a dependency cycle; domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (src/mcp/feedback-store.ts). The declared peerDependency (and its peerDependenciesMeta entry) was therefore unused. The real, correct direction is agent-knowledge -> agent-runtime (agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops). - Remove @tangle-network/agent-knowledge from peerDependencies + peerDependenciesMeta - Update pnpm-lock.yaml to match - Correct the CLAUDE.md repo-layering diagram to the true shape and add the 'runtime takes domain stores/tools as injected adapters' rule

tangletools

✅ Auto-approved PR — `4e71ed4e`

Blanket team auto-approval is enabled for this reviewer service.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-06-24T20:25:27Z}

…mples typecheck (#384) * fix(examples): exclude the optional-peer researcher-loop from the examples typecheck #383 dropped the @tangle-network/agent-knowledge peer dependency (agent-runtime src imports it zero times — the layering is agent-knowledge -> agent-runtime), but left examples/researcher-loop importing @tangle-network/agent-knowledge/profiles. With the peer gone it isn't installed in CI, so typecheck:examples failed on the unresolved import — turning main red and blocking both the merge gate (ci.yml) and the release verify (publish.yml), which run the same pnpm run typecheck. researcher-loop is documented as an optional-peer example (examples/README.md); runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop). Exclude this one example from the examples typecheck rather than failing on a peer CI intentionally doesn't install. It still runs for users who install agent-knowledge. * chore(docs): regenerate the API reference for the merged onSandboxEvent tee #378 (ExecCtx.onSandboxEvent) merged to main but its API-reference regeneration never landed — the docs freshness gate runs after typecheck in ci.yml, and the examples typecheck was failing (the break this PR fixes), so the stale docs were masked. Regenerate docs/api/runtime.md: adds the onSandboxEvent section and refreshes the source line-number links. Generated output only (typedoc). * docs(examples): document the researcher-loop typecheck carve-out Drop the inline // comments from tsconfig.examples.json (clean JSON again, no JSONC-vs-strict-JSON tooling inconsistency) and move the rationale to examples/README.md, which now notes researcher-loop is excluded from typecheck:examples because it needs the optional agent-knowledge peer.

…e output streaming (#385) Ships since v0.77.0: - feat(runtime): ExecCtx.onSandboxEvent per-event tee for live output (#378) - chore(layering): drop the unused agent-knowledge peerDep (#383) - fix(examples): exclude the optional-peer researcher-loop from the examples typecheck (#384) Publishes on the v0.78.0 tag via publish.yml (tag/version lock + OIDC).

drewstone · 2026-06-24T20:25:19Z

What

Makes agent-runtime's layering truly one-way.

Remove the unused @tangle-network/agent-knowledge peerDependency (and its peerDependenciesMeta entry) from package.json, plus the matching pnpm-lock.yaml entries.
Correct the CLAUDE.md repo-layering diagram to the real dependency shape.

Why

agent-runtime's src imports @tangle-network/agent-knowledgezero times — it deliberately avoids it to prevent a dependency cycle. Domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (see src/mcp/feedback-store.ts: "The substrate cannot import @tangle-network/agent-knowledge … consumers wire their own adapter").

The declared peerDep had nothing importing it. The real, correct direction is agent-knowledge → agent-runtime: agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops.

The old diagram drew the two packages as siblings both sitting on agent-eval, which is wrong — agent-knowledge sits above agent-runtime. Corrected, and added the rule: the runtime stays domain-clean by taking domain stores/tools as injected adapters, never importing a domain package. The existing "agent-eval MUST NOT import from agent-runtime" rule is left intact.

Verification (all green)

Gate	Result
`CI=true pnpm install --frozen-lockfile`	exit 0, lockfile up to date
`pnpm run build`	exit 0
`pnpm run typecheck`	exit 0 (src + examples)
`pnpm run lint`	exit 0 (339 files, no fixes)
`pnpm test`	117 files, 1131 passed / 2 skipped
`pnpm run docs:check`	0 errors; freshness OK — 3 substrate peers present + accurate

Removing an unused peerDep breaks nothing; the lockfile delta only drops the agent-knowledge resolution.

…yering diagram agent-runtime's src imports @tangle-network/agent-knowledge zero times — it deliberately avoids it to prevent a dependency cycle; domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (src/mcp/feedback-store.ts). The declared peerDependency (and its peerDependenciesMeta entry) was therefore unused. The real, correct direction is agent-knowledge -> agent-runtime (agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops). - Remove @tangle-network/agent-knowledge from peerDependencies + peerDependenciesMeta - Update pnpm-lock.yaml to match - Correct the CLAUDE.md repo-layering diagram to the true shape and add the 'runtime takes domain stores/tools as injected adapters' rule

tangletools

✅ Auto-approved PR — `4e71ed4e`

Blanket team auto-approval is enabled for this reviewer service.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-06-24T20:25:27Z}

…mples typecheck (#384) * fix(examples): exclude the optional-peer researcher-loop from the examples typecheck #383 dropped the @tangle-network/agent-knowledge peer dependency (agent-runtime src imports it zero times — the layering is agent-knowledge -> agent-runtime), but left examples/researcher-loop importing @tangle-network/agent-knowledge/profiles. With the peer gone it isn't installed in CI, so typecheck:examples failed on the unresolved import — turning main red and blocking both the merge gate (ci.yml) and the release verify (publish.yml), which run the same pnpm run typecheck. researcher-loop is documented as an optional-peer example (examples/README.md); runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop). Exclude this one example from the examples typecheck rather than failing on a peer CI intentionally doesn't install. It still runs for users who install agent-knowledge. * chore(docs): regenerate the API reference for the merged onSandboxEvent tee #378 (ExecCtx.onSandboxEvent) merged to main but its API-reference regeneration never landed — the docs freshness gate runs after typecheck in ci.yml, and the examples typecheck was failing (the break this PR fixes), so the stale docs were masked. Regenerate docs/api/runtime.md: adds the onSandboxEvent section and refreshes the source line-number links. Generated output only (typedoc). * docs(examples): document the researcher-loop typecheck carve-out Drop the inline // comments from tsconfig.examples.json (clean JSON again, no JSONC-vs-strict-JSON tooling inconsistency) and move the rationale to examples/README.md, which now notes researcher-loop is excluded from typecheck:examples because it needs the optional agent-knowledge peer.

…e output streaming (#385) Ships since v0.77.0: - feat(runtime): ExecCtx.onSandboxEvent per-event tee for live output (#378) - chore(layering): drop the unused agent-knowledge peerDep (#383) - fix(examples): exclude the optional-peer researcher-loop from the examples typecheck (#384) Publishes on the v0.78.0 tag via publish.yml (tag/version lock + OIDC).

drewstone · 2026-06-24T20:25:19Z

What

Makes agent-runtime's layering truly one-way.

Remove the unused @tangle-network/agent-knowledge peerDependency (and its peerDependenciesMeta entry) from package.json, plus the matching pnpm-lock.yaml entries.
Correct the CLAUDE.md repo-layering diagram to the real dependency shape.

Why

agent-runtime's src imports @tangle-network/agent-knowledgezero times — it deliberately avoids it to prevent a dependency cycle. Domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (see src/mcp/feedback-store.ts: "The substrate cannot import @tangle-network/agent-knowledge … consumers wire their own adapter").

The declared peerDep had nothing importing it. The real, correct direction is agent-knowledge → agent-runtime: agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops.

The old diagram drew the two packages as siblings both sitting on agent-eval, which is wrong — agent-knowledge sits above agent-runtime. Corrected, and added the rule: the runtime stays domain-clean by taking domain stores/tools as injected adapters, never importing a domain package. The existing "agent-eval MUST NOT import from agent-runtime" rule is left intact.

Verification (all green)

Gate	Result
`CI=true pnpm install --frozen-lockfile`	exit 0, lockfile up to date
`pnpm run build`	exit 0
`pnpm run typecheck`	exit 0 (src + examples)
`pnpm run lint`	exit 0 (339 files, no fixes)
`pnpm test`	117 files, 1131 passed / 2 skipped
`pnpm run docs:check`	0 errors; freshness OK — 3 substrate peers present + accurate

Removing an unused peerDep breaks nothing; the lockfile delta only drops the agent-knowledge resolution.

…yering diagram agent-runtime's src imports @tangle-network/agent-knowledge zero times — it deliberately avoids it to prevent a dependency cycle; domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (src/mcp/feedback-store.ts). The declared peerDependency (and its peerDependenciesMeta entry) was therefore unused. The real, correct direction is agent-knowledge -> agent-runtime (agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops). - Remove @tangle-network/agent-knowledge from peerDependencies + peerDependenciesMeta - Update pnpm-lock.yaml to match - Correct the CLAUDE.md repo-layering diagram to the true shape and add the 'runtime takes domain stores/tools as injected adapters' rule

tangletools

✅ Auto-approved PR — `4e71ed4e`

Blanket team auto-approval is enabled for this reviewer service.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-06-24T20:25:27Z}

…mples typecheck (#384) * fix(examples): exclude the optional-peer researcher-loop from the examples typecheck #383 dropped the @tangle-network/agent-knowledge peer dependency (agent-runtime src imports it zero times — the layering is agent-knowledge -> agent-runtime), but left examples/researcher-loop importing @tangle-network/agent-knowledge/profiles. With the peer gone it isn't installed in CI, so typecheck:examples failed on the unresolved import — turning main red and blocking both the merge gate (ci.yml) and the release verify (publish.yml), which run the same pnpm run typecheck. researcher-loop is documented as an optional-peer example (examples/README.md); runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop). Exclude this one example from the examples typecheck rather than failing on a peer CI intentionally doesn't install. It still runs for users who install agent-knowledge. * chore(docs): regenerate the API reference for the merged onSandboxEvent tee #378 (ExecCtx.onSandboxEvent) merged to main but its API-reference regeneration never landed — the docs freshness gate runs after typecheck in ci.yml, and the examples typecheck was failing (the break this PR fixes), so the stale docs were masked. Regenerate docs/api/runtime.md: adds the onSandboxEvent section and refreshes the source line-number links. Generated output only (typedoc). * docs(examples): document the researcher-loop typecheck carve-out Drop the inline // comments from tsconfig.examples.json (clean JSON again, no JSONC-vs-strict-JSON tooling inconsistency) and move the rationale to examples/README.md, which now notes researcher-loop is excluded from typecheck:examples because it needs the optional agent-knowledge peer.

…e output streaming (#385) Ships since v0.77.0: - feat(runtime): ExecCtx.onSandboxEvent per-event tee for live output (#378) - chore(layering): drop the unused agent-knowledge peerDep (#383) - fix(examples): exclude the optional-peer researcher-loop from the examples typecheck (#384) Publishes on the v0.78.0 tag via publish.yml (tag/version lock + OIDC).

drewstone · 2026-06-24T20:25:19Z

What

Makes agent-runtime's layering truly one-way.

Remove the unused @tangle-network/agent-knowledge peerDependency (and its peerDependenciesMeta entry) from package.json, plus the matching pnpm-lock.yaml entries.
Correct the CLAUDE.md repo-layering diagram to the real dependency shape.

Why

agent-runtime's src imports @tangle-network/agent-knowledgezero times — it deliberately avoids it to prevent a dependency cycle. Domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (see src/mcp/feedback-store.ts: "The substrate cannot import @tangle-network/agent-knowledge … consumers wire their own adapter").

The declared peerDep had nothing importing it. The real, correct direction is agent-knowledge → agent-runtime: agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops.

The old diagram drew the two packages as siblings both sitting on agent-eval, which is wrong — agent-knowledge sits above agent-runtime. Corrected, and added the rule: the runtime stays domain-clean by taking domain stores/tools as injected adapters, never importing a domain package. The existing "agent-eval MUST NOT import from agent-runtime" rule is left intact.

Verification (all green)

Gate	Result
`CI=true pnpm install --frozen-lockfile`	exit 0, lockfile up to date
`pnpm run build`	exit 0
`pnpm run typecheck`	exit 0 (src + examples)
`pnpm run lint`	exit 0 (339 files, no fixes)
`pnpm test`	117 files, 1131 passed / 2 skipped
`pnpm run docs:check`	0 errors; freshness OK — 3 substrate peers present + accurate

Removing an unused peerDep breaks nothing; the lockfile delta only drops the agent-knowledge resolution.

…yering diagram agent-runtime's src imports @tangle-network/agent-knowledge zero times — it deliberately avoids it to prevent a dependency cycle; domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (src/mcp/feedback-store.ts). The declared peerDependency (and its peerDependenciesMeta entry) was therefore unused. The real, correct direction is agent-knowledge -> agent-runtime (agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops). - Remove @tangle-network/agent-knowledge from peerDependencies + peerDependenciesMeta - Update pnpm-lock.yaml to match - Correct the CLAUDE.md repo-layering diagram to the true shape and add the 'runtime takes domain stores/tools as injected adapters' rule

tangletools

✅ Auto-approved PR — `4e71ed4e`

Blanket team auto-approval is enabled for this reviewer service.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-06-24T20:25:27Z}

…mples typecheck (#384) * fix(examples): exclude the optional-peer researcher-loop from the examples typecheck #383 dropped the @tangle-network/agent-knowledge peer dependency (agent-runtime src imports it zero times — the layering is agent-knowledge -> agent-runtime), but left examples/researcher-loop importing @tangle-network/agent-knowledge/profiles. With the peer gone it isn't installed in CI, so typecheck:examples failed on the unresolved import — turning main red and blocking both the merge gate (ci.yml) and the release verify (publish.yml), which run the same pnpm run typecheck. researcher-loop is documented as an optional-peer example (examples/README.md); runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop). Exclude this one example from the examples typecheck rather than failing on a peer CI intentionally doesn't install. It still runs for users who install agent-knowledge. * chore(docs): regenerate the API reference for the merged onSandboxEvent tee #378 (ExecCtx.onSandboxEvent) merged to main but its API-reference regeneration never landed — the docs freshness gate runs after typecheck in ci.yml, and the examples typecheck was failing (the break this PR fixes), so the stale docs were masked. Regenerate docs/api/runtime.md: adds the onSandboxEvent section and refreshes the source line-number links. Generated output only (typedoc). * docs(examples): document the researcher-loop typecheck carve-out Drop the inline // comments from tsconfig.examples.json (clean JSON again, no JSONC-vs-strict-JSON tooling inconsistency) and move the rationale to examples/README.md, which now notes researcher-loop is excluded from typecheck:examples because it needs the optional agent-knowledge peer.

…e output streaming (#385) Ships since v0.77.0: - feat(runtime): ExecCtx.onSandboxEvent per-event tee for live output (#378) - chore(layering): drop the unused agent-knowledge peerDep (#383) - fix(examples): exclude the optional-peer researcher-loop from the examples typecheck (#384) Publishes on the v0.78.0 tag via publish.yml (tag/version lock + OIDC).

drewstone · 2026-06-24T20:25:19Z

What

Makes agent-runtime's layering truly one-way.

Remove the unused @tangle-network/agent-knowledge peerDependency (and its peerDependenciesMeta entry) from package.json, plus the matching pnpm-lock.yaml entries.
Correct the CLAUDE.md repo-layering diagram to the real dependency shape.

Why

agent-runtime's src imports @tangle-network/agent-knowledgezero times — it deliberately avoids it to prevent a dependency cycle. Domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (see src/mcp/feedback-store.ts: "The substrate cannot import @tangle-network/agent-knowledge … consumers wire their own adapter").

The declared peerDep had nothing importing it. The real, correct direction is agent-knowledge → agent-runtime: agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops.

The old diagram drew the two packages as siblings both sitting on agent-eval, which is wrong — agent-knowledge sits above agent-runtime. Corrected, and added the rule: the runtime stays domain-clean by taking domain stores/tools as injected adapters, never importing a domain package. The existing "agent-eval MUST NOT import from agent-runtime" rule is left intact.

Verification (all green)

Gate	Result
`CI=true pnpm install --frozen-lockfile`	exit 0, lockfile up to date
`pnpm run build`	exit 0
`pnpm run typecheck`	exit 0 (src + examples)
`pnpm run lint`	exit 0 (339 files, no fixes)
`pnpm test`	117 files, 1131 passed / 2 skipped
`pnpm run docs:check`	0 errors; freshness OK — 3 substrate peers present + accurate

Removing an unused peerDep breaks nothing; the lockfile delta only drops the agent-knowledge resolution.

…yering diagram agent-runtime's src imports @tangle-network/agent-knowledge zero times — it deliberately avoids it to prevent a dependency cycle; domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (src/mcp/feedback-store.ts). The declared peerDependency (and its peerDependenciesMeta entry) was therefore unused. The real, correct direction is agent-knowledge -> agent-runtime (agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops). - Remove @tangle-network/agent-knowledge from peerDependencies + peerDependenciesMeta - Update pnpm-lock.yaml to match - Correct the CLAUDE.md repo-layering diagram to the true shape and add the 'runtime takes domain stores/tools as injected adapters' rule

tangletools

✅ Auto-approved PR — `4e71ed4e`

Blanket team auto-approval is enabled for this reviewer service.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-06-24T20:25:27Z}

…mples typecheck (#384) * fix(examples): exclude the optional-peer researcher-loop from the examples typecheck #383 dropped the @tangle-network/agent-knowledge peer dependency (agent-runtime src imports it zero times — the layering is agent-knowledge -> agent-runtime), but left examples/researcher-loop importing @tangle-network/agent-knowledge/profiles. With the peer gone it isn't installed in CI, so typecheck:examples failed on the unresolved import — turning main red and blocking both the merge gate (ci.yml) and the release verify (publish.yml), which run the same pnpm run typecheck. researcher-loop is documented as an optional-peer example (examples/README.md); runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop). Exclude this one example from the examples typecheck rather than failing on a peer CI intentionally doesn't install. It still runs for users who install agent-knowledge. * chore(docs): regenerate the API reference for the merged onSandboxEvent tee #378 (ExecCtx.onSandboxEvent) merged to main but its API-reference regeneration never landed — the docs freshness gate runs after typecheck in ci.yml, and the examples typecheck was failing (the break this PR fixes), so the stale docs were masked. Regenerate docs/api/runtime.md: adds the onSandboxEvent section and refreshes the source line-number links. Generated output only (typedoc). * docs(examples): document the researcher-loop typecheck carve-out Drop the inline // comments from tsconfig.examples.json (clean JSON again, no JSONC-vs-strict-JSON tooling inconsistency) and move the rationale to examples/README.md, which now notes researcher-loop is excluded from typecheck:examples because it needs the optional agent-knowledge peer.

…e output streaming (#385) Ships since v0.77.0: - feat(runtime): ExecCtx.onSandboxEvent per-event tee for live output (#378) - chore(layering): drop the unused agent-knowledge peerDep (#383) - fix(examples): exclude the optional-peer researcher-loop from the examples typecheck (#384) Publishes on the v0.78.0 tag via publish.yml (tag/version lock + OIDC).

drewstone · 2026-06-24T20:25:19Z

What

Makes agent-runtime's layering truly one-way.

Remove the unused @tangle-network/agent-knowledge peerDependency (and its peerDependenciesMeta entry) from package.json, plus the matching pnpm-lock.yaml entries.
Correct the CLAUDE.md repo-layering diagram to the real dependency shape.

Why

agent-runtime's src imports @tangle-network/agent-knowledgezero times — it deliberately avoids it to prevent a dependency cycle. Domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (see src/mcp/feedback-store.ts: "The substrate cannot import @tangle-network/agent-knowledge … consumers wire their own adapter").

The declared peerDep had nothing importing it. The real, correct direction is agent-knowledge → agent-runtime: agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops.

The old diagram drew the two packages as siblings both sitting on agent-eval, which is wrong — agent-knowledge sits above agent-runtime. Corrected, and added the rule: the runtime stays domain-clean by taking domain stores/tools as injected adapters, never importing a domain package. The existing "agent-eval MUST NOT import from agent-runtime" rule is left intact.

Verification (all green)

Gate	Result
`CI=true pnpm install --frozen-lockfile`	exit 0, lockfile up to date
`pnpm run build`	exit 0
`pnpm run typecheck`	exit 0 (src + examples)
`pnpm run lint`	exit 0 (339 files, no fixes)
`pnpm test`	117 files, 1131 passed / 2 skipped
`pnpm run docs:check`	0 errors; freshness OK — 3 substrate peers present + accurate

Removing an unused peerDep breaks nothing; the lockfile delta only drops the agent-knowledge resolution.

…yering diagram agent-runtime's src imports @tangle-network/agent-knowledge zero times — it deliberately avoids it to prevent a dependency cycle; domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (src/mcp/feedback-store.ts). The declared peerDependency (and its peerDependenciesMeta entry) was therefore unused. The real, correct direction is agent-knowledge -> agent-runtime (agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops). - Remove @tangle-network/agent-knowledge from peerDependencies + peerDependenciesMeta - Update pnpm-lock.yaml to match - Correct the CLAUDE.md repo-layering diagram to the true shape and add the 'runtime takes domain stores/tools as injected adapters' rule

tangletools

✅ Auto-approved PR — `4e71ed4e`

Blanket team auto-approval is enabled for this reviewer service.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-06-24T20:25:27Z}

…mples typecheck (#384) * fix(examples): exclude the optional-peer researcher-loop from the examples typecheck #383 dropped the @tangle-network/agent-knowledge peer dependency (agent-runtime src imports it zero times — the layering is agent-knowledge -> agent-runtime), but left examples/researcher-loop importing @tangle-network/agent-knowledge/profiles. With the peer gone it isn't installed in CI, so typecheck:examples failed on the unresolved import — turning main red and blocking both the merge gate (ci.yml) and the release verify (publish.yml), which run the same pnpm run typecheck. researcher-loop is documented as an optional-peer example (examples/README.md); runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop). Exclude this one example from the examples typecheck rather than failing on a peer CI intentionally doesn't install. It still runs for users who install agent-knowledge. * chore(docs): regenerate the API reference for the merged onSandboxEvent tee #378 (ExecCtx.onSandboxEvent) merged to main but its API-reference regeneration never landed — the docs freshness gate runs after typecheck in ci.yml, and the examples typecheck was failing (the break this PR fixes), so the stale docs were masked. Regenerate docs/api/runtime.md: adds the onSandboxEvent section and refreshes the source line-number links. Generated output only (typedoc). * docs(examples): document the researcher-loop typecheck carve-out Drop the inline // comments from tsconfig.examples.json (clean JSON again, no JSONC-vs-strict-JSON tooling inconsistency) and move the rationale to examples/README.md, which now notes researcher-loop is excluded from typecheck:examples because it needs the optional agent-knowledge peer.

…e output streaming (#385) Ships since v0.77.0: - feat(runtime): ExecCtx.onSandboxEvent per-event tee for live output (#378) - chore(layering): drop the unused agent-knowledge peerDep (#383) - fix(examples): exclude the optional-peer researcher-loop from the examples typecheck (#384) Publishes on the v0.78.0 tag via publish.yml (tag/version lock + OIDC).

drewstone · 2026-06-24T20:25:19Z

What

Makes agent-runtime's layering truly one-way.

Remove the unused @tangle-network/agent-knowledge peerDependency (and its peerDependenciesMeta entry) from package.json, plus the matching pnpm-lock.yaml entries.
Correct the CLAUDE.md repo-layering diagram to the real dependency shape.

Why

agent-runtime's src imports @tangle-network/agent-knowledgezero times — it deliberately avoids it to prevent a dependency cycle. Domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (see src/mcp/feedback-store.ts: "The substrate cannot import @tangle-network/agent-knowledge … consumers wire their own adapter").

The declared peerDep had nothing importing it. The real, correct direction is agent-knowledge → agent-runtime: agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops.

The old diagram drew the two packages as siblings both sitting on agent-eval, which is wrong — agent-knowledge sits above agent-runtime. Corrected, and added the rule: the runtime stays domain-clean by taking domain stores/tools as injected adapters, never importing a domain package. The existing "agent-eval MUST NOT import from agent-runtime" rule is left intact.

Verification (all green)

Gate	Result
`CI=true pnpm install --frozen-lockfile`	exit 0, lockfile up to date
`pnpm run build`	exit 0
`pnpm run typecheck`	exit 0 (src + examples)
`pnpm run lint`	exit 0 (339 files, no fixes)
`pnpm test`	117 files, 1131 passed / 2 skipped
`pnpm run docs:check`	0 errors; freshness OK — 3 substrate peers present + accurate

Removing an unused peerDep breaks nothing; the lockfile delta only drops the agent-knowledge resolution.

…yering diagram agent-runtime's src imports @tangle-network/agent-knowledge zero times — it deliberately avoids it to prevent a dependency cycle; domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (src/mcp/feedback-store.ts). The declared peerDependency (and its peerDependenciesMeta entry) was therefore unused. The real, correct direction is agent-knowledge -> agent-runtime (agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops). - Remove @tangle-network/agent-knowledge from peerDependencies + peerDependenciesMeta - Update pnpm-lock.yaml to match - Correct the CLAUDE.md repo-layering diagram to the true shape and add the 'runtime takes domain stores/tools as injected adapters' rule

tangletools

✅ Auto-approved PR — `4e71ed4e`

Blanket team auto-approval is enabled for this reviewer service.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-06-24T20:25:27Z}

…mples typecheck (#384) * fix(examples): exclude the optional-peer researcher-loop from the examples typecheck #383 dropped the @tangle-network/agent-knowledge peer dependency (agent-runtime src imports it zero times — the layering is agent-knowledge -> agent-runtime), but left examples/researcher-loop importing @tangle-network/agent-knowledge/profiles. With the peer gone it isn't installed in CI, so typecheck:examples failed on the unresolved import — turning main red and blocking both the merge gate (ci.yml) and the release verify (publish.yml), which run the same pnpm run typecheck. researcher-loop is documented as an optional-peer example (examples/README.md); runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop). Exclude this one example from the examples typecheck rather than failing on a peer CI intentionally doesn't install. It still runs for users who install agent-knowledge. * chore(docs): regenerate the API reference for the merged onSandboxEvent tee #378 (ExecCtx.onSandboxEvent) merged to main but its API-reference regeneration never landed — the docs freshness gate runs after typecheck in ci.yml, and the examples typecheck was failing (the break this PR fixes), so the stale docs were masked. Regenerate docs/api/runtime.md: adds the onSandboxEvent section and refreshes the source line-number links. Generated output only (typedoc). * docs(examples): document the researcher-loop typecheck carve-out Drop the inline // comments from tsconfig.examples.json (clean JSON again, no JSONC-vs-strict-JSON tooling inconsistency) and move the rationale to examples/README.md, which now notes researcher-loop is excluded from typecheck:examples because it needs the optional agent-knowledge peer.

…e output streaming (#385) Ships since v0.77.0: - feat(runtime): ExecCtx.onSandboxEvent per-event tee for live output (#378) - chore(layering): drop the unused agent-knowledge peerDep (#383) - fix(examples): exclude the optional-peer researcher-loop from the examples typecheck (#384) Publishes on the v0.78.0 tag via publish.yml (tag/version lock + OIDC).

drewstone · 2026-06-24T20:25:19Z

What

Makes agent-runtime's layering truly one-way.

Remove the unused @tangle-network/agent-knowledge peerDependency (and its peerDependenciesMeta entry) from package.json, plus the matching pnpm-lock.yaml entries.
Correct the CLAUDE.md repo-layering diagram to the real dependency shape.

Why

agent-runtime's src imports @tangle-network/agent-knowledgezero times — it deliberately avoids it to prevent a dependency cycle. Domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (see src/mcp/feedback-store.ts: "The substrate cannot import @tangle-network/agent-knowledge … consumers wire their own adapter").

The declared peerDep had nothing importing it. The real, correct direction is agent-knowledge → agent-runtime: agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops.

The old diagram drew the two packages as siblings both sitting on agent-eval, which is wrong — agent-knowledge sits above agent-runtime. Corrected, and added the rule: the runtime stays domain-clean by taking domain stores/tools as injected adapters, never importing a domain package. The existing "agent-eval MUST NOT import from agent-runtime" rule is left intact.

Verification (all green)

Gate	Result
`CI=true pnpm install --frozen-lockfile`	exit 0, lockfile up to date
`pnpm run build`	exit 0
`pnpm run typecheck`	exit 0 (src + examples)
`pnpm run lint`	exit 0 (339 files, no fixes)
`pnpm test`	117 files, 1131 passed / 2 skipped
`pnpm run docs:check`	0 errors; freshness OK — 3 substrate peers present + accurate

Removing an unused peerDep breaks nothing; the lockfile delta only drops the agent-knowledge resolution.

…yering diagram agent-runtime's src imports @tangle-network/agent-knowledge zero times — it deliberately avoids it to prevent a dependency cycle; domain stores/tools enter by injection via createMcpServer({ feedbackStore }) (src/mcp/feedback-store.ts). The declared peerDependency (and its peerDependenciesMeta entry) was therefore unused. The real, correct direction is agent-knowledge -> agent-runtime (agent-knowledge/src/profiles/researcher.ts imports @tangle-network/agent-runtime/loops). - Remove @tangle-network/agent-knowledge from peerDependencies + peerDependenciesMeta - Update pnpm-lock.yaml to match - Correct the CLAUDE.md repo-layering diagram to the true shape and add the 'runtime takes domain stores/tools as injected adapters' rule

tangletools

✅ Auto-approved PR — `4e71ed4e`

Blanket team auto-approval is enabled for this reviewer service.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

_{tangletools · auto-approval · reason: blanket_auto_approve · 2026-06-24T20:25:27Z}

…mples typecheck (#384) * fix(examples): exclude the optional-peer researcher-loop from the examples typecheck #383 dropped the @tangle-network/agent-knowledge peer dependency (agent-runtime src imports it zero times — the layering is agent-knowledge -> agent-runtime), but left examples/researcher-loop importing @tangle-network/agent-knowledge/profiles. With the peer gone it isn't installed in CI, so typecheck:examples failed on the unresolved import — turning main red and blocking both the merge gate (ci.yml) and the release verify (publish.yml), which run the same pnpm run typecheck. researcher-loop is documented as an optional-peer example (examples/README.md); runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop). Exclude this one example from the examples typecheck rather than failing on a peer CI intentionally doesn't install. It still runs for users who install agent-knowledge. * chore(docs): regenerate the API reference for the merged onSandboxEvent tee #378 (ExecCtx.onSandboxEvent) merged to main but its API-reference regeneration never landed — the docs freshness gate runs after typecheck in ci.yml, and the examples typecheck was failing (the break this PR fixes), so the stale docs were masked. Regenerate docs/api/runtime.md: adds the onSandboxEvent section and refreshes the source line-number links. Generated output only (typedoc). * docs(examples): document the researcher-loop typecheck carve-out Drop the inline // comments from tsconfig.examples.json (clean JSON again, no JSONC-vs-strict-JSON tooling inconsistency) and move the rationale to examples/README.md, which now notes researcher-loop is excluded from typecheck:examples because it needs the optional agent-knowledge peer.

…e output streaming (#385) Ships since v0.77.0: - feat(runtime): ExecCtx.onSandboxEvent per-event tee for live output (#378) - chore(layering): drop the unused agent-knowledge peerDep (#383) - fix(examples): exclude the optional-peer researcher-loop from the examples typecheck (#384) Publishes on the v0.78.0 tag via publish.yml (tag/version lock + OIDC).

tangletools approved these changes Jun 24, 2026
View reviewed changes

drewstone merged commit 85f23c0 into mainJun 24, 2026
1 check failed

Tjemmmic mentioned this pull request Jun 25, 2026
fix(examples): exclude the optional-peer researcher-loop from the examples typecheck #384
Merged

Tjemmmic mentioned this pull request Jun 25, 2026
chore(release): 0.78.0 — ExecCtx.onSandboxEvent per-event tee for live output streaming #385
Merged