fix(examples): exclude the optional-peer researcher-loop from the examples typecheck - #384

Merged
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck
Jun 25, 2026
Merged

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck#384
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck

Conversation

@Tjemmmic

Copy link
Copy Markdown
Contributor

Problem

main CI is red and has been since #383. examples/researcher-loop/ imports @tangle-network/agent-knowledge/profiles, but #383 removed the @tangle-network/agent-knowledge peer dependency (correctly — agent-runtime's src imports it zero times; the layering is agent-knowledge -> agent-runtime). With the peer gone it is no longer installed in CI, so typecheck:examples fails on the unresolved import:

examples/researcher-loop/researcher-loop.ts(19,8): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'
examples/researcher-loop/synthetic-researcher.ts(14,51): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'

This is not cosmetic — pnpm run typecheck (which includes typecheck:examples) runs in both the merge gate (ci.yml) and the release verify (publish.yml), so the break blocks every agent-runtime merge and every publish until it is fixed.

Fix

Exclude examples/researcher-loop from tsconfig.examples.json. researcher-loop is documented in examples/README.md as the optional-peer example ("needs the optional @tangle-network/agent-knowledge peer"), and runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop, runtime-run). The right move is to stop CI from typechecking an optional-peer example when that peer isn't installed — not to delete a documented example or re-add the peer #383 deliberately dropped. The example still runs for users who install agent-knowledge.

No code import references researcher-loop (only a prose cross-reference in driver-loop), so the exclude is self-contained.

Validation

Replicated the CI sequence locally (install → build → typecheck):

  • pnpm install --frozen-lockfile
  • pnpm run build
  • pnpm run typecheckexit 0 (both tsc --noEmit and typecheck:examples)
  • pnpm run lintexit 0

…mples 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.
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 5764ab4d

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-25T03:09:19Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): 2 addressed.

Summary

The PR narrowly scopes an exclusion in tsconfig.examples.json to skip the researcher-loop example, which depends on an optional peer package that isn't installed. The functional change is correct, but the PR introduces inline JSON comments that are incompatible with many tools, and the examples README documentation is now stale.

Issues Found

2 total — 0 P1 (blocking) · 0 P2 (should fix) · 2 P3 (nice to have)

ℹ️ P3 — Inline JSON comments break strict JSON toolingAddressed

Note:4d5f2de: the inline // comments are removed — tsconfig.examples.json is strict JSON again (exclude: ["node_modules", "dist", "examples/researcher-loop"]). The rationale moved to examples/README.md.

  • File:tsconfig.examples.json:L11-L18
  • Problem: The diff adds // line comments inside the exclude array. While tsc can parse JSONC in tsconfig files, many tools in the ecosystem (ESLint JSON parsers, json CLI, editors with strict JSON validation, prettier) will reject this file as invalid JSON. The existing file was clean JSON with no comments, so this introduces a maintenance inconsistency.
  • Fix: Remove the inline comments and move the rationale into the PR description, README, or CLAUDE.md. The exclude array should simply contain: ["node_modules", "dist", "examples/researcher-loop"]

ℹ️ P3 — Examples README still claims full typecheck coverageAddressed

Note:4d5f2de: examples/README.md no longer says "all of them are typechecked" — it now notes researcher-loop is excluded from typecheck:examples because it needs the optional @tangle-network/agent-knowledge peer (not installed in CI).

  • File:examples/README.md
  • Problem: The README documents that all examples are typechecked by pnpm run typecheck:examples, but this PR excludes researcher-loop, making the documentation inaccurate and potentially misleading to maintainers.
  • Fix: Update the README to explicitly note the carve-out: Most examples are typechecked by pnpm run typecheck:examples; researcher-loop is excluded because it requires the optional @tangle-network/agent-knowledge peer.

✅ APPROVE

Status: the branch also regenerates the stale API reference (docs/api/runtime.md) for the already-merged onSandboxEvent tee — that docs-freshness gate was the remaining red CI step (it had been masked by the examples typecheck failure this PR fixes). With both, the full CI passes locally (typecheck, docs:check, lint).

The core config change is correct and low-risk — it prevents a typecheck failure caused by an intentionally uninstalled optional peer dependency. Only two P3 issues were found (JSON comment compatibility and stale README), neither of which warrants blocking the merge. They should be addressed as follow-up cleanup.

Quick Reference

  • P3: Inline JSON comments break strict JSON tooling
  • P3: Examples README still claims full typecheck coverage

Synthesized by Sokuza AI from multiple independent reviewers

…nt 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).
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 55dc1a8b

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-25T03:28:09Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples tsconfig and updates generated runtime API docs. The tsconfig change is narrowly scoped and well-commented, and the documentation diff is generated markdown with no executable behavior. No concrete blocking issues were identified.

No Issues Found

✅ APPROVE

Both reviewers and the diff confirm this is a config-only adjustment that preserves the existing typecheck contract for installed dependencies while excluding an example that depends on an optional peer package. The generated API docs add documentation for onSandboxEvent and update line-number references — no executable behavior is introduced. No P1 or P2 issues are present.


Synthesized by Sokuza AI from multiple independent reviewers

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.

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 4d5f2deb

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-25T03:29:43Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples typecheck and documents the carve-out in the examples README. The tsconfig change is correctly scoped, the README rationale is accurate, and the docs/api/runtime.md line-number updates are harmless. No correctness, security, API contract, or testing concerns.

No Issues Found

✅ APPROVE

Both independent reviewers approved the change, and the diff confirms it is narrowly scoped and consistent: the tsconfig exclude entry matches the documented exception, the README accurately explains why the optional agent-knowledge peer cannot be typechecked in CI, and no runtime behavior or production code is modified. The docs/api/runtime.md changes are generated API-doc line-number drift and pose no issue.


Synthesized by Sokuza AI from multiple independent reviewers

@Tjemmmic
Tjemmmic merged commit 8c47012 into mainJun 25, 2026
1 check passed
Tjemmmic added a commit that referenced this pull request Jun 25, 2026
…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).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@Tjemmmic@tangletools
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck - #384

