chore(release): 8.0.3 — widen the Interface peer to <0.56.0 and verify against 0.55.0

[drewstone]

Problem

@tangle-network/agent-interface 0.55.0 published 2026-08-16T06:44:30Z and took the npm latest tag. 8.0.2 declares >=0.54.0 <0.55.0, which excludes it, so this package is now the one that blocks a plain @latest install:

npm install @tangle-network/agent-knowledge@latest @tangle-network/agent-interface@latest

The same shape broke the fleet two hours earlier. Interface 0.54.0 published 2026-08-16T04:30:11Z, 88 seconds after agent-runtime#873 merged a <0.54.0 cap. 8.0.2 then moved to >=0.54.0 <0.55.0 while agent-runtime 0.135.3 still held >=0.53.0 <0.54.0 — disjoint ranges, so npm install @tangle-network/agent-runtime@latest @tangle-network/agent-knowledge@latest could not resolve with the interface never named.

Change

field	before	after
version	8.0.2	8.0.3
peer @tangle-network/agent-interface	>=0.54.0 <0.55.0	>=0.54.0 <0.56.0
dev @tangle-network/agent-interface	0.54.0	0.55.0

The floor stays at 0.54, so a consumer that still carries a package on the 0.54 generation resolves too. A single-generation window makes every adoption wave atomic, and interface minors publish faster than a wave can finish — measured cadence 0.53 → 0.54 = 20h26m, 0.54 → 0.55 = 2h14m.

Evidence that 0.55.0 is additive

Published tarballs 0.54.0 against 0.55.0:

• Added file: dist/environment-interactive.{d.ts,js}.
• Added: optional startInteractive? and interactive? on AgentEnvironment; optional interactiveAgent? capability block on AgentEnvironmentCapabilities; AgentInteractiveSession* schemas and helpers re-exported from index.
• Removed: nothing. Diffing the exported-symbol list of every changed .d.ts yields zero removals. The remaining diff lines are enum key ORDER in generated declarations.

Proof

• pnpm install: @tangle-network/agent-interface 0.54.0 -> 0.55.0.
• pnpm typecheck (typecheck:src + typecheck:contracts): exit 0.
• pnpm test: Test Files 60 passed | 3 skipped (63), Tests 575 passed | 12 skipped (587).

Related

Part of one wave that moves every first-party package onto a window that holds the generations it verifies against:

• agent-runtime#878 — >=0.53.0 <0.56.0, release 0.135.4
• sandbox-ui#254 — >=0.36.0 <0.56.0
• agent-dev-container#5742 — agent-profile-materialize >=0.47.0 <0.56.0

The release-order rule that removes the cause is tangle-network/agent-sdk#190. The manifest gate that catches a floor moving generation without its siblings is tangle-network/agent-app#445.

[drewstone]

@tangletools review now

[tangletools]

✅ Auto-approved drewstone PR — d0de68c8

This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

This approval is provisional. It rests on the audit running. If the audit cannot run — for example the CLI bridge rejects it — this approval is dismissed rather than left standing, so an unrun check never reads as a passing one.

_{tangletools · auto-approval · reason: drewstone_author · 2026-08-16T07:00:07Z}

[tangletools]

✅ Auto-approved drewstone PR — d0de68c8

This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.

This approval is provisional. It rests on the audit running. If the audit cannot run — for example the CLI bridge rejects it — this approval is dismissed rather than left standing, so an unrun check never reads as a passing one.

_{tangletools · auto-approval · reason: drewstone_author · 2026-08-16T07:00:16Z}

[tangletools]

⚠️ Value Audit did not run — no verdict

This is not an approval and not a clean bill of health. Neither interrogation lens returned a judgment, so this PR has no value-audit evidence for or against it.

Status	audit-incomplete (could not run)
Why	value: cli-bridge admission rejected (queue saturated); usefulness: cli-bridge admission rejected (queue saturated)
Lenses answered	0 of 2
What to do	re-run once the CLI bridge has capacity: pr-reviewerctl trigger <repo>#<pr> --force

💰 Value — error

value agent never ran: the CLI bridge refused admission (no model was started).

• Model: opencode/deepseek/deepseek-v4-pro
• Bridge attempts: 4
• Bridge error: opencode/kimi-for-coding/k2p7: Bridge returned 503: bridge at capacity (queue_timeout, lane=reserved): active=20/20 queued=8/48 — no model was started

