chore(deps): accept the Eval 0.147.0 generation

[drewstone]

agent-runtime requires agent-eval >=0.147.0 <0.148.0; this package capped it at <0.147.0, so no install of the two together resolves. Peer moves to >=0.147.0 <0.148.0, dev pin to 0.147.0, version to 8.0.7.

The guard also had to change, and this is the substantive part. scripts/verify-package.mjs asserted that agent-eval pins agent-core exactly, by regex on the specifier string. agent-eval 0.147.0 declares ^0.9.4 deliberately — an exact first-party pin duplicates the package for every consumer already holding a later patch, which is what agent-runtime's packed-cohort guard now refuses fleet-wide.

The check's real intent is one installed copy, not one specifier shape. It now asserts the declared range admits the installed version — using this file's own assertCaretAdmits, the same helper it already applies to agent-interface — and assertSingleInstalledAgentStack keys off the installed version. A range that admits the installed copy passes; a range that does not still fails.

Verified locally: pnpm typecheck exit 0, pnpm build exit 0, pnpm verify:package exit 0 (the cohort and single-copy checks both run), pnpm test → 63 files passed | 3 skipped, 612 tests passed | 12 skipped.

[tangletools]

✅ Auto-approved drewstone PR — 12f3a458

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-17T01:49:59Z}