Merged
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck
Jun 25, 2026
Merged

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck#384
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck

Conversation

@Tjemmmic

Copy link
Copy Markdown
Contributor

Problem

main CI is red and has been since #383. examples/researcher-loop/ imports @tangle-network/agent-knowledge/profiles, but #383 removed the @tangle-network/agent-knowledge peer dependency (correctly — agent-runtime's src imports it zero times; the layering is agent-knowledge -> agent-runtime). With the peer gone it is no longer installed in CI, so typecheck:examples fails on the unresolved import:

examples/researcher-loop/researcher-loop.ts(19,8): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'
examples/researcher-loop/synthetic-researcher.ts(14,51): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'

This is not cosmetic — pnpm run typecheck (which includes typecheck:examples) runs in both the merge gate (ci.yml) and the release verify (publish.yml), so the break blocks every agent-runtime merge and every publish until it is fixed.

Fix

Exclude examples/researcher-loop from tsconfig.examples.json. researcher-loop is documented in examples/README.md as the optional-peer example ("needs the optional @tangle-network/agent-knowledge peer"), and runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop, runtime-run). The right move is to stop CI from typechecking an optional-peer example when that peer isn't installed — not to delete a documented example or re-add the peer #383 deliberately dropped. The example still runs for users who install agent-knowledge.

No code import references researcher-loop (only a prose cross-reference in driver-loop), so the exclude is self-contained.

Validation

Replicated the CI sequence locally (install → build → typecheck):

  • pnpm install --frozen-lockfile
  • pnpm run build
  • pnpm run typecheckexit 0 (both tsc --noEmit and typecheck:examples)
  • pnpm run lintexit 0

…mples 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.
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 5764ab4d

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-25T03:09:19Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): 2 addressed.

Summary

The PR narrowly scopes an exclusion in tsconfig.examples.json to skip the researcher-loop example, which depends on an optional peer package that isn't installed. The functional change is correct, but the PR introduces inline JSON comments that are incompatible with many tools, and the examples README documentation is now stale.

Issues Found

2 total — 0 P1 (blocking) · 0 P2 (should fix) · 2 P3 (nice to have)

ℹ️ P3 — Inline JSON comments break strict JSON toolingAddressed

Note:4d5f2de: the inline // comments are removed — tsconfig.examples.json is strict JSON again (exclude: ["node_modules", "dist", "examples/researcher-loop"]). The rationale moved to examples/README.md.

  • File:tsconfig.examples.json:L11-L18
  • Problem: The diff adds // line comments inside the exclude array. While tsc can parse JSONC in tsconfig files, many tools in the ecosystem (ESLint JSON parsers, json CLI, editors with strict JSON validation, prettier) will reject this file as invalid JSON. The existing file was clean JSON with no comments, so this introduces a maintenance inconsistency.
  • Fix: Remove the inline comments and move the rationale into the PR description, README, or CLAUDE.md. The exclude array should simply contain: ["node_modules", "dist", "examples/researcher-loop"]

ℹ️ P3 — Examples README still claims full typecheck coverageAddressed

Note:4d5f2de: examples/README.md no longer says "all of them are typechecked" — it now notes researcher-loop is excluded from typecheck:examples because it needs the optional @tangle-network/agent-knowledge peer (not installed in CI).

  • File:examples/README.md
  • Problem: The README documents that all examples are typechecked by pnpm run typecheck:examples, but this PR excludes researcher-loop, making the documentation inaccurate and potentially misleading to maintainers.
  • Fix: Update the README to explicitly note the carve-out: Most examples are typechecked by pnpm run typecheck:examples; researcher-loop is excluded because it requires the optional @tangle-network/agent-knowledge peer.

✅ APPROVE

Status: the branch also regenerates the stale API reference (docs/api/runtime.md) for the already-merged onSandboxEvent tee — that docs-freshness gate was the remaining red CI step (it had been masked by the examples typecheck failure this PR fixes). With both, the full CI passes locally (typecheck, docs:check, lint).

The core config change is correct and low-risk — it prevents a typecheck failure caused by an intentionally uninstalled optional peer dependency. Only two P3 issues were found (JSON comment compatibility and stale README), neither of which warrants blocking the merge. They should be addressed as follow-up cleanup.

Quick Reference

  • P3: Inline JSON comments break strict JSON tooling
  • P3: Examples README still claims full typecheck coverage

Synthesized by Sokuza AI from multiple independent reviewers

…nt 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).
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 55dc1a8b

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-25T03:28:09Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples tsconfig and updates generated runtime API docs. The tsconfig change is narrowly scoped and well-commented, and the documentation diff is generated markdown with no executable behavior. No concrete blocking issues were identified.

No Issues Found

✅ APPROVE

Both reviewers and the diff confirm this is a config-only adjustment that preserves the existing typecheck contract for installed dependencies while excluding an example that depends on an optional peer package. The generated API docs add documentation for onSandboxEvent and update line-number references — no executable behavior is introduced. No P1 or P2 issues are present.


Synthesized by Sokuza AI from multiple independent reviewers

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.

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 4d5f2deb

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-25T03:29:43Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples typecheck and documents the carve-out in the examples README. The tsconfig change is correctly scoped, the README rationale is accurate, and the docs/api/runtime.md line-number updates are harmless. No correctness, security, API contract, or testing concerns.

No Issues Found

✅ APPROVE

Both independent reviewers approved the change, and the diff confirms it is narrowly scoped and consistent: the tsconfig exclude entry matches the documented exception, the README accurately explains why the optional agent-knowledge peer cannot be typechecked in CI, and no runtime behavior or production code is modified. The docs/api/runtime.md changes are generated API-doc line-number drift and pose no issue.


Synthesized by Sokuza AI from multiple independent reviewers

@Tjemmmic
Tjemmmic merged commit 8c47012 into mainJun 25, 2026
1 check passed
Tjemmmic added a commit that referenced this pull request Jun 25, 2026
…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).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@Tjemmmic@tangletools
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck - #384

Merged
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck
Jun 25, 2026
Merged

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck#384
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck

Conversation

@Tjemmmic

