Implementation details referenced by the stability policy
The stability policy classifies public interfaces. These repository scripts and runtime signals are implementation details, not additional CLI commands or compatibility promises.
Repository tooling
- Check the public command inventory against
main.subCommandsinsrc/cli.tsand each group'ssubCommands. scripts/build-registry-index.tsbuilds registry indexes; it is maintainer tooling outside the public CLI.scripts/rekey-asset-ref.tsre-keys earned signal from an old ref to a new one. Normal rename remains delete/create, with a new identity.- In 0.10,
akm-migrateships inside theakm-clipackage alongsideakm, with no separate package.task-to-v4.tsandtask-source-v3-frozen.tslive underscripts/akm-migrate/migrate/, outsidesrc/. The standalone executable is deprecated for 0.11; callers should useakm migrate status/apply. BundleAdapter.placeNew()was removed in 0.10 because nothing called it. Writes use AKM's fixed type-to-directory table. Supporting writes into a non-AKM adapter layout would need placement support again (#1163).
Runtime and test environment
AKM_EVENT_SOURCE is a documented input (see STABILITY.md).
The earlier policy listed AKM_NODE_ENTRY, AKM_EVENT_SOURCE, AKM_SESSION_ID,
AKM_AGENT_HARNESS, AKM_EMBED_DETERMINISTIC, AKM_CLAUDE_PROJECTS_DIR, and
AKM_FORCE_INIT_TMP_STASH as implementation variables without compatibility
guarantees. Do not turn them into user-facing configuration promises by relying
on their names alone; inspect their current readers before changing launchers,
attribution, or test fixtures. Their presence here does not assert that every
variable is still read by every release.
AKM_STATE_DIR was also in that list. It is a live 0.10 location override and is
now listed with the other deprecated path overrides in the stability policy, so
an installation using it has an explicit 0.11 migration path.