Repository navigation
JAM v1.4.4
JAM 1.4.4 makes project setup deterministic when a machine carries old
settings, and stops "mixed" credentials from reading as a fault. Two field
reports drove it: an operator had to hand-edit ~/.jam/projects.yaml before
--project would take effect, and a working credential split across the OS
store and one exported token was investigated as if it were broken.
What changed
-
--project <KEY>decides the run. It already beat a personal binding,
JAM_PROJECT_KEYand a legacy preset entry; that is now pinned by tests,
and a stale binding is repaired through the ordinary replace plan. Nothing
has to be deleted by hand first. -
The repository's committed key is never overwritten silently. It used
to win over--projectwhile being reported asexplicit, so the flag
looked honoured when a different key was in use. A disagreement now stops:{ "status": "user_action_required", "code": "JAM_PROJECT_KEY_CONFLICT", "requested": { "key": "PROJECT", "source": "explicit" }, "existing": { "key": "OTHER", "source": "repository" } }No change is applied over a conflict, in any entry point. Which Jira
project a repository belongs to is the team's decision. -
Key provenance is reported. Sources are
explicit,repository,
env,bindingorpreset, and a plan carriesproject.keySource. -
Credential sources, per field.
describe()andauth status --json
carry asourcesmap naming which source suppliedJIRA_BASE_URL,
JIRA_EMAILandJIRA_API_TOKEN. Names only — no value is ever printed. -
doctor --jsongains a per-axisdiagnosis:credentials,
projectBinding,runtime,registration,liveToolset,
jiraAuthentication,jiraProjectAccess. A failure is attributed instead
of guessed at, andmixedis aWARNINGon the credentials axis — never a
failure on its own. Whether Jira accepts the credentials stays on its own
axis.
Install / Upgrade
npx --yes @jam-mcp/bootstrap@1.4.4 initOptional persistent command:
npm install -g @jam-mcp/launcher@1.4.4Existing users: re-run setup. Bindings, runtime selection, host registration
and credentials are untouched — a stale binding is repaired in place.
Agent setup
The canonical entry is unchanged; --project is what became reliable:
npx --yes @jam-mcp/bootstrap@1.4.4 setup --agent --project PROJECTCompatibility
- Node 20 or newer, unchanged. The five-tool MCP surface is unchanged.
- Additive JSON:
project.keySource,requested/existingon a conflict,
sourceson credential descriptions,diagnosison doctor. - One new stop:
JAM_PROJECT_KEY_CONFLICT. It fires only where a run
previously used a different key than the flag asked for.
Verified
- server 475 + launcher 39 tests, typecheck, build,
release:check, pack and
tarball smoke — green locally on Windows and on CI (Ubuntu/Windows ×
Node 20/22). - Live matrix against the published artefact: stale binding replaced
OLDKEY→ the requested key; a disagreeing repository key stopped with
JAM_PROJECT_KEY_CONFLICTand zero changes; an agreeing repository key
reportedkeySource: repository. - Real project acceptance:
setup --agent --project <KEY>reachedready
with all seven diagnosis axes OK, including a live Jira read, and no
credential value in any output. - A mixed credential (store plus one exported token) reported
WARNINGwith
its per-field sources while the overall status stayedready.
Known limitations
- A repository conflict is deliberately not auto-resolvable: JAM reports both
sides and stops, and someone has to decide with the team.