Copy link
Copy Markdown
Contributor

Problem

main CI is red and has been since #383. examples/researcher-loop/ imports @tangle-network/agent-knowledge/profiles, but #383 removed the @tangle-network/agent-knowledge peer dependency (correctly — agent-runtime's src imports it zero times; the layering is agent-knowledge -> agent-runtime). With the peer gone it is no longer installed in CI, so typecheck:examples fails on the unresolved import:

examples/researcher-loop/researcher-loop.ts(19,8): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'
examples/researcher-loop/synthetic-researcher.ts(14,51): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'

This is not cosmetic — pnpm run typecheck (which includes typecheck:examples) runs in both the merge gate (ci.yml) and the release verify (publish.yml), so the break blocks every agent-runtime merge and every publish until it is fixed.

Fix

Exclude examples/researcher-loop from tsconfig.examples.json. researcher-loop is documented in examples/README.md as the optional-peer example ("needs the optional @tangle-network/agent-knowledge peer"), and runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop, runtime-run). The right move is to stop CI from typechecking an optional-peer example when that peer isn't installed — not to delete a documented example or re-add the peer #383 deliberately dropped. The example still runs for users who install agent-knowledge.

No code import references researcher-loop (only a prose cross-reference in driver-loop), so the exclude is self-contained.

Validation

Replicated the CI sequence locally (install → build → typecheck):

  • pnpm install --frozen-lockfile
  • pnpm run build
  • pnpm run typecheckexit 0 (both tsc --noEmit and typecheck:examples)
  • pnpm run lintexit 0

…mples 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.
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 5764ab4d

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-25T03:09:19Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): 2 addressed.

Summary

The PR narrowly scopes an exclusion in tsconfig.examples.json to skip the researcher-loop example, which depends on an optional peer package that isn't installed. The functional change is correct, but the PR introduces inline JSON comments that are incompatible with many tools, and the examples README documentation is now stale.

Issues Found

2 total — 0 P1 (blocking) · 0 P2 (should fix) · 2 P3 (nice to have)

ℹ️ P3 — Inline JSON comments break strict JSON toolingAddressed

Note:4d5f2de: the inline // comments are removed — tsconfig.examples.json is strict JSON again (exclude: ["node_modules", "dist", "examples/researcher-loop"]). The rationale moved to examples/README.md.

  • File:tsconfig.examples.json:L11-L18
  • Problem: The diff adds // line comments inside the exclude array. While tsc can parse JSONC in tsconfig files, many tools in the ecosystem (ESLint JSON parsers, json CLI, editors with strict JSON validation, prettier) will reject this file as invalid JSON. The existing file was clean JSON with no comments, so this introduces a maintenance inconsistency.
  • Fix: Remove the inline comments and move the rationale into the PR description, README, or CLAUDE.md. The exclude array should simply contain: ["node_modules", "dist", "examples/researcher-loop"]

ℹ️ P3 — Examples README still claims full typecheck coverageAddressed

Note:4d5f2de: examples/README.md no longer says "all of them are typechecked" — it now notes researcher-loop is excluded from typecheck:examples because it needs the optional @tangle-network/agent-knowledge peer (not installed in CI).

  • File:examples/README.md
  • Problem: The README documents that all examples are typechecked by pnpm run typecheck:examples, but this PR excludes researcher-loop, making the documentation inaccurate and potentially misleading to maintainers.
  • Fix: Update the README to explicitly note the carve-out: Most examples are typechecked by pnpm run typecheck:examples; researcher-loop is excluded because it requires the optional @tangle-network/agent-knowledge peer.

✅ APPROVE

Status: the branch also regenerates the stale API reference (docs/api/runtime.md) for the already-merged onSandboxEvent tee — that docs-freshness gate was the remaining red CI step (it had been masked by the examples typecheck failure this PR fixes). With both, the full CI passes locally (typecheck, docs:check, lint).

The core config change is correct and low-risk — it prevents a typecheck failure caused by an intentionally uninstalled optional peer dependency. Only two P3 issues were found (JSON comment compatibility and stale README), neither of which warrants blocking the merge. They should be addressed as follow-up cleanup.

Quick Reference

  • P3: Inline JSON comments break strict JSON tooling
  • P3: Examples README still claims full typecheck coverage

Synthesized by Sokuza AI from multiple independent reviewers

…nt 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).
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 55dc1a8b

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-25T03:28:09Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples tsconfig and updates generated runtime API docs. The tsconfig change is narrowly scoped and well-commented, and the documentation diff is generated markdown with no executable behavior. No concrete blocking issues were identified.

No Issues Found

✅ APPROVE

Both reviewers and the diff confirm this is a config-only adjustment that preserves the existing typecheck contract for installed dependencies while excluding an example that depends on an optional peer package. The generated API docs add documentation for onSandboxEvent and update line-number references — no executable behavior is introduced. No P1 or P2 issues are present.


Synthesized by Sokuza AI from multiple independent reviewers

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.

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 4d5f2deb

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-25T03:29:43Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples typecheck and documents the carve-out in the examples README. The tsconfig change is correctly scoped, the README rationale is accurate, and the docs/api/runtime.md line-number updates are harmless. No correctness, security, API contract, or testing concerns.

No Issues Found

✅ APPROVE

Both independent reviewers approved the change, and the diff confirms it is narrowly scoped and consistent: the tsconfig exclude entry matches the documented exception, the README accurately explains why the optional agent-knowledge peer cannot be typechecked in CI, and no runtime behavior or production code is modified. The docs/api/runtime.md changes are generated API-doc line-number drift and pose no issue.


Synthesized by Sokuza AI from multiple independent reviewers

@Tjemmmic
Tjemmmic merged commit 8c47012 into mainJun 25, 2026
1 check passed
Tjemmmic added a commit that referenced this pull request Jun 25, 2026
…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).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@Tjemmmic@tangletools
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck - #384

Merged
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck
Jun 25, 2026
Merged

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck#384
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck

Conversation

@Tjemmmic

Copy link
Copy Markdown
Contributor

Problem

