Skip to content

JAM v1.6.0

Choose a tag to compare

@github-actions github-actions released this 06 Sep 23:32
· 6 commits to main since this release
dbe98c5

JAM 1.6.0 answers to the same lifecycle words as ASC: status, refresh and
uninstall join setup, update and runtime.

What changed

  • jam status. The first place to ask what is going on. It is doctor's
    user-facing role under the name both products use, and it does not
    reimplement the judgement: the same health gate and the same per-axis
    verdicts — credentials, project binding, runtime, registration, live toolset,
    Jira authentication, Jira project access — answer here. jam doctor keeps
    working and names its replacement.
  • jam refresh. Keeps the version and re-registers what this build owns.
    What goes stale in JAM is a registration line, and update is for when a
    newer release exists; refresh is for when the line drifted from the build
    that is already here. Its scope stops there: the project binding,
    ~/.jam/config.yaml, the credentials and every .jira-agent/project.yaml
    are outside it. jam refresh check and jam refresh plan change nothing.
  • jam uninstall. Removes the MCP registrations JAM wrote and the global
    launcher when one is installed. It keeps ~/.jam in full — the project
    bindings, the runtime choice — and the credentials in the OS secret store.
    There is no purge: nothing yet needs a command that destroys those.
  • Help is organised by what a person is doing — Lifecycle, Jira,
    Authentication, agent entry points — with jam serve named for what it is:
    the host's launch command, not something a person types.
  • Nothing is removed before its replacement is verified, in refresh as in
    update, and a registration JAM could not read back is never reported as done.

What did not change

JAM has no execution mode. It is the Jira access layer: no session model, no
approval path, no guard. A Jira write still travels ASC's decision path and
lands through jira_write_plan / jira_write_apply. The two products share a
vocabulary, not a release train — ASC 0.8.0 and JAM 1.6.0 are independent.

Install / Upgrade

jam update

From nothing:

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

Agent setup

The canonical entry is unchanged:

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

Updating an already-configured machine is jam update; making its registration
match the build already here is jam refresh. Neither is setup --agent, which
re-plans the binding and everything else.

Compatibility

  • Node 20 or newer, unchanged — that is what every manifest's engines declares.
    No config or data format change.
  • jam doctor continues to work, printing a deprecation line; jam status is
    the name to use.

Verified

  • CI: build, tests, release checks, packaging, packed smoke.
  • refresh is checked to leave a bare entry alone, to skip a host with no JAM
    entry, to remove before re-registering, and to fail rather than claim success
    when the read-back still shows the old pin.
  • uninstall is checked to touch no path under ~/.jam and to run no removal
    of the person's files.

Known limitations

  • Published acceptance against the 1.6.0 artefact runs after publishing.
  • refresh measures registrations through each host's own CLI; a host whose
    CLI is not on PATH is reported as unavailable rather than assumed empty.