Skip to content
Junior 0.20.0 · concurrent runs share the machine, warm worktrees, and reused lane evidence →
Junior Agent

RELEASE HISTORY

What changed in Junior.

Condensed notes for the releases that shaped the current CLI. The full, authoritative history lives in the project changelog.

Read the full CHANGELOG on GitHub ↗

  1. v0.20.0

    Concurrent runs share the machine safely, worktrees start warm, lane evidence is reused at integration, and the ADR gate and command guards no longer pass by default.

    Added

    • Machine-wide admission control: every worker and check takes a slot shared by all Junior processes on the machine, and nothing starts while memory is low or swap-out is high. machine.pools caps matching commands (for example two dotnet checks at once). Waits show in junior status --live and on the receipt; a run not admitted in time ends admission_timeout (#277).
    • isolationSetup.warmFrom copies build caches (**/obj/ by default) from a pre-built tree into each new worktree, with reflink where supported. It never symlinks or writes into the source tree, and never fails the run (#278).
    • Each check result carries its phase (build, test or other), its duration and a governed evidence identity: the touched projects' tree hash, the command and filter, the lockfile hash and the toolchain. Receipts report build vs test time, warm or cold (#278, #280).
    • junior land applies reviewed lanes to an integration checkout, reports each lane check as reused or stale on the final tree, and runs one compile for the batch (#280).
    • junior status lists ready_for_review runs older than reviewQueue.agingMinutes, with an optional notify hook. junior doctor shows admission slots and memory pressure, and flags repeated cold builds with no warmFrom (#277, #278, #280).
    • Default command guards, on without a commandPolicy: a --no-build test after a failed or missing build is refused, and git hook bypasses (--no-verify, core.hooksPath, HUSKY=0) are refused in checks and the worker's bash. Every decision is recorded as a typed policy event (#281).
    • A budget above the workflow default stops at needs_budget_approval until a human runs junior auth budget approve. That command and junior auth consent grant refuse in an agent shell and ask for a typed-back code on a terminal (#281).
    • junior validate, handoff preflight and junior plan check warn on CHECK_UNFILTERED (a whole test suite when the contract names a few test files) and CONTRACT_OVER_BUDGET, and refuse under jev.mode enforce. A run stopped by output_truncated or budget_exceeded carries a ready continuation contract (#279).
    • junior adr check --stage implementation --whole-change judges each ADR once over the whole diff plus a Relationships section of cross-tool imports and shared modules (#276).

    Fixed

    • The ADR gate always judges the ADRs a change or design is about: cited by id, covered by applies_to, or sharing a file-less design's topic. **/ in applies_to matches zero or more segments (#276).
    • A gate that answers uncertain for nearly every row reports NO_DISCRIMINATION and exits 2 instead of passing (#276).
  2. v0.18.7

    junior init sets up companion calls even with installers off, and the build moves to TypeScript 7.

    Changed

    • The build uses TypeScript 7.0.2, the native compiler (#264). Every module with timing logic uses an injectable clock, and timing tests are deterministic (#265).
    • Every managed tool is verified at its current release: cpm 0.8.0, fmeca 0.2.2, crossmatrix 0.3.4, elicitation 0.1.3, scientific-process 0.3.1 and triz 0.4.1.

    Fixed

    • junior init with JUNIOR_NO_INSTALL writes the project hop (.delivery/setup/hop.json) from the tools already installed, so junior tools call works. junior doctor reports a project with usable tools but no hop as not ready, and junior setup repairs it (#271).
  3. v0.18.6

    Junior verifies the current release of every tool it manages, including cpm-planner 0.8.0 and elicitation 0.1.3.

    Changed

    • junior doctor verifies cpm-planner 0.8.0 (before, only up to 0.4.3) and elicitation 0.1.3. Every managed tool is verified at its current published version: cpm 0.8.0, fmeca 0.2.2, elicitation 0.1.3, scientific-process 0.3.1, and Pi 1.5.2.
    • Elicitation 0.1.3 lists every missing append field in one error and documents complete payloads and the qualify scope. The Junior skill documents the optional <hop.json> argument to junior tools call (#250).

    Fixed

    • A remote Pi run whose transport returns an artifact manifest without a source commit is stamped with the requested commit. Before, it threw ReferenceError: manifestRoot is not defined (#261).
  4. v0.18.5

    An out-of-credit provider is reported as such, ADR subcommands answer --help, and implementation checks find the right base branch.

    Fixed

    • A provider HTTP 402 (out of credit or over the key limit) is reported as workerFailure.category provider_credit_exhausted. It is not retried, and the summary names the remedy. Before, it read as a generic receipt failure (#251).
    • junior adr <command> --help prints that command's usage and exits 0. Before, adr new --help wrote an ADR titled --help (#252).
    • junior adr check --stage implementation without --base diffs against the remote's default branch (origin/HEAD), then origin/main, then origin/master, so dev-only repositories work. When none exists, the error names --base <ref> (#249).
  5. v0.18.4

    ADR folders that mix Junior-format and Nygard/MADR records load every record.

    Fixed

    • adr check, lint, init, scope, sync and ticket checks parse each record by its own format instead of failing on the first file without front matter, and a parse error names the record path. adr lint resolves its configuration the same way adr check does (#245).

Earlier releases

0.18.x 4 releases · 2026-11-15 to 2026-11-15
  1. v0.18.3

    junior adr scope gives the same proposals from run to run.

    Fixed

    • Each candidate path is judged several times (--samples, default 3) and kept only on a majority of confident yes votes. Marginal paths are reported as uncertain instead of appearing and disappearing (#235).
    • Candidates are judged top-down, so a kept parent covers its children, and answers are cached per ADR text in .delivery/adr-scope-cache.json; an edited ADR is re-judged and --fresh ignores the cache (#235).
  2. v0.18.2

    Implementation-stage ADR checks judge the change, not the top of each file.

    Fixed

    • Each changed path is sent as a unified diff against the merge base (or HEAD in a handoff worktree), new files are sent whole, and oversized diffs keep whole hunks. junior adr check --stage implementation accepts --base and --result.
    • Foreign MADR/Nygard ADRs parse real-world Decision headings and dates.
  3. v0.18.1

    ADR scope proposals are valid YAML.

    Fixed

    • junior adr scope writes front-matter strings as YAML double-quoted scalars, and Junior reads them back exactly.
  4. v0.18.0

    Junior works with existing ADR collections: any file naming, drafted scopes for foreign ADRs, and an honest result when nothing was checked.

    Added

    • adr.filePattern selects ADR records and takes the id from its number group, so collections named ADR-001-title.md work. junior adr init proposes the pattern, and adr lint/check report a discovery object (adr check exits 2) when Markdown files match no records (#229).
    • junior adr scope drafts applies_to for accepted MADR/Nygard ADRs without Junior front matter. Proposals go under .delivery/adr-proposals/ for review; the original ADR is never edited (#229).
    • junior adr lint reads MADR/Nygard records through the configured folder and pattern, still reporting duplicate ids and missing Decision rules (#229).
    • An implementation check that judged nothing while accepted ADRs were skipped reports inconclusive and exits 2 instead of looking clean, and points to junior adr scope.
0.17.x 1 release · 2026-11-14 to 2026-11-14
  1. v0.17.0

    Junior checks designs, tickets and code against your architecture decision records, and lets you decide which OpenRouter providers and regions may process your code.

    Added

    • junior adr check runs at four checkpoints: design, ticket proposal, ticket pickup and implementation. Under adr.gate enforce a likely ADR contradiction stops the work until you decide with junior adr decide (override with a reason, amend the ADR, or revise). Decisions go to a committed .junior/adr-decisions.jsonl (#220).
    • Junior's own runs use the same gate: prepare briefs are gated per option, code handoffs before review, and a contract that names a ticket before any worker starts. GitHub and Jira tickets are supported, and ticket text is treated as data (#221).
    • junior init and junior update keep one managed <junior> block in CLAUDE.md and AGENTS.md, so Claude Code, Codex and Cursor run the ADR checkpoints. Nothing outside the block changes (#223).
    • models.dataPolicy controls who may process your requests: data collection, zero data retention, provider allow and deny lists, regions and fallbacks. A policy no provider can satisfy stops before any spend, served providers are checked after the run, and junior doctor --online shows the posture (#218).

    Fixed

    • The compact receipt now carries the notes a run records, so an unverified or skipped check never reads as a clean pass.
0.16.x 2 releases · 2026-11-11 to 2026-11-14
  1. v0.16.1

    Valid Claude Code deny rules for the .crossmatrix store, migrated on upgrade, and contract deadlines that are no longer dropped.

    Fixed

    • The Claude Code .crossmatrix deny rules Junior writes are all valid, and junior init migrates the old spellings without touching your own rules; junior doctor reports them as current, outdated or missing (#214, #217).
    • A top-level deadlineMs is honoured when a contract also has an execution object, junior validate warns about a shadowed field, and the receipt shows the resolved deadline (#219).
  2. v0.16.0

    junior update installs binary tools correctly again.

    Fixed

    • Binary tools are extracted byte for byte, a tool that closes stdin during the health probe no longer crashes Node, and a crashed install no longer strands its lock (#210).
0.15.x 2 releases · 2026-11-10 to 2026-11-10
  1. v0.15.1

    Parallel worktree handoffs keep working on projects without a matrix model.

    Fixed

    • A handoff that names a feature or plan deliverable no longer creates a Crossmatrix model in your checkout, which used to make every following worktree handoff refuse a dirty checkout.
  2. v0.15.0

    Junior runs inside a Codex workspace-write sandbox, is tested on Pi 1.5.2, and junior update keeps every project on the tested Pi.

    Added

    • junior update installs the tested Pi when yours is older, never downgrades a newer Pi, and raises an older pi.testedVersion in delivery.config.json.
    • Pi 1.5.2 is the tested Pi, and Jevitate 0.30.0 is the managed companion version (a run that passes without a job done check now exits 2).
    • commandPolicy.manifest accepts the devbox placement schema (schemaVersion 1): local control-plane commands are refused through a remote wrapper, with the local command to run instead (#202).

    Fixed

    • In a Codex workspace-write sandbox, child processes are captured through files, so git inspection, Pi probes, doctor and handoff events work there; a read-only .git now gets a clear worktree refusal (#201, #203).
    • Pi credential-store failures are reported as credential_lock with the path and the fix, and a ~ in PI_CODING_AGENT_DIR is expanded (#203).
    • junior compact restores the active plan from a snapshot when the planner database is read-only, without writing to it (#200).
    • A plan-leased handoff that stops before its run releases its lease instead of holding it until the TTL.
0.14.x 1 release · 2026-10-31 to 2026-10-31
  1. v0.14.0

    Fast, zero-config feature-to-code lookup with git-anchored staleness, a locked matrix store, and concurrent plan-leased handoffs.

    Added

    • Every junior matrix flag is now an override: the hop, model, sources, plan, result and feature default from the project, or from a matrix block in delivery.config.json (#188).
    • junior matrix refresh keeps the feature-to-code map current in one idempotent pass, and junior apply links applied files to the run's feature (#189).
    • junior matrix features <path> looks up the jobs, journeys, outcomes and deliverables a file serves; handoffs naming a feature get its code-map files as context (#190).
    • Links remember the git commit and blob they were confirmed against; junior matrix stale reports changed, moved, deleted and entity-changed links from git alone (#191).
    • The .crossmatrix/ store is read only through junior matrix or the Crossmatrix MCP: the worker guard, Claude Code deny rules and a doctor check enforce it (#194).
    • Each matrix command uses one Crossmatrix server session (#193), and receipts list newly exported symbols with no production caller (#186).

    Fixed

    • Concurrent plan-leased handoffs on one plan no longer fail with a HOP revision error, and a dead holder's lock is reaped (#184).
    • junior update refreshes existing user-scope Junior skills, matching doctor (#185).
    • junior update authenticates GitHub calls and reports rate limits as skipped; maxToolOutputBytes is documented as a cumulative budget (#187).
0.13.x 3 releases · 2026-10-29 to 2026-10-30
  1. v0.13.2

    junior update works again.

    Fixed

    • junior update no longer fails with "DEFAULT_INSTALL_ROOT is not defined" (#178).
  2. v0.13.1

    Internal restructuring: no source file over 1,000 lines, with unchanged APIs.

    Added

    • Large modules are split into cohesive files behind facades that keep every previous import working, pinned by export tests.
  3. v0.13.0

    Binding command placement, bounded report workflows and reliable sandboxed Pi runs.

    Added

    • commandPolicy makes repository command placement binding for the Pi bash guard, checks and isolation setup (#164).
    • Report workflows have an enforced default budget, and the compact receipt gives typed lines for consent, check timeouts, budgets and Pi failures (#158, #161, #162).

    Fixed

    • Sandboxed Pi runs use a run-local agent directory with 0600 credentials deleted on exit, and Pi failures are classified instead of returning an empty receipt (#153, #155, #165, #167).
    • resumeFrom imports the parent session; plan-backed handoffs no longer refuse their own HOP revision and release the lease when a run never starts (#154, #156, #157, #160, #166).
0.12.x 5 releases · 2026-10-23 to 2026-10-27
  1. v0.12.4

    Validated clarification answers and a corrected CPM HOP startup check.

    Fixed

    • Clarification answers have a documented JSON schema, and malformed or unknown answers fail before any artifacts are written (#147).
    • CPM HOP startup parses state_mode separately from the database path, removing a false path rejection (#148).
  2. v0.12.3

    Sandboxed Pi handoffs now work with read-only home directories without weakening credential-at-rest handling.

    Fixed

    • Sandboxed Pi handoffs keep credential locks and transient agent state in the ignored run-artifact directory while linking, rather than copying, the configured credential file (#129).
  3. v0.12.2

    Doctor distinguishes a usable harness from an EPERM-limited Pi version probe.

    Fixed

    • junior doctor reports a degraded result instead of a hard failure when Pi writes an EPERM error to stderr during its version probe and the execution harness is otherwise ready (#126).
  4. v0.12.1

    Production controls for bounded local and remote execution, plus explicit consent before source context leaves the project.

    Added

    • Remote compute control (#101, #102, #103, #117, #121-#128): Junior now has a bounded local and Hetzner control plane with authenticated Pi transport, safe pool provisioning and scaling, reconciliation, and operator-controlled lifecycle actions.
    • External-context disclosure and consent: before source context can be sent to an external model provider, Junior records the destination, model and bounded file scope and requires explicit run or project consent.
    • Worker runtime budgets and retry lifecycle controls keep execution time, output and repair attempts bounded while preserving inspectable evidence for review.

    Fixed

    • An unclear contract now returns its clarification questions before execution consent is requested; consent still blocks every provider handoff until it is explicitly granted.
  5. v0.12.0

    Acceptance criteria gain stable ids plus the checks and fmeca mitigations they verify, with verified-mitigation proposals and personas as graph nodes.

    Added

    • Acceptance entries in a contract may be objects {id, text, when, checks, mitigates} as well as strings (#81, ADR 0011): id matches ^[A-Za-z0-9:._/-]{1,128}$ and is unique within the contract; checks are 0-based indexes into the contract’s checks array; mitigates are <session_id>/<mitigation_id> links; an entry without an id is reported as AC<n>. validate rejects an invalid or duplicate id and a check index outside the array.
    • junior matrix plan-from-spec / spec-bridge assign each drafted criterion the id <requirement id>/ac<n> (for example req:c1/ac2), assigned once when the draft plan is written; ids are never recomputed from position afterwards (#81, ADR 0011 R2).
    • result.json criterion records carry tier (check_passed|deterministic|judged|none) and, when set, mitigates; a criterion is check_passed only when every check it names ran in this run and exited 0 (#81, ADR 0011 R4).
    • junior plan contracts copies acceptance objects as they are, ids, when, checks and mitigates included, and junior plan check reports DUPLICATE_ACCEPTANCE_ID (warning) when one acceptance id appears twice (#81, ADR 0011).
    • junior fmeca propose-verified <result.json|run id> prints one ready set_mitigation_status request per (criterion, mitigation) pair whose verdict is met at tier check_passed; it never calls fmeca and changes nothing (#81, ADR 0011 R5).
    • Personas are a graph node kind: jevitate-personas:<id> seeds normalise to persona:<id> nodes, and the contract context built from a matrix graph slice collects persona members in evidence.personas (#81).

    Fixed

    • Dimension-qualified seeds that already carry the member prefix (for example jevitate-jobs:job:x) now resolve to the prefixed member id instead of staying an unclassified member (#81).
0.11.x 2 releases · 2026-10-23 to 2026-10-23
  1. v0.11.1

    Junior’s crossmatrix adapter now works against a real crossmatrix model (ADR 0012): every dimension, scale and relation Junior uses is declared by Junior, and crossmatrix stays a standalone tool.

    Changed

    • Deliverable status is a status attribute on the cpm roster (read from plan.status when syncing through the hop) instead of self-edge observations; fmeca members carry criticality, residual_criticality, standing and disposition instead of the always-empty severity, occurrence and detection numbers (#109).

    Fixed

    • junior matrix codemap init no longer fails on a model without Jevitate dimensions: a default feature dimension the model lacks is skipped with a note; a missing dimension named with --feature-dimension is still an error (#108).
    • junior matrix sync --source state writes only to relations it declares between dimensions the model has, so its writes land on a real model. Before, the first write failed with unknown_member and aborted the sync. Failure modes now link to the deliverables and files their refs name (junior-fmeca-cpm, junior-fmeca-code, relation type undermines), and a plan criterion’s mitigates links its deliverable to the failure mode with the mitigation’s status (junior-cpm-fmeca). A failed write is reported in failures (exit code 1) and the sync continues; a stale reference is a note (#109).
    • junior matrix autolink finds a complete deliverable’s run by evidence path, run id (<id>/<stamp>) or the latest .delivery/<id>/<stamp>/result.json, and lists each one it could not link in skipped instead of skipping silently (#110).
  2. v0.11.0

    Local session notes, capture proposals on compaction, and hook installs for Claude Code, Codex and Cursor.

    Added

    • Session notes (#93): junior note add|list|done|promote|dismiss keeps local session notes in .delivery/notes.jsonl, one append-only event per line (add, done, promote, dismiss). The file is locally excluded and never committed. A manager note stays open until done; a capture proposal stays pending until promoted or dismissed.
    • Capture proposals (#93): junior compact --capture reads the PreCompact hook input from stdin and asks the pinned default commodity model (today DeepSeek V4.1 Flash, via OpenRouter) once for open decisions, questions, risks, hypotheses and todos, saving them only as proposals. The budget is a 48000-character transcript tail, 1500 output tokens with model reasoning off, one request with a 30-second timeout and at most 12 proposals. It always exits 0 and writes one record per attempt to .delivery/capture/<timestamp>.json; it never writes FMECA, plan or scientific-process state.
    • Four new junior compact block sections (#93): Pending decisions (needs_answers, needs_choice and needs_model_approval runs with the file to read), Open notes, Open PRs (gh for this repo plus compact.repos from delivery.config.json, with a 3-second timeout and unavailable when gh is missing) and Capture proposals.
    • junior compact --cursor (#93) prints {additional_context} for Cursor.

    Changed

    • junior setup --context-hooks (#93) also installs a Claude Code PreCompact hook running junior compact --capture. With --harness codex|cursor it writes .codex/hooks.json or .cursor/hooks.json with SessionStart and PreCompact hooks, locally excluded when created (Codex needs the hooks trusted in /hooks), instead of printing instructions.
    • Junior is tested with Pi 1.4.0 (was 1.0.4): every Pi option Junior passes is unchanged, a live DeepSeek handoff reports the same receipt fields, and Pi 1.4.0 fixes sessions that broke after an output-limit cut-off, which continuation segments can hit. junior init installs 1.4.0 and doctor compares against it.
    • Junior verifies cpm-planner 0.4.3, elicitation 0.1.2 and scientific-process 0.3.1; their recorded responses are unchanged.
0.10.x 2 releases · 2026-10-23 to 2026-10-23
  1. v0.10.1

    Online model catalog planning, repo-aware plan contracts and compact cleanup.

    Changed

    • junior model list and junior model upgrade plan from the online OpenRouter catalog by default, as junior update does, so both report the same newer same-lineage model. --offline uses Pi’s local catalog; --online is still accepted. model approve and model revoke now reject unknown flags (#74).
    • junior plan contracts and junior plan check --jev honour a deliverable’s metadata.repo through delivery.config.json plan.repos (repo name to checkout): the contract’s cwd is that checkout and the <repo>: prefix is stripped before the scope and registration-file rules, so a deliverable that owns triz:README.md is no longer told not to edit README.md. A repo missing from plan.repos keeps the plan’s checkout. Contracts carry metadata.junior.context and metadata.junior.constraints, and plan-time scoring passes the resolved context to Jev, as the run-time gate does (#94).

    Fixed

    • junior compact no longer lists finished work as in flight: a run whose deliverable is complete in any cpm plan line (archived or complete lines included) and synthetic live-check-* runs are left out (#92).
    • The crossmatrix code roster never includes .crossmatrix/ and skips codemap.exclude globs from delivery.config.json (default: .changeset/, lockfiles and snapshots); members dropped from the roster are deprecated by the server, not deleted (#90).
    • FMECA: the f12 Pi-drift detection mitigation now says the isolation check reports after the run rather than aborting before spend (#91).
    • junior setup --context-hooks records its settings backup (.claude/settings.local.json.<stamp>.bak) in .git/info/exclude, so the backup no longer makes the checkout dirty and blocks worktree handoffs (#95).
    • A plan-leased handoff refused before any worker starts (for example, worktree isolation refused on a dirty checkout) keeps its lease and leaves the deliverable’s status alone instead of marking it failed, so re-running the same contract picks it up again (#96).
  2. v0.10.0

    Isolated worker runs, a scope check, a clarity gate for planned contracts and session restore without a model call.

    Added

    • Run isolation (#75): every run probes pi --help and passes the isolation flags Pi supports (--no-extensions, --no-skills, --no-context-files, --no-prompt-templates, --no-approve, --no-mcp) with --tools read,bash,edit,write. The contract field piContext opts back into ambient resources. The receipt records piIsolation, including whether Pi’s own system message confirms it took effect, and junior doctor names any missing flag. Before this, all 114 recorded worker runs had received 18 unrelated ambient skills.
    • Scope check (#76): a contract’s scope lists owned and incidental paths, and junior plan contracts fills it from the plan. The receipt reports the files changed in and out of scope, and an out-of-scope file appears in the unresolved list. The run status does not change. 22 of 79 recorded plan runs had changed files outside their owned set.
    • A clarity gate for planned contracts (ADR 0009, #85): a contract with an explicit workflow that Jev judges unclear (contract_clear below 0.6) stops at needs_answers before a worker starts. junior handoff <task.json> --answers <file> returns the same contract with the answers as constraints and the workflow unchanged. checkBack: "off" opts out. junior plan check <plan> --jev scores plan contracts with the same readiness check (opt-in, paid).
    • Plan-check lessons (#79): junior plan check reports REGISTRATION_OUTSIDE_SCOPE when a deliverable owns a test file that package.json does not register. Plan contracts default to the general model profile, a 25-minute deadline and a constraint against editing unowned registration files.
    • junior compact [--json] [--max-chars N] (#78) rebuilds a session-start block from saved state with no model call: the active plan, FMECA state, open scientific-process hypotheses and unresolved runs from the last 48 hours. junior setup --context-hooks installs a Claude Code SessionStart hook for compaction and resume, or prints setup steps for Codex and Cursor. A restore-context route points to both.

    Changed

    • The build collects every production module, so a new module ships without a separate list.
    • The Junior skill covers the restore-context route, the clarity gate, junior compact and how to derive sharper hypotheses from a refuted one.

    Fixed

    • Worker runs no longer inherit ambient Pi skills, extensions, context files, prompt templates, project trust or MCP servers (#75).
    • Explicit-workflow plan contracts no longer bypass the clarification gate when Jev judges the contract unclear (#85).
    • Clarification questions quote at most 160 characters of context instead of repeating the whole deliverable in every question.
0.9.x 1 release · 2026-10-22 to 2026-10-22
  1. v0.9.0

    Jev gateways, a LiteLLM provider and clearer clarify receipts.

    Added

    • Jev gateways (ADR 0006, #69): gateway.ts holds one table of gateways (openrouter, typesafe) with key order (environment variable, then Pi auth.json) and model ids. jev.provider (auto, openrouter or typesafe) in the contract or delivery.config.json chooses where Jev calls go; auto uses TypeSafe when TYPESAFE_JEV_API_KEY resolves and OpenRouter otherwise. An OpenRouter key alone is still a complete setup. A provider pinned without its key fails with jev_provider_key_missing instead of switching paid paths. Direct TypeSafe calls go to api.typesafe.ai with the System One wire format and jev-latest; TypeSafe’s Data Processing Agreement is at https://typesafe.ai/legal/data-processing. The run record names the Jev gateway, and key values never appear in errors, receipts or doctor output.
    • Companion tools spawned through junior tools call get OPENROUTER_API_KEY and, when configured, TYPESAFE_JEV_API_KEY from the same resolver; values in the hop env or the process env still win.
    • junior doctor has a gateways section: each gateway’s status and key source, the resolved Jev provider, and the litellm provider in Pi’s models.json (defined, how its key is configured, model count). A !command key is reported, never run.
    • LiteLLM (ADR 0007, #70): point Pi at a LiteLLM proxy with a litellm provider in its models.json and pin provider: "litellm" with a vendor-prefixed model. The commodity-only policy treats litellm like OpenRouter: the vendor prefix decides, frontier vendors are refused, and an unprefixed id is refused as unknown. Jev stays on OpenRouter or TypeSafe.

    Changed

    • A clarify names what to fix (ADR 0005, #68): the readiness call also asks which contract part is least clear, and a contract_clear or blocking_assumptions clarify carries part, a quoted excerpt and at least one question. The compact receipt now shows the clarification batch.
    • junior tools call cpm passes the project’s model as CPM_LLM_MODEL and refuses a frontier or unknown model before cpm-planner starts (#67). cpm-planner 0.4.2 also defaults to a commodity model on its own.
    • A non-OpenRouter run’s billing records why there is no authoritative bill, and a Pi-reported 0 for real token use on such a provider is shown as unpriced rather than free.
    • Recorded responses for cpm 0.4.2 and fmeca 0.2.2 (unchanged shapes); the companion releases adopted are cpm-planner 0.4.2, crossmatrix 0.3.4, fmeca 0.2.2 and triz 0.4.0.
0.8.x 2 releases · 2026-10-20 to 2026-10-20
  1. v0.8.1

    Applied-patch tracking and verified companion responses.

    Added

    • junior apply records the applied patch hash in applied.json, and junior prune removes a worktree whose changes were applied and are unchanged since, instead of skipping it as "unreviewed changes".
    • Recorded responses for cpm 0.4.1, fmeca 0.2.1, elicitation 0.1.1 and scientific-process 0.3.0: junior doctor reports them as verified. Their response shapes are unchanged from the previous versions. The fixture index lists every verified version per tool.

    Changed

    • The companion releases this adopts document junior tools call in their own skills (praxec/cpm-planner#82, scientific-process#11, elicitation#12, fmeca#88, crossmatrix#31), and scientific-process 0.3.0 accepts a per-call session_id (scientific-process#12); Junior’s same-process session opening stays for older servers.
  2. v0.8.0

    A route map, one companion response reader and offline matrix imports.

    Added

    • junior routes [--json] [<query>] and routes.ts: one machine-readable map of manager jobs to Junior routes (delegate, CPM planning, plan shaping, running and tracking plans, FMECA risk, crossmatrix traceability, discover, investigate, TRIZ, browser testing, issue reports, setup, models). A query ranks the routes by trigger match, so an agent can recover the right command after a compaction.
    • companion-shapes.ts: the single reader for cpm, fmeca, elicitation and scientific-process responses. It accepts every known shape (including cpm 0.4.0 graph.deliverables) and raises ShapeError for an unrecognized response instead of reading it as empty. Recorded responses of the installed companion versions live in tools/test-fixtures/companions/, regenerated by node scripts/capture-companion-fixtures.mjs.
    • junior doctor reports an advisory shape:<tool> item per installed companion: verified when this release has recorded that version’s responses, unverified otherwise. It never changes readiness.
    • junior matrix export|sync --source cpm --plan-file <plan.json> and junior matrix bootstrap --plan-file <plan.json> read a plan file offline, with no hop or server.

    Changed

    • The Junior skill leads with a "Choose a route" table and a "Planning with Junior" quick path, and its description names every route’s triggers, so planning, risk and traceability requests load it, not only delegation. skill-routing.test.ts keeps the table in sync with routes.ts.
    • junior init creates the project Crossmatrix store when it is missing (--no-matrix opts out). junior update no longer creates project state unless --with-matrix is passed, reports "command": "update", and stops repeating the junior matrix init reminder.
    • matrix, matrix-autopilot, state-sync, plan-handoff and clarify read companion responses only through companion-shapes.ts.
    • matrix bootstrap expands an owned directory to the tracked files under it and skips owned paths that are not tracked yet, so matrix confirm no longer fails on them.

    Fixed

    • matrix export|sync --source cpm read 0 deliverables from cpm-planner 0.4.0 plan.get, so matrix confirm failed with unknown_member (#58).
    • The Junior skill did not trigger on CPM/FMECA planning requests and buried the planning loop (#59). (tools call stdin and inline forms already shipped in 0.7.0; the skill now shows them up front.)
    • junior tools call with scientific-process failed with no session open for every method but session.open, because each call starts a new server. The session is now opened in the same process first.
    • A handoff that stopped at needs_model_approval marked its plan deliverable failed; it now keeps the lease like needs_answers and needs_choice.
0.7.x 1 release · 2026-10-19 to 2026-10-19
  1. v0.7.0

    Apply reviewed work in one command, plan-aware handoffs, inline tool calls and a doctor that names a stale skill.

    Added

    • junior apply <id|result.json> applies a reviewed handoff’s worktree changes, new files included, to your checkout with a three-way merge. It refuses a run that is not ready for review or whose base has moved, and leaves your tree unchanged on conflict; --dry-run checks first.
    • Plan-aware handoffs: a contract with plan: {id, deliverable} leases that CPM deliverable before the worker starts and records its hours and evidence afterwards. Repairs and clarify re-runs re-enter the same lease; the manager still reviews and marks it complete.
    • Inline tool calls: junior tools call cpm plan.status plan_id=… runs against the project hop without a request file; values are JSON when they parse.

    Changed

    • junior tools call prints only the tool result (revision and snapshot on stderr) and exits 1 on a tool failure; --full prints the full envelope.
    • junior init refreshes an unmodified outdated Junior skill without --upgrade; a customized copy is still kept unless --force.

    Fixed

    • junior doctor names an outdated, customized or missing Junior skill and the affected managers in its warnings and remediation, and the startup notice lists an outdated skill.
    • Companion skill installs pass scientific-process and elicitation only the targets and project flag they accept, so junior update installs their skills.
0.6.x 1 release · 2026-10-19 to 2026-10-19
  1. v0.6.0

    Commodity-only model policy, a routed roster, Junior-ready planning and runtime robustness.

    Added

    • Commodity-only executor policy: Junior runs only on a recognized commodity or open-weight vendor (DeepSeek, Moonshot, Z.ai, Qwen, MiniMax, Meta Llama, plus openai/gpt-oss) and refuses a frontier or unknown model before any spend. Jev is a classifier only.
    • Commodity roster and routing: built-in profiles general (default, DeepSeek V4.1 Flash), deep-reasoning, long-horizon, agentic-tools and fast-mechanical, with models.routing (off, shadow or auto), models.roster overrides and models.autoUpgrade.
    • Model visibility: a junior doctor model section, the cached startup update check listing newer models, and the junior model status, list and upgrade commands.
    • Junior-ready planning: junior plan check and junior plan contracts shape a cpm plan into bounded handoffs designed for the default model (NEEDS_MODEL_APPROVAL flags anything that would need a pricier one); plan-from-spec emits metadata.junior.
    • Human consent before any non-default model: Jev routing and a contract-named model stop at needs_model_approval with a rationale (pick, confidence, strengths, price against the default); approve per run (--approve-model), per plan (approvedProfiles) or per project (junior model approve).
    • Price parity: a newer version is adopted only when its price, measured on the cheapest tool-capable endpoint, is within models.priceTolerance (default 1.25x); pricier versions are listed as waiting for price parity.
    • Cache visibility and stickiness: receipts show the prompt-cache hit rate and upstream providers; a deliverable keeps one model and one OpenRouter provider across segments, repairs and re-dispatches.

    Changed

    • Jev recommends one model profile when a contract names no model; the default (cheapest DeepSeek) stays unless a human approves the recommendation.
    • junior update adopts newer same-lineage commodity models only when models.autoUpgrade is true and the new version is price-comparable; otherwise it reports them.

    Fixed

    • The output cap keeps whole lines and reports an outputBreakdown.
    • A final per-message output-limit stop continues in a fresh segment, and a recovered transient error no longer fails a run.
    • Analysis workflows judge acceptance with a report outline and excerpt.
0.5.x 2 releases · 2026-10-16 to 2026-10-16
  1. v0.5.1

    Update-notice refresh and cleaner setup exclusions.

    Fixed

    • junior update refreshes the cached update summary after adopting newer releases.
    • junior setup records the companion skill files it creates in the repository-local .git/info/exclude.
  2. v0.5.0

    Harness readiness, Jev tool routing, Crossmatrix autopilot and clarification workflows.

    Added

    • Harness detection for Claude Code, Cursor and Codex; a per-harness readiness object in junior doctor; junior setup previews and confirms its repair plan.
    • A cached 24-hour startup update notice covering Junior, managed tools and companions; Jev tool routing with deterministic playbooks and a toolPlan.
    • Crossmatrix state mirror, autopilot links, context graph and impact analysis, link QC, decision analysis, ADR governance, jobs-to-be-done bridging and plan-from-spec.
    • Prepare workflow and check-back, the clarification loop, discover and investigate analysis workflows, and the managed scientific-process and elicitation tools.
0.4.x 1 release · 2026-10-16 to 2026-10-16
  1. v0.4.0

    Companion-skill readiness, output bounds and worktree guards.

    Added

    • junior doctor reports companion agent-skill readiness as companionSkills without gating ok.
    • The Pi guard extension caps bash-tool timeouts and makes each call read stdin from /dev/null; a timed-out tool is named in the receipt.
    • execution.maxOutputBytes bounds retained worker output, and execution.continuations starts a fresh-session continuation segment.
    • junior validate warns when a contract names more than six context paths or ten acceptance criteria.

    Fixed

    • Local git excludes are verified with git check-ignore.
    • isolationSetup provisioning is idempotent in a resumed worktree.
0.3.x 3 releases · 2026-10-12 to 2026-10-12
  1. v0.3.2

    Tool provenance and read classification fixes.

    Fixed

    • junior tools init no longer records stale tool provenance.
    • FMECA vet is classified as a read, like cpm plan.review.
  2. v0.3.1

    Self-update ordering and Windows fixes.

    Added

    • junior update updates Junior itself from npm first, then re-runs as the new version to update every managed binary, companion and skill.
    • junior doctor --check-updates reports Junior’s own version.

    Fixed

    • The managed TRIZ install keeps the release’s package name and version.
    • npm and npm-installed companion CLIs shim correctly on Windows.
  3. v0.3.0

    The Crossmatrix hub.

    Added

    • junior matrix export and sync turn code, tests, jevitate jobs, CPM deliverables and FMECA failure modes into a committed .crossmatrix/ store.
    • The code map: matrix codemap, link, files, context and stale.
    • Crossmatrix ships as an npm companion with its agent skills.
0.2.x 2 releases · 2026-10-12 to 2026-10-12
  1. v0.2.1

    Output-cap and install fixes.

    Fixed

    • The worker stops as soon as its output reaches the accumulation cap.
    • An already-current companion or managed release is not re-downloaded.
  2. v0.2.0

    Companion tools, auth, MCP, streaming and contract context.

    Added

    • Companion tools FMECA, CPM Planner, jevitate and TRIZ, installed with their agent skills.
    • junior update and junior doctor --check-updates; junior auth set and remove; junior mcp register; junior report-issue; junior doctor --online.
    • Streaming handoff progress and junior status --live.
    • Contract code context, conditional acceptance criteria and the checkReserveMs setting.
    • isolationSetup worktree provisioning and frontier-attention fields in the compact handoff.

Looking for an older release? See the full changelog.