main CI is red and has been since #383. examples/researcher-loop/ imports @tangle-network/agent-knowledge/profiles, but #383 removed the @tangle-network/agent-knowledge peer dependency (correctly — agent-runtime's src imports it zero times; the layering is agent-knowledge -> agent-runtime). With the peer gone it is no longer installed in CI, so typecheck:examples fails on the unresolved import:

examples/researcher-loop/researcher-loop.ts(19,8): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'
examples/researcher-loop/synthetic-researcher.ts(14,51): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'

This is not cosmetic — pnpm run typecheck (which includes typecheck:examples) runs in both the merge gate (ci.yml) and the release verify (publish.yml), so the break blocks every agent-runtime merge and every publish until it is fixed.

Fix

Exclude examples/researcher-loop from tsconfig.examples.json. researcher-loop is documented in examples/README.md as the optional-peer example ("needs the optional @tangle-network/agent-knowledge peer"), and runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop, runtime-run). The right move is to stop CI from typechecking an optional-peer example when that peer isn't installed — not to delete a documented example or re-add the peer #383 deliberately dropped. The example still runs for users who install agent-knowledge.

No code import references researcher-loop (only a prose cross-reference in driver-loop), so the exclude is self-contained.

Validation

Replicated the CI sequence locally (install → build → typecheck):

  • pnpm install --frozen-lockfile
  • pnpm run build
  • pnpm run typecheckexit 0 (both tsc --noEmit and typecheck:examples)
  • pnpm run lintexit 0

…mples 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.
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 5764ab4d

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-25T03:09:19Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): 2 addressed.

Summary

The PR narrowly scopes an exclusion in tsconfig.examples.json to skip the researcher-loop example, which depends on an optional peer package that isn't installed. The functional change is correct, but the PR introduces inline JSON comments that are incompatible with many tools, and the examples README documentation is now stale.

Issues Found

2 total — 0 P1 (blocking) · 0 P2 (should fix) · 2 P3 (nice to have)

ℹ️ P3 — Inline JSON comments break strict JSON toolingAddressed

Note:4d5f2de: the inline // comments are removed — tsconfig.examples.json is strict JSON again (exclude: ["node_modules", "dist", "examples/researcher-loop"]). The rationale moved to examples/README.md.

  • File:tsconfig.examples.json:L11-L18
  • Problem: The diff adds // line comments inside the exclude array. While tsc can parse JSONC in tsconfig files, many tools in the ecosystem (ESLint JSON parsers, json CLI, editors with strict JSON validation, prettier) will reject this file as invalid JSON. The existing file was clean JSON with no comments, so this introduces a maintenance inconsistency.
  • Fix: Remove the inline comments and move the rationale into the PR description, README, or CLAUDE.md. The exclude array should simply contain: ["node_modules", "dist", "examples/researcher-loop"]

ℹ️ P3 — Examples README still claims full typecheck coverageAddressed

Note:4d5f2de: examples/README.md no longer says "all of them are typechecked" — it now notes researcher-loop is excluded from typecheck:examples because it needs the optional @tangle-network/agent-knowledge peer (not installed in CI).

  • File:examples/README.md
  • Problem: The README documents that all examples are typechecked by pnpm run typecheck:examples, but this PR excludes researcher-loop, making the documentation inaccurate and potentially misleading to maintainers.
  • Fix: Update the README to explicitly note the carve-out: Most examples are typechecked by pnpm run typecheck:examples; researcher-loop is excluded because it requires the optional @tangle-network/agent-knowledge peer.

✅ APPROVE

Status: the branch also regenerates the stale API reference (docs/api/runtime.md) for the already-merged onSandboxEvent tee — that docs-freshness gate was the remaining red CI step (it had been masked by the examples typecheck failure this PR fixes). With both, the full CI passes locally (typecheck, docs:check, lint).

The core config change is correct and low-risk — it prevents a typecheck failure caused by an intentionally uninstalled optional peer dependency. Only two P3 issues were found (JSON comment compatibility and stale README), neither of which warrants blocking the merge. They should be addressed as follow-up cleanup.

Quick Reference

  • P3: Inline JSON comments break strict JSON tooling
  • P3: Examples README still claims full typecheck coverage

Synthesized by Sokuza AI from multiple independent reviewers

…nt 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).
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 55dc1a8b

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-25T03:28:09Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples tsconfig and updates generated runtime API docs. The tsconfig change is narrowly scoped and well-commented, and the documentation diff is generated markdown with no executable behavior. No concrete blocking issues were identified.

No Issues Found

✅ APPROVE

Both reviewers and the diff confirm this is a config-only adjustment that preserves the existing typecheck contract for installed dependencies while excluding an example that depends on an optional peer package. The generated API docs add documentation for onSandboxEvent and update line-number references — no executable behavior is introduced. No P1 or P2 issues are present.


Synthesized by Sokuza AI from multiple independent reviewers

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.

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 4d5f2deb

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-25T03:29:43Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples typecheck and documents the carve-out in the examples README. The tsconfig change is correctly scoped, the README rationale is accurate, and the docs/api/runtime.md line-number updates are harmless. No correctness, security, API contract, or testing concerns.

No Issues Found

✅ APPROVE

Both independent reviewers approved the change, and the diff confirms it is narrowly scoped and consistent: the tsconfig exclude entry matches the documented exception, the README accurately explains why the optional agent-knowledge peer cannot be typechecked in CI, and no runtime behavior or production code is modified. The docs/api/runtime.md changes are generated API-doc line-number drift and pose no issue.


Synthesized by Sokuza AI from multiple independent reviewers

@Tjemmmic
Tjemmmic merged commit 8c47012 into mainJun 25, 2026
1 check passed
Tjemmmic added a commit that referenced this pull request Jun 25, 2026
…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).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@Tjemmmic@tangletools
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck - #384

Merged
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck
Jun 25, 2026
Merged

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck#384
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck

Conversation

@Tjemmmic

Copy link
Copy Markdown
Contributor

Problem

