[dmealing]

What Changed

• Sets a 120s timeout on the server-backed D1/SQLite report tests in api-contract-report-sqlite.test.ts, and a 60s timeout on the libsql migrate and diff tests in view-recreate-drift-sqlite.test.ts. Each test boots its own Miniflare or libsql instance, which can exceed bun's 5000ms default under parallel lane load.
• Restamps first-touch version references to 1.1.3 (npm, PyPI, NuGet) and 8.1.3 (Maven Central) in README.md, AGENTS.md, and docs/ports/{typescript,java,kotlin,csharp}.md.
• Corrects the version-state prose in AGENTS.md so it lists 1.1.0 through 1.1.3 as released and the latest as 1.1.3 / 8.1.3.

Validation

Risk Assessment

✅ Low: Docs-only version restamps to 1.1.3 / 8.1.3 plus per-test timeout options on server-backed and DB-backed integration tests; no production code changes, and the remaining 1.1.2 mentions are legitimate minimum-version statements.

Testing

The Test agent exceeded its invocation budget before live validation completed; no evidence was gathered for this head.

• Outcome: ⚠️ 1 warning across 1 run (1h50m4s)

Pipeline

Updates from git push no-mistakes

✅ **Intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

⚠️ **Test** - 1 warning

• ⚠️ The Test agent did not finish within its invocation budget. Reported: agent run tests timed out at its 1h30m0s still-working cap (silent budget 1h15m0s; ran 1h30m1s): agent last produced output 23m20s ago (3 observed); agent reported: claude exited: signal: terminated: glm-claude: step=test route=light glm-claude: trying haiku55 (effort low, thinking off)... glm-claude: haiku55 failed (timed out after 2000s, partial stream discarded) glm-claude: haiku55 failed — failing over glm-claude: trying sonnet55 (effort high)... glm-claude: sonnet55 failed (timed out after 2000s, partial stream discarded) glm-claude: sonnet55 failed — fa.... This is a budget or provider-slowness cut, not a code failure. Re-running the same request costs another full budget, so no further attempt is made automatically. If this repository's targeted tests or evidence gathering routinely stay quiet longer than the default 30m0s, raise test_agent_timeout in global config. If the turn was still producing output or running a child process, set or raise test_agent_working_timeout there instead: a turn runs past test_agent_timeout only up to that still-working cap. Respond with fix to spend another budget: a repair turn runs only for selected findings other than this budget cut, then validation re-runs. Or abort and retry after raising the budget.

⏭️ **Document** - skipped

Step was skipped.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.