JAM v1.4.2

JAM 1.4.2 stops treating a healthy persistent installation as a defect. A bare
jam serve registration is now judged by measuring the executable it actually
runs, and setup's repair respects a persistent install instead of rewriting it
back to an npx pin.

What changed

• Bare-registration judgement — a jam serve entry carries no version in
  the host's listing, so JAM asks the executable (jam runtime status --json)
  and compares that. Previously a bare entry was permanently misjudged stale.
• Persistent-respecting repair — when the measured global launcher is
  exactly this release, repair registers bare jam serve; otherwise it keeps
  the npx pin fallback. Repair no longer recreates the npx cache structure on
  a machine that deliberately installed the launcher.

Install / Upgrade

npx --yes @jam-mcp/bootstrap@1.4.2 init

Existing users: re-run setup once; a mis-judged bare registration is repaired
in place. Bindings, runtime selection and credentials are untouched.

Agent setup

No change to the canonical entry:

npx --yes @jam-mcp/bootstrap@1.4.2 setup --agent

Compatibility

• Node 20 or newer, unchanged. The five-tool MCP surface is unchanged.

Verified

• release:verify green on Ubuntu and Windows against Node 20 and 22 (CI),
  including new regression tests for the bare-entry judgement.
• Published via the Trusted Publishing workflow; registry verification and the
  published smoke ran inside it.

Known limitations

• On a machine where jam resolves only through a package runner's ephemeral
  PATH, the persistent judgement could still be misled — fixed in 1.4.3.
• This body was restored after the fact (2026-08-31) from the recorded
  procedure and commit history; it claims no verification beyond those records.