main CI is red and has been since #383. examples/researcher-loop/ imports @tangle-network/agent-knowledge/profiles, but #383 removed the @tangle-network/agent-knowledge peer dependency (correctly — agent-runtime's src imports it zero times; the layering is agent-knowledge -> agent-runtime). With the peer gone it is no longer installed in CI, so typecheck:examples fails on the unresolved import:

examples/researcher-loop/researcher-loop.ts(19,8): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'
examples/researcher-loop/synthetic-researcher.ts(14,51): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'

This is not cosmetic — pnpm run typecheck (which includes typecheck:examples) runs in both the merge gate (ci.yml) and the release verify (publish.yml), so the break blocks every agent-runtime merge and every publish until it is fixed.

Fix

Exclude examples/researcher-loop from tsconfig.examples.json. researcher-loop is documented in examples/README.md as the optional-peer example ("needs the optional @tangle-network/agent-knowledge peer"), and runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop, runtime-run). The right move is to stop CI from typechecking an optional-peer example when that peer isn't installed — not to delete a documented example or re-add the peer #383 deliberately dropped. The example still runs for users who install agent-knowledge.

No code import references researcher-loop (only a prose cross-reference in driver-loop), so the exclude is self-contained.

Validation

Replicated the CI sequence locally (install → build → typecheck):

  • pnpm install --frozen-lockfile
  • pnpm run build
  • pnpm run typecheckexit 0 (both tsc --noEmit and typecheck:examples)
  • pnpm run lintexit 0

…mples 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.
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 5764ab4d

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-25T03:09:19Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): 2 addressed.

Summary

The PR narrowly scopes an exclusion in tsconfig.examples.json to skip the researcher-loop example, which depends on an optional peer package that isn't installed. The functional change is correct, but the PR introduces inline JSON comments that are incompatible with many tools, and the examples README documentation is now stale.

Issues Found

2 total — 0 P1 (blocking) · 0 P2 (should fix) · 2 P3 (nice to have)

ℹ️ P3 — Inline JSON comments break strict JSON toolingAddressed

Note:4d5f2de: the inline // comments are removed — tsconfig.examples.json is strict JSON again (exclude: ["node_modules", "dist", "examples/researcher-loop"]). The rationale moved to examples/README.md.

  • File:tsconfig.examples.json:L11-L18
  • Problem: The diff adds // line comments inside the exclude array. While tsc can parse JSONC in tsconfig files, many tools in the ecosystem (ESLint JSON parsers, json CLI, editors with strict JSON validation, prettier) will reject this file as invalid JSON. The existing file was clean JSON with no comments, so this introduces a maintenance inconsistency.
  • Fix: Remove the inline comments and move the rationale into the PR description, README, or CLAUDE.md. The exclude array should simply contain: ["node_modules", "dist", "examples/researcher-loop"]

ℹ️ P3 — Examples README still claims full typecheck coverageAddressed

Note:4d5f2de: examples/README.md no longer says "all of them are typechecked" — it now notes researcher-loop is excluded from typecheck:examples because it needs the optional @tangle-network/agent-knowledge peer (not installed in CI).

  • File:examples/README.md
  • Problem: The README documents that all examples are typechecked by pnpm run typecheck:examples, but this PR excludes researcher-loop, making the documentation inaccurate and potentially misleading to maintainers.
  • Fix: Update the README to explicitly note the carve-out: Most examples are typechecked by pnpm run typecheck:examples; researcher-loop is excluded because it requires the optional @tangle-network/agent-knowledge peer.

✅ APPROVE

Status: the branch also regenerates the stale API reference (docs/api/runtime.md) for the already-merged onSandboxEvent tee — that docs-freshness gate was the remaining red CI step (it had been masked by the examples typecheck failure this PR fixes). With both, the full CI passes locally (typecheck, docs:check, lint).

The core config change is correct and low-risk — it prevents a typecheck failure caused by an intentionally uninstalled optional peer dependency. Only two P3 issues were found (JSON comment compatibility and stale README), neither of which warrants blocking the merge. They should be addressed as follow-up cleanup.

Quick Reference

  • P3: Inline JSON comments break strict JSON tooling
  • P3: Examples README still claims full typecheck coverage

Synthesized by Sokuza AI from multiple independent reviewers

…nt 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).
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 55dc1a8b

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-25T03:28:09Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples tsconfig and updates generated runtime API docs. The tsconfig change is narrowly scoped and well-commented, and the documentation diff is generated markdown with no executable behavior. No concrete blocking issues were identified.

No Issues Found

✅ APPROVE

Both reviewers and the diff confirm this is a config-only adjustment that preserves the existing typecheck contract for installed dependencies while excluding an example that depends on an optional peer package. The generated API docs add documentation for onSandboxEvent and update line-number references — no executable behavior is introduced. No P1 or P2 issues are present.


Synthesized by Sokuza AI from multiple independent reviewers

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.

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 4d5f2deb

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-25T03:29:43Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples typecheck and documents the carve-out in the examples README. The tsconfig change is correctly scoped, the README rationale is accurate, and the docs/api/runtime.md line-number updates are harmless. No correctness, security, API contract, or testing concerns.

No Issues Found

✅ APPROVE

Both independent reviewers approved the change, and the diff confirms it is narrowly scoped and consistent: the tsconfig exclude entry matches the documented exception, the README accurately explains why the optional agent-knowledge peer cannot be typechecked in CI, and no runtime behavior or production code is modified. The docs/api/runtime.md changes are generated API-doc line-number drift and pose no issue.


Synthesized by Sokuza AI from multiple independent reviewers

@Tjemmmic
Tjemmmic merged commit 8c47012 into mainJun 25, 2026
1 check passed
Tjemmmic added a commit that referenced this pull request Jun 25, 2026
…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).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@Tjemmmic@tangletools
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck - #384

Merged
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck
Jun 25, 2026
Merged

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck#384
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck

Conversation

@Tjemmmic

Copy link
Copy Markdown
Contributor

Problem

main CI is red and has been since #383. examples/researcher-loop/ imports @tangle-network/agent-knowledge/profiles, but #383 removed the @tangle-network/agent-knowledge peer dependency (correctly — agent-runtime's src imports it zero times; the layering is agent-knowledge -> agent-runtime). With the peer gone it is no longer installed in CI, so typecheck:examples fails on the unresolved import:

