toko-tooling 0.45.0

Shared development tools, CI helpers and engineering rules for Toko Studios
Documentation
# Dependency advisory and freshness review
<!-- Shared companions: rules/engineering-details.md -->

Apply the [common run contract](README.md). This initial task covers Rust
lockfiles; identify other package ecosystems as outside this task's coverage.

Inventory every selected maintained Cargo lockfile and the repository's existing
advisory policy, exemptions and prepared cargo-audit version. Check current
owner CI first. Freshness requires a current advisory observation even when the
source commit and lockfile have not changed.

For authorized execution with prepared tools, use the existing
[isolated RustSec preparation procedure](../docs/validation/source-helpers.md#isolated-rustsec-database-preparation).
An explicitly selected online run may read the official advisory feed into its
new evidence directory. Record its exact revision and use `cargo audit --no-fetch`
against that prepared database and the selected lockfile. An offline run records
the selected database revision and its freshness limitation. Stop on preparation
failure; do not let the audit silently fetch another database.

Report advisory ID, affected locked package/version, dependency path, supported
target/feature reachability, available correction and any reviewed exemption.
Distinguish an advisory match from proven exploitability, and audit completion
from current-feed coverage. Do not upgrade packages, edit exemptions or refresh
lockfiles as part of the check.

## Supplier freshness

Also apply the baseline's [dependency freshness rule](../TOKO-TOOLING.md#current-dependencies-and-upstream-independence).
Inventory direct normal, build, dev, optional and target-specific dependencies
across product and maintained qualification/fixture workspaces. Resolve renamed
packages through Cargo metadata; compare actual lock selections as well as
requirements. Observe current stable, non-yanked registry versions outside the
declared range too. Do not use `cargo update` for this read-only review.

Report supplier, consumer workspace/role, requirement, locked version, latest
published version and observation time. Distinguish direct selections from
upstream-only transitive versions, compatible minimums from stale locks, and
path candidates from published releases. Check existing adoption work and
approved holds before recommending changes. Each newer selection needs an
explicit adoption, bounded deferral or approved blocker disposition; an old
passing qualification suite is not a freshness decision. Missing registry or
graph evidence is incomplete coverage. Do not infer compatibility or upgrade
siblings from version distance alone.

## Remediation ownership

Apply the baseline's [shared dependency finding rule](../rules/engineering-details.md#shared-dependency-findings).
Reuse the supplying owner's canonical advisory issue, including IC Platform
for crypto/Agent dependencies supplied through its external IC boundary.
Retain the selected consumer's graph and operation evidence there, distinguishing
fresh observations from historical ones. Respect consolidated issue redirects;
separate consumer issues require distinct actionable work under that rule.

Return graph identity, advisory database revision/time, command/run evidence and
owning issues. This is a dependency advisory task, not a complete security audit.