Lodestar v1.2.5

Lodestar 1.2.5

Tool calls failed when the host spelled a tool name differently than the plugin
expected. This release makes recognition namespace-agnostic.

npm install --global lodestar-agent-context@1.2.5
lodestar start --cwd .

One tool, three spellings

A host may present the same tool as lodestar_work_start,
lodestar__lodestar_work_start, or lodestar/lodestar_work_start. The hook stored
whichever string it received, and execution compared against a reconstructed one. When
those disagreed the call failed with:

Invalid, expired, mismatched, or replayed host attestation

That message describes a security failure, so a naming mismatch looked like tampering.
Both sides now compare the canonical suffix. The token stays bound to its session, turn,
cwd, and arguments — only the spelling stopped mattering.

Verified across every form, for both families:

work_start        lodestar_ / lodestar__ / lodestar/     ok
handoff_status    lodestar_ / lodestar__ / lodestar/     ok

Near misses still miss: notlodestar_work_start, lodestar_work_bogus, and
work_start are not recognized.

Upgrading

Schema unchanged since 1.2.0. Refresh the plugin and restart the host so the running
process loads it:

npm install --global lodestar-agent-context@1.2.5
codex plugin add lodestar@personal

Requires Node.js 24.15.0 or newer.