examples/researcher-loop/researcher-loop.ts(19,8): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'
examples/researcher-loop/synthetic-researcher.ts(14,51): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'

This is not cosmetic — pnpm run typecheck (which includes typecheck:examples) runs in both the merge gate (ci.yml) and the release verify (publish.yml), so the break blocks every agent-runtime merge and every publish until it is fixed.

Fix

Exclude examples/researcher-loop from tsconfig.examples.json. researcher-loop is documented in examples/README.md as the optional-peer example ("needs the optional @tangle-network/agent-knowledge peer"), and runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop, runtime-run). The right move is to stop CI from typechecking an optional-peer example when that peer isn't installed — not to delete a documented example or re-add the peer #383 deliberately dropped. The example still runs for users who install agent-knowledge.

No code import references researcher-loop (only a prose cross-reference in driver-loop), so the exclude is self-contained.

Validation

Replicated the CI sequence locally (install → build → typecheck):

  • pnpm install --frozen-lockfile
  • pnpm run build
  • pnpm run typecheckexit 0 (both tsc --noEmit and typecheck:examples)
  • pnpm run lintexit 0

…mples 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.
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 5764ab4d

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-25T03:09:19Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): 2 addressed.

Summary

The PR narrowly scopes an exclusion in tsconfig.examples.json to skip the researcher-loop example, which depends on an optional peer package that isn't installed. The functional change is correct, but the PR introduces inline JSON comments that are incompatible with many tools, and the examples README documentation is now stale.

Issues Found

2 total — 0 P1 (blocking) · 0 P2 (should fix) · 2 P3 (nice to have)

ℹ️ P3 — Inline JSON comments break strict JSON toolingAddressed

Note:4d5f2de: the inline // comments are removed — tsconfig.examples.json is strict JSON again (exclude: ["node_modules", "dist", "examples/researcher-loop"]). The rationale moved to examples/README.md.

  • File:tsconfig.examples.json:L11-L18
  • Problem: The diff adds // line comments inside the exclude array. While tsc can parse JSONC in tsconfig files, many tools in the ecosystem (ESLint JSON parsers, json CLI, editors with strict JSON validation, prettier) will reject this file as invalid JSON. The existing file was clean JSON with no comments, so this introduces a maintenance inconsistency.
  • Fix: Remove the inline comments and move the rationale into the PR description, README, or CLAUDE.md. The exclude array should simply contain: ["node_modules", "dist", "examples/researcher-loop"]

ℹ️ P3 — Examples README still claims full typecheck coverageAddressed

Note:4d5f2de: examples/README.md no longer says "all of them are typechecked" — it now notes researcher-loop is excluded from typecheck:examples because it needs the optional @tangle-network/agent-knowledge peer (not installed in CI).

  • File:examples/README.md
  • Problem: The README documents that all examples are typechecked by pnpm run typecheck:examples, but this PR excludes researcher-loop, making the documentation inaccurate and potentially misleading to maintainers.
  • Fix: Update the README to explicitly note the carve-out: Most examples are typechecked by pnpm run typecheck:examples; researcher-loop is excluded because it requires the optional @tangle-network/agent-knowledge peer.

✅ APPROVE

Status: the branch also regenerates the stale API reference (docs/api/runtime.md) for the already-merged onSandboxEvent tee — that docs-freshness gate was the remaining red CI step (it had been masked by the examples typecheck failure this PR fixes). With both, the full CI passes locally (typecheck, docs:check, lint).

The core config change is correct and low-risk — it prevents a typecheck failure caused by an intentionally uninstalled optional peer dependency. Only two P3 issues were found (JSON comment compatibility and stale README), neither of which warrants blocking the merge. They should be addressed as follow-up cleanup.

Quick Reference

  • P3: Inline JSON comments break strict JSON tooling
  • P3: Examples README still claims full typecheck coverage

Synthesized by Sokuza AI from multiple independent reviewers

…nt 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).
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 55dc1a8b

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-25T03:28:09Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples tsconfig and updates generated runtime API docs. The tsconfig change is narrowly scoped and well-commented, and the documentation diff is generated markdown with no executable behavior. No concrete blocking issues were identified.

No Issues Found

✅ APPROVE

Both reviewers and the diff confirm this is a config-only adjustment that preserves the existing typecheck contract for installed dependencies while excluding an example that depends on an optional peer package. The generated API docs add documentation for onSandboxEvent and update line-number references — no executable behavior is introduced. No P1 or P2 issues are present.


Synthesized by Sokuza AI from multiple independent reviewers

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.

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 4d5f2deb

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-25T03:29:43Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples typecheck and documents the carve-out in the examples README. The tsconfig change is correctly scoped, the README rationale is accurate, and the docs/api/runtime.md line-number updates are harmless. No correctness, security, API contract, or testing concerns.

No Issues Found

✅ APPROVE

Both independent reviewers approved the change, and the diff confirms it is narrowly scoped and consistent: the tsconfig exclude entry matches the documented exception, the README accurately explains why the optional agent-knowledge peer cannot be typechecked in CI, and no runtime behavior or production code is modified. The docs/api/runtime.md changes are generated API-doc line-number drift and pose no issue.


Synthesized by Sokuza AI from multiple independent reviewers

@Tjemmmic
Tjemmmic merged commit 8c47012 into mainJun 25, 2026
1 check passed
Tjemmmic added a commit that referenced this pull request Jun 25, 2026
…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).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@Tjemmmic@tangletools
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck - #384

Merged
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck
Jun 25, 2026
Merged

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck#384
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck

Conversation

@Tjemmmic

Copy link
Copy Markdown
Contributor

Problem

main CI is red and has been since #383. examples/researcher-loop/ imports @tangle-network/agent-knowledge/profiles, but #383 removed the @tangle-network/agent-knowledge peer dependency (correctly — agent-runtime's src imports it zero times; the layering is agent-knowledge -> agent-runtime). With the peer gone it is no longer installed in CI, so typecheck:examples fails on the unresolved import:

