chore(deps): upgrade dependencies

[backgroundagents]

Upgrades project dependencies. See details in workflow run.

---

Automatically created by the "upgrade-main" workflow

[scottschreckengaust]

Review: PR #590 chore(deps): upgrade dependencies

Verdict: REQUEST_CHANGES — this bot dep-bump is not mergeable as-is because it breaks the build. build (agentcore) is RED and the cause is a dependency in this very diff (the ty type-checker bump), not a pre-existing/flaky failure. For a dependency PR, CI-green is the load-bearing signal, so a bump that turns the build red must be fixed before merge — even for routine bot hygiene.

Everything else in the bump is safe (details below); the block is narrow and mechanical.

Vision alignment

Bounded blast radius, mostly. Lockfile-only change (agent/uv.lock + yarn.lock; no package.json / pyproject.toml edits), so every bump stays within existing semver ranges. No attack-surface widening, no new top-level deps. The one leak past the intended boundary is ty: it is pinned bare ("ty", no version bound) in agent/pyproject.toml, so "regenerate within pins" still walked the type-checker forward to a stricter engine (0.0.56 → 0.0.59) that rejects previously-accepted source.

Blocking

B1 — ty 0.0.56 → 0.0.59 breaks //agent:typecheck (build (agentcore) job is RED). agent/uv.lock (ty package block; +version = "0.0.59").

• //agent:typecheck runs uv run ty check (agent/mise.toml:44). ty 0.0.59 now emits 9 new diagnostics in agent/tests/test_models.py — the source is unchanged in this PR, so this is purely the engine getting stricter/regressing on the same code:
  • 6× invalid-assignment "Property … is read-only" at test_models.py:30, 63, 140, 170, 416, 447. Each is an intentional negative test asserting Pydantic immutability (e.g. c.author = "bob" inside with pytest.raises(ValidationError):) on models declared model_config = ConfigDict(frozen=True, …) (agent/src/models.py:20, 47, 62, 117, 294, 305).
  • 2× invalid-argument-type at test_models.py:237, 244: content_trust={"issue": "untrusted-external", …} is inferred as dict[str, str] and rejected against the declared dict[str, ContentTrustLevel] where ContentTrustLevel = Literal["trusted","untrusted-external","memory"] (agent/src/models.py:71, 130).
• Note this is a two-step jump vs main, which currently pins ty 0.0.50.
• Fix — pick one, none should be silent:
  1. Cleanest for a pure dep-bump: pin ty==0.0.56 (last known-green) in agent/pyproject.toml and revert only the ty block of agent/uv.lock; let the other 8 Python bumps + all yarn bumps land green.
  2. If keeping ty current is desired: that requires touching agent/tests/test_models.py source (per-line # ty: ignore[invalid-assignment] on the 6 deliberate frozen-write negative tests, and an explicit dict[str, ContentTrustLevel] annotation / cast for the 2 content_trust literals). Source changes fall outside bot dep-hygiene and need a governance issue per ADR-003 — so this should be split out, not ridden in on the auto-approve bump.
  • Do not globally relax [tool.ty.rules] to mask this — it would hide real future frozen-write / literal bugs.

Non-blocking observations

• Cedar parity: intact. Neither cedarpy (Python) nor @cedar-policy/cedar-wasm (TS) is touched — cedarpy==4.8.4 and cedar-wasm@4.8.2 are unchanged on both sides. The paired-engine rule (AGENTS.md "Common mistakes") is not triggered; no contracts/cedar-parity/ refresh needed.
• No downgrades. All 9 uv.lock and ~60 yarn.lock transitions move forward.
• No synth-affecting core CDK bump. aws-cdk-lib and constructs are not changed (the @@ aws-cdk-lib@^2.260.0 line is only a hunk-context header). @aws-cdk/cloud-assembly-schema 54.8.0→54.11.0 and the aws-cdk CLI 2.1129.0→2.1131.0 are the CLI/cxapi side, within the pinned major — CDK snapshot tests should not shift.
• AWS SDK v3 clients (@aws-sdk/client-bedrock-agentcore/-runtime/-dynamodb/-ecs/-lambda/-s3/-secrets-manager) 3.1081.0→3.1087.0: standard weekly patch/minor cadence, no majors.
• Python bumps anyio 4.14.1→4.14.2, asgiref 3.11.1→3.12.1, botocore 1.43.42→1.43.48, coverage 7.15.0→7.15.1, grpcio 1.81.1→1.82.1, ruff 0.15.20→0.15.21, s3transfer 0.19.0→0.19.1, websockets 16.0→16.1 — all patch/minor, none with a known advisory.

Documentation

N/A — pure lockfile bump; no docs/guides/ or docs/design/ source touched, so no Starlight mirror sync required.

Tests & CI

• Secrets, deps, and workflow scan (OSV Scanner on yarn.lock + agent/uv.lock): pass — no advisories or vulnerable pulls introduced. CodeQL / Analyze (actions, js-ts, python): pass. Dead-code (advisory): pass. Validate PR title: pass.
• build (agentcore): FAIL — //agent:typecheck Found 9 diagnostics → exit 1 (B1). This is the sole failure and it is deterministic, not a flake.
• No new tests expected for a dep bump; the concern is that existing tests/typecheck must stay green, and they do not.

Review agents run

• pr-review-toolkit:code-reviewer — ran; independently reproduced the ty build-breaker mechanism and confirmed no downgrades / no synth-affecting core bump / Cedar untouched.
• silent-failure-hunter, type-design-analyzer — omitted (out of scope: lockfile-only diff, no error-handling or type-definition source changes).

Human heuristics

Base is fresh (PR head merge-base == origin/main @ 22705e83, single commit). Author is the backgroundagents bot; missing approved-issue is normal for pure dep hygiene and is not the basis for this block. The auto-approve label is present but must not auto-merge a red build — the failing agentcore job is a legitimate, self-caused gate failure. The narrowest green path is option (1): pin ty back and re-run.

_{🤖 Generated with Claude Code}

[scottschreckengaust]

Blocking: this ty bump (0.0.56 → 0.0.59) is what turns build (agentcore) red. ty is pinned bare ("ty") in agent/pyproject.toml, so the lockfile is its only bound and regenerating walked it to a stricter engine. uv run ty check (agent/mise.toml:44) now emits 9 new diagnostics in agent/tests/test_models.py (6 frozen-attribute negative tests + 2 content_trust Literal narrowings) even though that source is unchanged in this PR.

Cleanest fix to keep this a green, pure dep-bump: pin ty==0.0.56 in agent/pyproject.toml and revert just this ty block of the lockfile; let the other bumps land. Keeping ty current instead requires editing test_models.py (deliberate # ty: ignore + explicit dict[str, ContentTrustLevel] annotations), which is source work that should go through a governance issue rather than the auto-approve bot bump.