Skip to content

chore(deps): bump substrate to agent-eval ^0.77.0 / agent-runtime ^0.44.0 + docs to live API#22

Merged
drewstone merged 1 commit into
mainfrom
chore/substrate-bump-0.77
Jun 3, 2026
Merged

chore(deps): bump substrate to agent-eval ^0.77.0 / agent-runtime ^0.44.0 + docs to live API#22
drewstone merged 1 commit into
mainfrom
chore/substrate-bump-0.77

Conversation

@drewstone
Copy link
Copy Markdown
Contributor

agent-knowledge had drifted ~35 minors behind the substrate and its docs described an API that hasn't existed since 0.42. This bumps it to current and rewrites the stale docs to the shipped contract.

Why it was frozen

  • @tangle-network/agent-eval ^0.42.0 — the 0.x caret traps it at >=0.42.0 <0.43.0, 35 minors behind 0.77.0. It physically could not resolve forward.
  • @tangle-network/agent-runtime ^0.25.0 — trapped <0.26.0, 19 behind 0.44.0.
  • minimumReleaseAgeExclude: [] — combined with the 3-day install cooldown, freshly-published substrate could never install.

Changes

  • deps: agent-eval ^0.42.0 → ^0.77.0, agent-runtime ^0.25.0 → ^0.44.0, sandbox (dev) ^0.3.0 → ^0.4.0
  • age gate: exclude the first-party @tangle-network substrate from minimumReleaseAge (matches the agent-runtime / tax / creative convention — the cooldown is for third-party supply-chain risk, not our own packages)
  • version: 1.5.2 → 1.6.0
  • docs: README, AGENTS, docs/architecture.md, and the release.ts docstring referenced removed/never-shipped functions (runKnowledgeBaseOptimization, knowledgeReleaseReportFromOptimization, runMultiShotOptimization). Rewritten to the shipped path: run an agent-eval improvement loop (runImprovementLoop) over KB variants, then knowledgeReleaseReport() folds the candidate/baseline RunRecord[] into release confidence.

Verification

The substrate imports are type-only (AnalystFinding/AnalystSeverity) plus the agent-runtime/loops subpath — all unchanged in 0.77/0.44. Against the bumped substrate, with zero source-logic edits:

  • pnpm typecheck → EXIT 0
  • pnpm test → 99 passed / 5 network-skipped
  • pnpm build → clean (DTS + JS emit)
  • repo-wide grep for the removed APIs → zero references remain

…44.0 + docs to live API

agent-knowledge was caret-trapped at agent-eval ^0.42.0 (>=0.42.0 <0.43.0, 35
minors behind 0.77.0) and agent-runtime ^0.25.0 (19 behind 0.44.0), with an
empty minimumReleaseAgeExclude that froze it under the 3-day install cooldown.

- bump @tangle-network/agent-eval ^0.42.0 -> ^0.77.0, agent-runtime ^0.25.0 ->
  ^0.44.0, sandbox (dev) ^0.3.0 -> ^0.4.0
- exclude the first-party @tangle-network substrate from minimumReleaseAge so
  freshly-published substrate installs (matches the agent-runtime/tax/creative
  convention; the age gate is for third-party supply-chain risk, not our own)
- version 1.5.2 -> 1.6.0

The substrate imports are type-only (AnalystFinding/AnalystSeverity) plus the
agent-runtime/loops subpath, all unchanged in 0.77/0.44 — typecheck EXIT=0,
99 tests pass, build clean with zero source edits.

Docs referenced removed/never-shipped functions (runKnowledgeBaseOptimization,
knowledgeReleaseReportFromOptimization, runMultiShotOptimization). Rewritten to
the shipped contract: run an agent-eval improvement loop over KB variants, then
knowledgeReleaseReport() folds the candidate/baseline RunRecords into release
confidence. README, AGENTS, architecture.md, and the release.ts docstring now
describe only the current API.
@drewstone drewstone merged commit feebfd1 into main Jun 3, 2026
1 check passed
@drewstone drewstone deleted the chore/substrate-bump-0.77 branch June 3, 2026 15:08
Sign up for free to 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.

1 participant