examples/researcher-loop/researcher-loop.ts(19,8): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'
examples/researcher-loop/synthetic-researcher.ts(14,51): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'

This is not cosmetic — pnpm run typecheck (which includes typecheck:examples) runs in both the merge gate (ci.yml) and the release verify (publish.yml), so the break blocks every agent-runtime merge and every publish until it is fixed.

Fix

Exclude examples/researcher-loop from tsconfig.examples.json. researcher-loop is documented in examples/README.md as the optional-peer example ("needs the optional @tangle-network/agent-knowledge peer"), and runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop, runtime-run). The right move is to stop CI from typechecking an optional-peer example when that peer isn't installed — not to delete a documented example or re-add the peer #383 deliberately dropped. The example still runs for users who install agent-knowledge.

No code import references researcher-loop (only a prose cross-reference in driver-loop), so the exclude is self-contained.

Validation

Replicated the CI sequence locally (install → build → typecheck):

  • pnpm install --frozen-lockfile
  • pnpm run build
  • pnpm run typecheckexit 0 (both tsc --noEmit and typecheck:examples)
  • pnpm run lintexit 0

…mples 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.
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 5764ab4d

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-25T03:09:19Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): 2 addressed.

Summary

The PR narrowly scopes an exclusion in tsconfig.examples.json to skip the researcher-loop example, which depends on an optional peer package that isn't installed. The functional change is correct, but the PR introduces inline JSON comments that are incompatible with many tools, and the examples README documentation is now stale.

Issues Found

2 total — 0 P1 (blocking) · 0 P2 (should fix) · 2 P3 (nice to have)

ℹ️ P3 — Inline JSON comments break strict JSON toolingAddressed

Note:4d5f2de: the inline // comments are removed — tsconfig.examples.json is strict JSON again (exclude: ["node_modules", "dist", "examples/researcher-loop"]). The rationale moved to examples/README.md.

  • File:tsconfig.examples.json:L11-L18
  • Problem: The diff adds // line comments inside the exclude array. While tsc can parse JSONC in tsconfig files, many tools in the ecosystem (ESLint JSON parsers, json CLI, editors with strict JSON validation, prettier) will reject this file as invalid JSON. The existing file was clean JSON with no comments, so this introduces a maintenance inconsistency.
  • Fix: Remove the inline comments and move the rationale into the PR description, README, or CLAUDE.md. The exclude array should simply contain: ["node_modules", "dist", "examples/researcher-loop"]

ℹ️ P3 — Examples README still claims full typecheck coverageAddressed

Note:4d5f2de: examples/README.md no longer says "all of them are typechecked" — it now notes researcher-loop is excluded from typecheck:examples because it needs the optional @tangle-network/agent-knowledge peer (not installed in CI).

  • File:examples/README.md
  • Problem: The README documents that all examples are typechecked by pnpm run typecheck:examples, but this PR excludes researcher-loop, making the documentation inaccurate and potentially misleading to maintainers.
  • Fix: Update the README to explicitly note the carve-out: Most examples are typechecked by pnpm run typecheck:examples; researcher-loop is excluded because it requires the optional @tangle-network/agent-knowledge peer.

✅ APPROVE

Status: the branch also regenerates the stale API reference (docs/api/runtime.md) for the already-merged onSandboxEvent tee — that docs-freshness gate was the remaining red CI step (it had been masked by the examples typecheck failure this PR fixes). With both, the full CI passes locally (typecheck, docs:check, lint).

The core config change is correct and low-risk — it prevents a typecheck failure caused by an intentionally uninstalled optional peer dependency. Only two P3 issues were found (JSON comment compatibility and stale README), neither of which warrants blocking the merge. They should be addressed as follow-up cleanup.

Quick Reference

  • P3: Inline JSON comments break strict JSON tooling
  • P3: Examples README still claims full typecheck coverage

Synthesized by Sokuza AI from multiple independent reviewers

…nt 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).
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 55dc1a8b

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-25T03:28:09Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples tsconfig and updates generated runtime API docs. The tsconfig change is narrowly scoped and well-commented, and the documentation diff is generated markdown with no executable behavior. No concrete blocking issues were identified.

No Issues Found

✅ APPROVE

Both reviewers and the diff confirm this is a config-only adjustment that preserves the existing typecheck contract for installed dependencies while excluding an example that depends on an optional peer package. The generated API docs add documentation for onSandboxEvent and update line-number references — no executable behavior is introduced. No P1 or P2 issues are present.


Synthesized by Sokuza AI from multiple independent reviewers

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.

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 4d5f2deb

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-25T03:29:43Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples typecheck and documents the carve-out in the examples README. The tsconfig change is correctly scoped, the README rationale is accurate, and the docs/api/runtime.md line-number updates are harmless. No correctness, security, API contract, or testing concerns.

No Issues Found

✅ APPROVE

Both independent reviewers approved the change, and the diff confirms it is narrowly scoped and consistent: the tsconfig exclude entry matches the documented exception, the README accurately explains why the optional agent-knowledge peer cannot be typechecked in CI, and no runtime behavior or production code is modified. The docs/api/runtime.md changes are generated API-doc line-number drift and pose no issue.


Synthesized by Sokuza AI from multiple independent reviewers

@Tjemmmic
Tjemmmic merged commit 8c47012 into mainJun 25, 2026
1 check passed
Tjemmmic added a commit that referenced this pull request Jun 25, 2026
…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).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@Tjemmmic@tangletools
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck - #384

Merged
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck
Jun 25, 2026
Merged

fix(examples): exclude the optional-peer researcher-loop from the examples typecheck#384
Tjemmmic merged 3 commits into
mainfrom
fix/exclude-optional-peer-example-from-typecheck

Conversation

@Tjemmmic

Copy link
Copy Markdown
Contributor

Problem

main CI is red and has been since #383. examples/researcher-loop/ imports @tangle-network/agent-knowledge/profiles, but #383 removed the @tangle-network/agent-knowledge peer dependency (correctly — agent-runtime's src imports it zero times; the layering is agent-knowledge -> agent-runtime). With the peer gone it is no longer installed in CI, so typecheck:examples fails on the unresolved import:

