toko-tooling 0.45.0

Shared development tools, CI helpers and engineering rules for Toko Studios
Documentation
# Documentation-only CI selection

`perl scripts/ci/classify-ci-change.pl --event pull_request --ref refs/heads/main
--base <base-sha> --head <tested-sha> --policy ci/docs-only-paths.txt` prints `docs`
or `full`. Pass full commit identities through quoted arguments, not shell source.
For pushes use `--event push` and the before/after SHAs; a tag or release ref
always selects full qualification. PR comparison uses the merge base; pushes
require ancestry. Missing history, invalid input and failed Git observations
select `full` without fetching. An empty comparison also selects `full`.

Consumers own an exact, reviewed list of Markdown paths that are prose only.
There are no globs. The classifier reads identical policy bytes from both
compared commits, never an uncommitted list. Apart from the explicit version-only
exception below, unknown paths select full CI. Policy/workflow/code changes,
executable files and symlinks always select full CI. Renames are checked as
both deletion and addition. Do not list Markdown used by `include_str!`, doctests,
generation, packaging or other executable/build contracts; the extension alone
is not proof. Keep the classifier and workflow under normal code review: this
is an optimization, not a security boundary against workflow authors.

Submodule identity changes always select full CI, even when local Git settings
normally hide them. Relative-diff settings cannot narrow the compared paths.

Toko Tooling opts into `--allow-version-bump` for root `Cargo.toml` package.version.
Alongside reviewed prose, a literal version-only edit may use the reduced path when
`CHANGELOG.md` is also changed and allowlisted. Both committed endpoints must have
regular non-executable version/changelog files, canonical stable versions and
matching first changelog headings; historical headings must be older than their
own top version. The version must increase. Missing files, mismatches, malformed
versions, rollbacks and mixed code changes select full CI. Uncommitted repairs
cannot influence the decision. The rest of the Cargo manifest must be byte-identical;
changes to dependencies, package names or any other metadata retain full CI. The
historical VERSION convention is still understood, but changing version-source
formats selects full CI. This option is off by default for consumers. The normal version
check still runs; release/tag qualification is unchanged.

Use a cheap classification job with complete comparison history. Keep stable
required job names and run a real documentation check on the docs path. Avoid
workflow-level path filters that leave required checks pending. If classification
fails as a job, dependent checks must fail or run full qualification, never report
unverified success. Full code/tooling checks keep all required native hosts;
release gates remain complete and independent of this selection.

Toko Tooling's allowlist covers reviewed root, governance and developer-guide
prose. The guide expansion excludes documents with snapshot-companion declarations
because those headers control exported payloads. New paths still require explicit
review; embedded/build inputs remain outside the list. Documentation-only
changes select one Linux matrix entry instead of three identical Linux jobs,
checking local documentation links and whitespace. Normal changes retain native
Linux and both macOS jobs. The lint/security job still runs, including the
repository secret scan. A docs-only pass does not claim native qualification.