🎯 Usefulness — error

usefulness agent never ran: the CLI bridge refused admission (no model was started).

• Model: opencode/deepseek/deepseek-v4-pro
• Bridge attempts: 4
• Bridge error: opencode/zai-coding-plan/glm-5.2: Bridge returned 503: bridge at capacity (queue_timeout, lane=reserved): active=20/20 queued=9/48 — no model was started

No concerns are listed because nothing examined the change — absence of findings here is absence of evidence, not a pass.

---

What this audit checks

It judges the change on its merits — not whether it was tasked out in an issue. Unticketed, fast-moving work is fine; the question is whether the change is good and whether a better or existing approach should be used instead.

Pass	What it asks
Heuristic	Vague title? Whitespace-only or cruft-bearing diff? (content signals only)
Duplication	Do added function/class names already exist elsewhere in the repo?
Value Audit	What does it do? What goal does it achieve? Is it good? Better architecture or already-exists?
Usefulness Audit	Does it integrate and fit? Will it hold up in real use and actually get used?

Findings are concerns, not blocks — the human reviewer decides what to do with them.

_{value-audit · 20260816T071529Z}

Value audit could not run (value: cli-bridge admission rejected (queue saturated); usefulness: cli-bridge admission rejected (queue saturated)). This approval was provisional on that audit running, so it is dismissed. Re-run the reviewer once the CLI bridge has capacity.

[drewstone]

Positive control — the wave resolves, proven before merge

The final proof normally waits on merge → publish. It does not have to: npm's resolver reads only manifests, so packing these branches and installing the tarballs beside the live registry is the same resolution the published packages will produce.

agent-runtime's catalog: specifiers were resolved from pnpm-workspace.yaml exactly as pnpm publish does (agent-core 0.9.1, agent-knowledge 8.0.2, agent-profile-materialize 0.15.2, agent-trace-contract ^1.0.2) and devDependencies dropped, since a consumer never installs them.

Negative control — the published state, right now

$ npm install --dry-run @tangle-network/agent-runtime@latest \
    @tangle-network/agent-knowledge@latest \
    @tangle-network/agent-eval@latest \
    @tangle-network/agent-interface@latest
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error     peer @tangle-network/agent-eval@">=0.145.16 <0.146.0" from @tangle-network/agent-knowledge@8.0.2
npm error Could not resolve dependency:
npm error peer @tangle-network/agent-interface@">=0.54.0 <0.55.0" from @tangle-network/agent-knowledge@8.0.2
  EXIT=1

Positive control — the same command against these branches

$ npm install --dry-run ./agent-runtime-0.135.4-resolved.tgz \
    ./tangle-network-agent-knowledge-8.0.3.tgz \
    @tangle-network/agent-eval@latest \
    @tangle-network/agent-interface@latest
add @tangle-network/agent-runtime 0.135.4
add @tangle-network/agent-knowledge 8.0.3
add @tangle-network/agent-interface 0.55.0
add @tangle-network/agent-eval 0.145.17
add @tangle-network/agent-core 0.9.2
add @tangle-network/agent-profile-materialize 0.15.2
add @tangle-network/agent-knowledge 8.0.2
add @tangle-network/agent-core 0.9.1
add @tangle-network/agent-interface 0.54.0

added 48 packages in 6s
  EXIT=0

Zero ERESOLVE. Interface 0.55.0 hoists to the root and satisfies both new peer windows. The nested 0.54.0 and agent-core 0.9.1 are exact dependencies of transitively pulled older releases — npm nests those rather than failing, so they never block an install.

Same command shape, same live registry, same day. Only the two manifests differ.

One more generation landed during this run

@tangle-network/agent-eval@0.145.17 published while the proof was being built, depending on agent-interface 0.55.0 and agent-core 0.9.2. That is the fourth first-party package to adopt 0.55 inside three hours, and the <0.56.0 window in these branches admits it with no further change — which is the point of widening the window instead of tracking the newest generation alone.

Root cause and the release-order rule: tangle-network/agent-sdk#190. Manifest gate for the sibling-floor half: tangle-network/agent-app#445.

[drewstone]

Superseded by merged PR #136. This release path is intentionally not being published; the next release will target Interface 0.56.0 and the aligned latest Eval.