examples/researcher-loop/researcher-loop.ts(19,8): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'
examples/researcher-loop/synthetic-researcher.ts(14,51): error TS2307: Cannot find module '@tangle-network/agent-knowledge/profiles'

This is not cosmetic — pnpm run typecheck (which includes typecheck:examples) runs in both the merge gate (ci.yml) and the release verify (publish.yml), so the break blocks every agent-runtime merge and every publish until it is fixed.

Fix

Exclude examples/researcher-loop from tsconfig.examples.json. researcher-loop is documented in examples/README.md as the optional-peer example ("needs the optional @tangle-network/agent-knowledge peer"), and runLoop is also demonstrated by self-contained examples (driver-loop, ui-audit, supervisor-loop, runtime-run). The right move is to stop CI from typechecking an optional-peer example when that peer isn't installed — not to delete a documented example or re-add the peer #383 deliberately dropped. The example still runs for users who install agent-knowledge.

No code import references researcher-loop (only a prose cross-reference in driver-loop), so the exclude is self-contained.

Validation

Replicated the CI sequence locally (install → build → typecheck):

  • pnpm install --frozen-lockfile
  • pnpm run build
  • pnpm run typecheckexit 0 (both tsc --noEmit and typecheck:examples)
  • pnpm run lintexit 0

…mples 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.
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 5764ab4d

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-25T03:09:19Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): 2 addressed.

Summary

The PR narrowly scopes an exclusion in tsconfig.examples.json to skip the researcher-loop example, which depends on an optional peer package that isn't installed. The functional change is correct, but the PR introduces inline JSON comments that are incompatible with many tools, and the examples README documentation is now stale.

Issues Found

2 total — 0 P1 (blocking) · 0 P2 (should fix) · 2 P3 (nice to have)

ℹ️ P3 — Inline JSON comments break strict JSON toolingAddressed

Note:4d5f2de: the inline // comments are removed — tsconfig.examples.json is strict JSON again (exclude: ["node_modules", "dist", "examples/researcher-loop"]). The rationale moved to examples/README.md.

  • File:tsconfig.examples.json:L11-L18
  • Problem: The diff adds // line comments inside the exclude array. While tsc can parse JSONC in tsconfig files, many tools in the ecosystem (ESLint JSON parsers, json CLI, editors with strict JSON validation, prettier) will reject this file as invalid JSON. The existing file was clean JSON with no comments, so this introduces a maintenance inconsistency.
  • Fix: Remove the inline comments and move the rationale into the PR description, README, or CLAUDE.md. The exclude array should simply contain: ["node_modules", "dist", "examples/researcher-loop"]

ℹ️ P3 — Examples README still claims full typecheck coverageAddressed

Note:4d5f2de: examples/README.md no longer says "all of them are typechecked" — it now notes researcher-loop is excluded from typecheck:examples because it needs the optional @tangle-network/agent-knowledge peer (not installed in CI).

  • File:examples/README.md
  • Problem: The README documents that all examples are typechecked by pnpm run typecheck:examples, but this PR excludes researcher-loop, making the documentation inaccurate and potentially misleading to maintainers.
  • Fix: Update the README to explicitly note the carve-out: Most examples are typechecked by pnpm run typecheck:examples; researcher-loop is excluded because it requires the optional @tangle-network/agent-knowledge peer.

✅ APPROVE

Status: the branch also regenerates the stale API reference (docs/api/runtime.md) for the already-merged onSandboxEvent tee — that docs-freshness gate was the remaining red CI step (it had been masked by the examples typecheck failure this PR fixes). With both, the full CI passes locally (typecheck, docs:check, lint).

The core config change is correct and low-risk — it prevents a typecheck failure caused by an intentionally uninstalled optional peer dependency. Only two P3 issues were found (JSON comment compatibility and stale README), neither of which warrants blocking the merge. They should be addressed as follow-up cleanup.

Quick Reference

  • P3: Inline JSON comments break strict JSON tooling
  • P3: Examples README still claims full typecheck coverage

Synthesized by Sokuza AI from multiple independent reviewers

…nt 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).
tangletools
tangletools previously approved these changes Jun 25, 2026

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 55dc1a8b

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-25T03:28:09Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples tsconfig and updates generated runtime API docs. The tsconfig change is narrowly scoped and well-commented, and the documentation diff is generated markdown with no executable behavior. No concrete blocking issues were identified.

No Issues Found

✅ APPROVE

Both reviewers and the diff confirm this is a config-only adjustment that preserves the existing typecheck contract for installed dependencies while excluding an example that depends on an optional peer package. The generated API docs add documentation for onSandboxEvent and update line-number references — no executable behavior is introduced. No P1 or P2 issues are present.


Synthesized by Sokuza AI from multiple independent reviewers

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.

@tangletoolstangletools left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Auto-approved PR — 4d5f2deb

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-25T03:29:43Z

@Tjemmmic

Tjemmmic commented Jun 25, 2026

Copy link
Copy Markdown
ContributorAuthor

🤖 AI Code Review (ensemble)

Resolution (4d5f2de): No issues raised; independent re-review concurs, CI green.

Summary

The PR excludes the optional-peer researcher-loop example from the examples typecheck and documents the carve-out in the examples README. The tsconfig change is correctly scoped, the README rationale is accurate, and the docs/api/runtime.md line-number updates are harmless. No correctness, security, API contract, or testing concerns.

No Issues Found

✅ APPROVE

Both independent reviewers approved the change, and the diff confirms it is narrowly scoped and consistent: the tsconfig exclude entry matches the documented exception, the README accurately explains why the optional agent-knowledge peer cannot be typechecked in CI, and no runtime behavior or production code is modified. The docs/api/runtime.md changes are generated API-doc line-number drift and pose no issue.


Synthesized by Sokuza AI from multiple independent reviewers

@Tjemmmic
Tjemmmic merged commit 8c47012 into mainJun 25, 2026
1 check passed
Tjemmmic added a commit that referenced this pull request Jun 25, 2026
…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).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@Tjemmmic@tangletools