v0.8.2 — bilingual semantics, consumer runtime fixes

Bilingual business semantics, and a release path that verifies itself

Chinese readers see Chinese business logic, English readers see English — derived at compile time from the project's own documents, configuration, and identifiers, with the evidence and confidence behind each name kept alongside it. A name that cannot be read from evidence is marked 待确认 rather than invented, and that judgement is per language.

Since 0.8.1

• Per-locale uncertainty. English is no longer told a name is unconfirmed when English read it perfectly well.
• Consumer runtimes off Node 20. The composite action moves to cache v6, upload-artifact v7, upload-pages-artifact v5, deploy-pages v5; the workflow init --github generates moves to checkout v7.
• The CLI installs from npm. It previously installed from a GitHub Release asset — and v0.8.1 was tagged and published to npm with no Release created, so that URL 404'd. Moving @v1 onto it would have broken every consumer at the install step. The registry is where a published version actually lives.
• Version consistency is enforced, in both a test and release:check. Seven declarations must agree, including the action's cli-version default — the one that broke.
• The Pages branch is tested. upload-pages-artifact@v5 runs for real and its artifact is unpacked and inspected; the default is asserted to leave Pages alone; a failed analysis is asserted to publish the last successful map rather than a half-built one.

Runner requirement

The action runs on Node 24, which needs Actions Runner 2.327.1 or newer. GitHub-hosted runners are already there. A pinned self-hosted runner must be updated first.

Install

npm install --save-dev agent-runtime-map
npx agent-runtime-map init --github

All three packages are published to npm with signed provenance from GitHub Actions.