Update Deps

<!-- This local skill replaces the shared update-deps skill (.ai/shared/skills/update-deps/SKILL.md) to add the anonymizer rules below. When the shared skill changes, reconcile this file with it and record the new base in .ai/local-skills/shared-bases.sha256; scripts/check-local-skill-overrides.sh fails until then. -->

Update Dependencies

Review or update the dependency scope requested by the user. Discover the repository's actual manifests and source-of-truth files before running ecosystem commands; do not assume they live at the root.

1. Resolve Scope and Sources of Truth

Inspect repository instructions, workspace manifests, lockfiles, dependency catalogs or resolutions, automated update configuration, and open dependency PRs when relevant. Common sources include:

• package.json, workspace manifests, bun.lock, and bunfig.toml
• every relevant pyproject.toml, uv.lock, and Python constraints file
• every relevant Cargo.toml and its Cargo.lock
• Dockerfile* and Compose YAML
• .github/workflows/* and dependency-update configuration

Default to an inventory and recommendation unless the user asks to apply updates. When applying a broad sweep, split it into coherent, independently validated batches. Give every major and heavy minor its own validated batch and commit. A heavy minor is a minor whose official release notes require migration or whose application requires source, configuration, or schema changes beyond dependency manifests and lockfiles.

"Separate" means its own batch and commit, not its own pull request and not omitted. An applied sweep covers every applicable update within the requested scope and each dependency's intended registry channel. Keep stable dependencies on stable releases. Include prerelease updates only within an explicitly selected prerelease channel. The only reason to leave a version behind is a mechanical block: a release still inside the repository's release-age quarantine, a peer or engine constraint that cannot be satisfied, or an upstream break with no migration path. Report each block with its reason. Upgrade size, review burden, and "risky major" are not blocks.

For every major and heavy minor, read the official release notes for capabilities worth adopting, not only for breakage. Report the relevant migration details and capabilities adopted or identified with the version moves.

Anonymizer Packages

@stll/anonymize, @stll/anonymize-wasm, and @stll/anonymize-data decide what leaves the workspace in anonymized chat, so any version move of them, patch included and whether alone or in a sweep, follows these rules:

1. Measure before and after. Before changing the version, with the current version installed, record the per-class corpus tallies:

   bun apps/api/scripts/name-matching-corpus.ts --failures > /tmp/corpus-before.txt

   Run it again after the update and put both tallies, or their difference, in the pull request.

2. The name-matching gates pass. From apps/api, run the corpus gate and the real-anonymizer suites against the new version:

   bun run test src/mcp/name-matching-corpus.test.ts \
     src/mcp/anonymization.test.ts \
     src/handlers/chat/stored-parts-send-mode.integration.test.ts \
     src/handlers/chat/provider-request-schemas.integration.test.ts \
     src/handlers/chat/provider-request-roles.integration.test.ts
   bun run test:property src/mcp/anonymization.property.test.ts

   and, from packages/anonymize-chat, bun run test:property. These run the native binding; the anonymize-chat property suite uses a stand-in runtime.

3. The WASM build is exercised for real. When @stll/anonymize-wasm moves, run bun --filter @stll/web test:e2e:landing: it drives the shipped WASM bundle in a browser and fails when the engine does not boot or detect. No automated test yet runs the chat worker's deny-list matching on the real WASM build, so also check it by hand on a local stack (bun run agent:up): add short, inflected, and diacritic names to a workspace deny list, send an anonymized chat that uses them, confirm each is replaced in the request the provider receives, and state the result in the pull request.

4. Bounds only tighten. Never lower a recall floor or raise a false-positive ceiling in name-matching-corpus.test.ts (or relax a property test) to make the update pass, unless the pull request states the reason, the classes and cases affected, and the before and after tallies, and that justification is reviewed and approved before merge. Raise a floor or lower a ceiling when the new version does better.

2. Inventory the Full Requested Surface

Run Bun inventory from the workspace root:

bun outdated --filter="*"

For each relevant Rust manifest, inspect the full dependency graph:

cargo outdated --manifest-path <path/to/Cargo.toml>

If cargo-outdated is unavailable, preview compatible lockfile updates with:

cargo update --manifest-path <path/to/Cargo.toml> --dry-run

This dry run is an incomplete inventory: it cannot surface releases outside the manifest's current version requirements. Supplement it with registry-aware cargo info or cargo search checks for every direct dependency in scope, and report the limitation. Do not default to --root-deps-only when cargo-outdated is available: transitive changes can carry the material risk.

For each uv-managed Python project, inspect direct and transitive packages:

uv tree --project <path> --locked --outdated

Also compare every direct dependency's declared constraint with authoritative PyPI metadata. uv tree --outdated can hide a newer release when the current constraint excludes it, so it is not a complete major-version inventory by itself. Keep accelerator packages and their container runtime in one compatibility batch: verify the Python wheel's CUDA/ROCm requirements against the selected base image and exercise a native-library import or linkage smoke test.

Inventory container references across Dockerfiles and Compose files:

rg -n '^\s*(FROM|image:)\s+' \
  --glob 'Dockerfile*' \
  --glob '*compose*.yml' \
  --glob '*compose*.yaml' \
  --glob '!node_modules/**'

Resolve current tags and digests from authoritative registry metadata. Inspect GitHub Actions when requested or when workflow files are in scope.

Flag exact prerelease pins and non-stable channels separately. Package-manager "latest" output can miss a newer alpha, beta, rc, next, canary, or dev release on the intended channel. Query registry tags and compare the deliberate channel.