@ngockhoale/ukit 3.4.79 → 3.4.81

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,21 @@
2
2
 
3
3
  All notable changes to UKit are documented here.
4
4
 
5
+ ## 3.4.81 - 2026-11-08
6
+
7
+ - New: **automatic Claude Code session discovery for UKit Advisor.** `ukit:advisor` / `$ukit-advisor` with nothing after the trigger (or only a short remark such as "lỗi rồi") reads the latest main-agent Claude Code session of the current project — no paste needed; `session <id>` and `project <path>` name one explicitly; anything else is still pasted output, as in 3.4.80. A bundled read-only Node reader (`scripts/claude-session-reader.mjs` inside the skill, also `ukit advisor context [--last|--session <id>|--project <path>] [--json]`) matches the project by the session's recorded cwd (realpath, git root, linked worktrees; nested repos and sibling folders excluded), honours `CLAUDE_CONFIG_DIR`, skips subagent/sidechain transcripts and symlinks, refuses to guess between concurrent sessions, streams huge/partial/concurrently-written JSONL with bounded secret redaction, and renders a bounded, redacted, untrusted digest that keeps owner messages, tool results, assistant claims and Stop-hook/gate refusals apart (owner STOP ≠ hook refusal). It never writes, spawns, resumes or messages Claude Code; no session, no permission or a Codex model that cannot run shell commands yields one safe status-request prompt.
8
+ - Tests: 41 session-reader tests on synthetic transcripts with an isolated `CLAUDE_CONFIG_DIR`; the repo-only live runner `scripts/dev/advisor-live-eval.mjs` gains `--mode=auto` and counts only real `command_execution` events as a reader run; two load-sensitive hook tests get timing headroom (assertions unchanged).
9
+ - Release note: 3.4.80 was tagged and GitHub-released but never published to npm; 3.4.81 is the first npm release carrying UKit Advisor (both the paste mode and session discovery).
10
+ - Packaging: the 2.3.0–2.4.3 changelog entries moved verbatim to `docs/archive/CHANGELOG-2.3.0-2.4.3.md` (repository only); size limits unchanged.
11
+
12
+ ## 3.4.80 - 2026-11-08
13
+
14
+ - New: **UKit Advisor for Codex.** Paste Claude Code output (status, errors, stalled transcripts, STOP/gate/release messages — VN/EN/mixed) into Codex after `$ukit-advisor` or `ukit:advisor` and get back exactly ONE copy-ready Vietnamese prompt for Claude Code (PROMPT ONLY: no analysis section, no code fence, no alternatives). The advisor is read-only, treats the paste as untrusted data, never lifts an owner STOP, never forges ownership/receipts, never starts duplicate jobs, keeps release states distinct (never republishes a verified npm version) and redacts secrets.
15
+ - Surfaces: `$ukit-advisor` is a native Codex skill seeded into `~/.agents/skills/ukit-advisor` (`allow_implicit_invocation: false`). `ukit:advisor` is instruction-routed — a marker-delimited block in the active global Codex instructions file (`$CODEX_HOME/AGENTS.override.md` when present, else `AGENTS.md`) points the prefix at the same SKILL.md; it is not a native Codex command.
16
+ - Lifecycle: installed/refreshed by `ukit install` when the Codex adapter is selected, and by `ukit update` (with `--no-install` or outside a UKit project it only refreshes an advisor UKit already installed); idempotent; ownership via `.ukit-managed.json` hashes, so an unrelated same-name skill is never overwritten and user-edited files are kept; the user's AGENTS.md bytes, BOM and line endings are preserved; a damaged BEGIN/END marker pair or a symlinked AGENTS.md is reported and never rewritten. New `ukit advisor status|install|uninstall [--dry-run]`; opt out with `UKIT_CODEX_ADVISOR=0`.
17
+ - Tests: lifecycle/ownership/cross-platform unit tests, a deterministic PROMPT-ONLY contract checker with 13 eval fixtures, test isolation now pins `CODEX_HOME`, and a repo-only live runner `scripts/dev/advisor-live-eval.mjs`.
18
+ - Packaging: the 3.0.0–3.3.3 changelog entries moved verbatim to `docs/archive/CHANGELOG-3.0.0-3.3.3.md` (repository only); size limits unchanged.
19
+
5
20
  ## 3.4.79 - 2026-11-07
6
21
 
7
22
  - P0 handoff queue lifecycle: one read-only classifier (`classifyQueuedBlueprints`) now decides which `docs/AI_HANDOFF/queued/` blueprints still count as unfinished work. `QueueIntent: superseded|stale` + `QueueSupersededBy: archive:cycle-NN[, …] | queue:<slug>` excludes a blueprint only when the provenance is proven (every package task archived in an 8-column cycle snapshot as delivered/grounded-cancelled, or a live non-cyclic replacement inside the project); self-references, cycles, paths, symlink escapes, partial archives and malformed headers fail closed with diagnostics. Legacy blueprints and `deliberate-future` keep their behaviour; the array API stays compatible. A frozen `ScopeQueue` naming a superseded blueprint warns instead of consuming it silently; a sibling `queue/` directory is reported, never migrated. A `queue:<slug>` replacement that is `deliberate-future` backlog cannot carry the obligation (fails closed). New read-only `resumable-run.mjs queue-status`.
@@ -797,212 +812,6 @@ full playbook backlog and the queued orchestrator blueprint:
797
812
  Note: `npm pack` budgets raised once for the wave (packed 3.03MB, unpacked
798
813
  9.88MB — attributed in `tests/integration/packageArtifact.test.js`).
799
814
 
800
- ## 3.3.3 - 2026-09-27
801
-
802
- Republish of 3.3.2 — npm staged-version E409 limbo (same content, version bump only).
803
-
804
- ## 3.3.2 - 2026-09-27
805
-
806
- **Agent VM driver + self-improve code lane.** CLI (list/show/status/shadow-run/evidence), driver producing promotion evidence into , self-improve step (one shadow run per reference plan per pass), and step (AUTO-<id>.md handoff task files mined from recurring failure patterns — whitelist fix classes, denylist protected lanes, ≤3/pass, never commits code). See docs/plans/AGENT_VM_DRIVER_PLAN.md + SELF_IMPROVE_CODE_LANE.md.
807
-
808
-
809
- ## Unreleased
810
- - **Self-improve `codeProposals` step — the code lane (SELF_IMPROVE_CODE_LANE plan).** After telemetry, each rate-limited pass turns mined, recurring failure patterns into **AUTO handoff task files** (`docs/AI_HANDOFF/tasks/AUTO-<seq>.md`) on the standard `_TEMPLATE.md` skeleton — frozen pattern evidence, `ready`/`S`, executor + reviewer + tests stay the quality gate. Whitelist fix classes only (timeout/hang, missing-fallback, empty-output, stale-doc); denylist targets (`src/decision/`, `src/core/agentRuntime/`, runtimeConfig, auth/security code) are skipped, never proposed; ≤3 AUTO tasks per pass; signatures already carried by `tasks/` or `archive/` files dedupe to `duplicate`. `learning.selfImprove.codeProposals` (default `true`) gates the step; `learning.selfImprove.codeProposalsCommit` is hard-false — writing a task file is the ceiling, self-improve never writes code or commits. `ukit self-improve --proposals` prints the proposal list; `--dry-run` lists would-be AUTO tasks without writing.
811
- - **`ukit vm` driver surface + shadow-run + evidence (agent-VM driver D-01..D-03).** New `src/cli/commands/vm.js` exposes `list`/`show <planId>`/`status`/`shadow-run <planId>`/`evidence <key>` over the plan library; all subcommands refuse `stage_off` (exit 2, zero writes) when `decisionRuntime.vm` is `'off'`. New `src/core/agentRuntime/shadowRun.js` `runShadowPlan(planId, {projectRoot, config, plansDir?, engineDir?, evidence?})` replays a pinned plan through a real `createVmEngine` rooted at `.ukit/storage/agent-runtime/shadow/<planId>/` with a stub `startFn` — deterministic synthetic events (RUN/WAIT_EVENT → `operation.completed`, BRANCH → first declared choice) until terminal, never throws, returns `{transitions, nodeStates, wallMs, irHash, planVersion}`. Each run appends one record to `evidence/vm.jsonl` (256 KiB rotation; `qualityDelta`/`wallP95Ratio`/`costRatio` stay `null` so shadow evidence can never self-promote); `ukit vm evidence vm` prints the `promote()` verdict verbatim without writing config.
812
-
813
- - **Self-improve `vmShadow` step (agent-VM driver D-04).** After diagnostics, each rate-limited `runSelfImprove` pass now runs one shadow-run per `planLibrary` reference plan via `agentRuntime/shadowRun.js` when `decisionRuntime.vm.stage` is `'shadow'` or higher — the first live-path caller that accumulates evidence for `PROMOTION_CRITERIA`. `off` → step `skipped` (`stage_off`), zero writes under `.ukit/storage/agent-runtime/`; driver missing, refusing, or throwing → step status `error`, the pass never throws and later steps still run.
814
-
815
- - **`ukit vm run` — evidence-gated live lane (BL-031).** `src/cli/commands/vm.js` gains `run <planId>`: a real `VmEngine`+`createSupervisor` path (`runLivePlan` in `src/core/agentRuntime/shadowRun.js`) that launches RUN-node specs declaring the supervisor contract (`spec.command`/`spec.argv` — descriptive `spec.cmd` prose is never shelled out, it fails typed), relays supervised terminal outcomes into the engine, and appends one `lane:'live'` evidence record. Stage gate: `off` → `stage_off` refuse (zero writes); `shadow` → `live_stage_required` refuse — execution requires `canary`/`default`. BL-031 promotion bar is recorded verbatim (`REPLAY_PROMOTION_BAR`: promote only if the VM catches ≥1 defect the doc pipeline missed OR cuts cycle time ≥25% at equal verdicts); `buildReplayComparison`/`recordReplayComparison` write a `replay-comparison` record to the evidence store and `ukit vm evidence` prints its verdict verbatim — `promote()` stays the only stage-advance mechanism.
816
-
817
- ## 3.3.1 - 2026-09-27
818
-
819
- - **Republish of 3.3.0, content-identical.** npm staged 3.3.0 then returned E409 "previously staged version" on retry — same staged-limbo pattern as 3.0.11→3.0.12. Version bump only; parity verified below.
820
-
821
- ## 3.3.0 - 2026-09-27
822
-
823
- **Zero-config self-improvement: every feature stage ships on, UKit collects and learns from its own data.** Fixes the gap where 2.6.8–3.2.0 built the machinery (flight recorder, memory v2, learning, decision plane) but nothing on the live hook path fed it — measured 1 telemetry record and 0 memory-v2 records after days of use.
824
-
825
- - **`ukit self-improve` — the automatic collect → learn → apply pass** (`src/learning/selfImprove.js`, `src/cli/commands/selfImprove.js`). One bounded, rate-limited (10 min), lock-guarded pass that runs after every session: (1) backfills an episode for every idle exec-ledger — engine-agnostic, fixes omp session-id mismatch and Codex having no lifecycle hooks; (2) refreshes diagnostics (failure patterns, feedback, skill accuracy); (3) computes tuning suggestions and **auto-applies** them under `learning.tuning.applyMode: 'auto'` (new default) as clamped one-step moves into `.ukit/storage/learning/tuned.json` with a 24h per-key cooldown; (4) writes repeated failure patterns as pending pattern candidates (promotion still needs `ukit memory approve`); (5) ingests stored hook/ledger telemetry, flushes, refreshes the support view. Never throws; each step isolated.
826
- - **`self-improve-trigger.mjs`** (`template_project/.claude/ukit/runtime/`): fire-and-forget launcher called from Claude `SessionEnd`/`session-episode.sh`, omp `session_stop` via the bridge, and Codex `route-task.mjs` (its only per-task entry). Detached child, returns in ms, silent no-op on any failure; opt out via `learning.selfImprove.enabled: false` or `UKIT_SELF_IMPROVE=0`.
827
- - **CLI locator** (`.ukit/storage/cli.json`, `writeCliLocator` in `metadata.js`, written by `ukit install`): absolute node + bin paths so hooks spawning the CLI work on GUI-launched hosts whose PATH lacks nvm/volta. `resolveCliLocator` validates node basename, `bin/ukit` shape and `@ngockhoale/ukit` package identity before trusting it; PATH lookup stays the fallback.
828
- - **All stage flags default on**: `routing.*` → `default`; `memoryV2.decision` → `default`; `learning.candidates`/`overlays` → `default`; `continuity.resumableRun` → `default`; `decisionRuntime.*` → `shadow` (diagnostics → `default`); `experiments.deliberation`/`dynamicWorkflow` → enabled; `observability.stage` added to code defaults (`default`). `learning.tuning.applyMode` accepts `'auto'`; tuned overlay merges via `inspectRuntimeConfig`. Rollback: per-key `stage: "off"`, `applyMode: 'manual'`, or delete `tuned.json`.
829
- - **`ukit memory episode` refactored** onto shared `src/core/memory/episodes.js` (`resolveLedger`, `episodeText`, `writeEpisode`, `backfillEpisodes`) — one owner for the record shape between the single-session command and the self-improve backfill.
830
- - Tests: 28 new (tunedOverlay clamp/merge/cooldown, episodes resolve/write/backfill dedupe, trigger locator validation + spawn contract); stale stage-default pins updated to the 3.3.0 contract.
831
-
832
-
833
-
834
- ## 3.2.0 - 2026-09-26
835
-
836
- **Agent VM / Language-Compiled Runtime phase 2 (V-01..V-06)** — IR v2 flag-gated opcodes, decisionRuntime.vm stage-promotion machinery, plan library pins, VM decision nodes via unic-decision, host parity adapters, sanitized support bundle. All new surfaces ship `off`.
837
-
838
- - **Host lane adapters for the owned runner (agent-vm-runtime V2).** `adapters.js` gains the frozen `HOST_ADAPTERS` registry plus `detectHost` (env-marker best-effort ambient engine resolution, ambiguous → `null`) and `probeHostAdapter` — honest per-host capability statuses `supported` / `unsupported-probe` / `unsupported` with typed reasons (`unknown_host`, `process_group_kill_unavailable`, `host_spawn_unavailable`, `live_host_e2e_unproven`); `supported` is reachable only via explicit `liveHostE2E` evidence, never inferred from primitive presence (G-V2). `buildHostCapabilityMap` in `runtimeSupport.js` exposes the map per lane; every lane reports `completionApi: 'eventStore-journal'` — no engine exposes a host-owned durable completion API. `createSupervisor` accepts `opts.host` and per-launch `spec.host` (precedence spec → opts → ambient detect → no lane); a lane probed `unsupported` refuses `start()` typed (`host_unknown`/`host_unsupported`, zero fs writes) while `unsupported-probe` lanes still run the identical spawn → journal → terminal contract. Live-E2E gap for claude-code/codex is documented in the task file — never claimed as supported.
839
- - **Agent VM V-01 — IR v2 flag gate + versioned IR contract.** IR v2 ops (`PARALLEL`, `TIMEOUT`) now parse only behind an explicit opt-in — `ir.planVersion: 'v2'` on the artifact, `opts.irVersion: 'v2'` on `compilePlan`, a caller `allowedOps` list naming them, or a non-`off` `decisionRuntime.vm` stage forwarded by `planLibrary.loadPlan({config})`. Ungated v2 IR fails with `ir_v2_disabled`; unknown version literals fail `invalid_ir_version`. `contract.js` exports `IR_VERSIONS` (`['v1','v2']`) and `ValidatedPlan` carries `irVersion` derived from ops actually used — v1 plans compile byte-identical under every flag state (planVersion unchanged). RETRY lands as the bounded per-node `retry` policy (side-effect-class aware: non-auto-retryable classes can never claim `maxAttempts > 1`; a crashed non-idempotent node stays `recovery_required` and is never re-run blind). New fault coverage: TIMEOUT firing mid-node on deliver → deterministic `escalate` replay-identically; duplicate delivery at the join is idempotent across a crash (single `completed` fold in the wrapper journal); bounded fan-out honors `maxNodes`.
840
-
841
- - **V4 plan library: release pinning + spec text.** `planLibrary.loadPlan` now returns `specText` (the human-authored spec each plan was compiled from) and `planVersion`, and enforces `PLAN_PINS` — a shipped plan whose compiled hash drifts from its pin fails with `plan_version_mismatch` instead of silently running a different workflow. Fourth reference plan `flag-promotion` (stage-promotion gate: baseline replay → shadow runs → promote/rollback branch, mirroring `promotion.js`) joins `bugfix-loop`, `handoff-review-batch`, `release-check`. Coverage: artifact-hash stability, vmEngine replay determinism per plan, malformed-artifact rejection, pin drift.
842
- - **VM decision nodes via `unic-decision` (agent-vm-runtime V5).** `vmEngine` nodes may now carry a bounded `question` block (`{decisionKey?, instruction?, candidates?}`, validated by `validateNodeQuestion` in `contract.js` and carried through `planCompiler`). When `decisionRuntime.vm.stage` is promoted past `off` and no `classifyFn` is injected, unclassifiable events are routed by `createVmClassifyFn` (`src/decision/runtimeDecide.js`) through one bounded `runtime.node_route.v1` / `runtime.node_classify.v1` question — the only two keys a node may ask (registered `rolloutStage: 'off'`, owner `vmEngine`, deterministic escalate fallback). Model answers are data only (`tool_calls` never dispatched); `model_not_found`/timeout/invalid/adapter faults all resolve to the deterministic escalation lane with a `fallbackCode`, never a hard failure — a throwing `classifyFn` now escalates too. Stage `off` (default, absent, or malformed) installs no adapter: zero decision calls, byte-identical behaviour.
843
-
844
- - **Agent VM V-06 — per-run support bundle** (`src/core/agentRuntime/diagnostics.js` `exportSupportBundle`, `eventStore.js` `readJournalExcerpt` + `summarizeEvent`, `telemetry.js` `buildTraceExcerpt`, `ukit telemetry export-run <operationId>`): one sanitized bundle per operation lands in the Data Foundation support layout — `Documents/UKit Support/proj-<sha256>/run-<sha256>/` with `journal.jsonl` (bounded code summaries only), `trace.jsonl` (double-gated span excerpt, deterministic pseudonyms), `SUMMARY.md` and a `ukit-support/1` manifest with sha256 checksums, importable via `ukit telemetry import`. Privacy: redaction before persist — secret/path/PII rules + `sanitizeForSupport` on trace records + a final assembled-bytes re-scan that blocks all writes on any residual secret; no raw prompt/diff/path content can appear. `decisionRuntime.diagnostics.stage: 'off'` → `skipped` with zero writes. Missing/corrupt journals still emit bundles with declared `gap` markers; a 256 KiB cap drops excerpt lines deterministically (`coverage.dropped_lines`).
845
-
846
- ## 3.1.9 - 2026-09-26
847
-
848
- - **Checkpoint locked to `unic-decision` for all classes.** Owner decision: the single `unic-decision` model answers every decision (English, multilingual, unknown) — the provider swaps the backend (Lava/JEV) behind that name, so UKit no longer routes per-language. `checkpoints.{default,english,unknownLanguage}` all resolve to `unic-decision` in code + shipped config; `unic-decision-multilingual` removed from defaults (remains configurable via `decisionPlane.checkpoints` if ever needed). Endpoint config unchanged: `ukit decision` / `gatewayDecision.json` / `UKIT_DECISION_*` env.
849
-
850
- - **Agent VM V-03 — stage-promotion machinery** (`src/core/agentRuntime/promotion.js`, `src/core/runtimeConfig.js`): new `resolveDecisionRuntimeStage(config, key)` resolves `decisionRuntime.<key>.stage` with `decisionPlane` semantics (absent/malformed → `off`); new pure `promote(config, evidence)` advances one family flag `off → shadow → canary → default` only when the frozen `PROMOTION_CRITERIA` hold on ≥ `minSampledRuns` sampled runs (quality delta ≥ `-QUALITY_SCORE_FLOOR`, wall-p95 and cost ratios ≤ baseline), and instant rollback (`evidence.rollback` or any forbidden failure) resolves `off` — deterministic owners authoritative, zero VM calls. `off` never self-promotes and one noisy run never flips a default. All `decisionRuntime.*` stages stay `off`: machinery only, no rollout flip.
851
-
852
- ## 3.1.8 - 2026-09-26
853
-
854
- - **Agent VM IR v2**: `PARALLEL` (bounded fan-out, `join:'all'`) and `TIMEOUT` (deadline wrapper, `onTimeout: fail|escalate`, 30-minute ceiling) opcodes added to `planCompiler` + `vmEngine`; fault-injection coverage for crash-between-fan-out-and-join, non-idempotent child recovery, duplicate delivery. v2 plans hash under a `v2:`-prefixed serialization; v1 hashes unchanged.
855
- - **Install seeds `.ukit/storage/observability/`** — the segment writer's safe `resolveRoot` rejects a missing parent, so the first emit on a fresh install previously failed with ENOENT. `ukit install` now creates the directory (advisory, never fails).
856
-
857
- ## 3.1.7 - 2026-09-26
858
-
859
- - **Observability + memory recording enabled by default on install.** Shipped `config.json` now sets `observability.stage: 'default'` (recorder + analytics + projector + evaluation — the full Data Foundation pipeline) and `learning.episodes.autoWrite: true` + `learning.candidates.stage: 'shadow'` (ukit-memory records evidence without auto-applying anything). Privacy gates (`sanitizeObserved`, `sanitizeForSupport` default-deny) are unchanged. Code defaults in `runtimeConfig.js` updated to match. New: `planLibrary.js` + 3 versioned reference plans (`bugfix-loop`, `handoff-review-batch`, `release-check`) as the V4 artifact seed for the Agent VM phase-2 plan.
860
-
861
- ## 3.1.6 - 2026-09-26
862
-
863
- - **Decision endpoint URL normalization**: a `UKIT_DECISION_BASE_URL` that already ends in `/v1` (OpenAI convention) no longer produces `…/v1/v1/chat/completions`; the client strips a trailing `/v1` before joining. Applied to `src/decision/client.js` and mirrored in `unic-decision.mjs`.
864
-
865
- ## 3.1.5 - 2026-09-26
866
-
867
- - **Install/update warns when the decision lane has no API key.** After a project refresh, `ukit install` (and `ukit update`'s refresh) prints a bold-red warning with setup instructions — `ukit decision --base-url <url> --key <key>`, `~/.ukit/storage/gatewayDecision.json`, or `UKIT_DECISION_API_KEY` — whenever no dedicated decision key and no shared UNIC token are resolvable. When a key (or the shared UNIC token fallback) is found, a one-line confirmation is printed instead.
868
-
869
- ## 3.1.4 - 2026-09-26
870
-
871
- - **`ukit decision` — user-facing decision-lane gateway setup.** Resolution order (per field): env `UKIT_DECISION_BASE_URL`/`UKIT_DECISION_API_KEY`/`UKIT_DECISION_SCHEME` → `~/.ukit/storage/gatewayDecision.json` (new per-lane file; `gateway<Lane>.json` pattern) → `~/.ukit/storage/config.json` `decisionGateway` → `openai.unicjsc.com` + shared UNIC token. File field names mirror the env vars; `scheme` selects `Authorization: Bearer` vs `x-api-key`. Both files are seeded by `ukit install` with the full key set (`mergeStrategy: skip` — `ukit update` never overwrites user values). Commands: `--status`, `--base-url/--key/--scheme`, `--set-unic`, `--clear`.
872
-
873
- ## 3.1.3 - 2026-09-26
874
-
875
- - **`unic-decision-multilingual` becomes the shipped default checkpoint** — the variant is credential-bound on UNIC Provider (verified via live `health-probe` + `safe-vs-risky-lane` decision). `english`/`unknownLanguage` classes keep the bare `unic-decision` alias; `model_not_found` auto-fallback still covers unbound variants.
876
-
877
- ## 3.1.2 - 2026-09-26
878
-
879
- - **Decision plane goes live on the UNIC provider** — the decision lane now resolves its own endpoint independent of the engine's LLM gateway, so UKit uses UNIC even when Claude Code/Codex/omp point elsewhere:
880
- - **Endpoint chain**: `~/.ukit/storage/gateway.json` `{decision:{baseUrl,apiKey,scheme}}` → env `UKIT_DECISION_BASE_URL`/`UKIT_DECISION_API_KEY` → default `https://openai.unicjsc.com`; credential falls back to the shared UNIC token (ANTHROPIC_*). New resolvers `resolveDecisionBaseUrl`/`resolveDecisionApiKey` in `src/core/gatewayProbe.js`, mirrored in `unic-decision.mjs`.
881
- - **Live transport fixes** (verified against the real gateway): SSE `data: [DONE]` trailer — sometimes glued to the JSON body — is stripped via balanced-object extraction; model answers use native arg names (`choice`/`noul`/`score`) now accepted alongside the schema's `value`; a `model_not_found` variant checkpoint retries once on the bare `unic-decision` alias.
882
- - **Checkpoints**: shipped defaults collapse to the bare `unic-decision` model (the credential-safe alias); `unic-decision-multilingual`/variants remain configurable via `decisionPlane.checkpoints`.
883
- - **Optional backlog drained**: injection-point contracts documented (deliberation `judge`, vmEngine `classifyFn`, completionGate `modelJudgment`), `memoryV2.decision` plane marked reserved, `resume.next-action.v1` + `verify.depth.v1` shadow questions wired, gatewayProbe marked migration-exempt.
884
-
885
- ## 3.1.1 - 2026-09-26
886
-
887
- - **Decision plane — review + workflow families (UNIC_DECISION_MIGRATION S1–S4)** — the reserved `review` and `workflow` registry families are now populated and wired; all keys ship `rolloutStage: 'off'` so deterministic fallbacks stay authoritative (stage promotion is a separate owner decision):
888
- - **Registry** (`src/decision/registry.js`): `review.verdict.v1`, `review.finding-bucket.v1`, `review.panel-verdict.v1`, `workflow.sidecar-lane.v1`, `workflow.sidecar-risk.v1`, `workflow.routing-needed.v1`, `workflow.step-budget.v1`, `workflow.compact-now.v1`, `workflow.summarize-vs-keep.v1` — all `choice` kind, `off`, deterministic fallback owners recorded.
889
- - **Review adapter**: `src/decision/reviewVerdict.js` + installed twin `template_project/.claude/ukit/index/review-verdict.mjs` — findings (whitelisted `{id, severity, file, line, claim}`) in, stage-gated verdict + per-finding buckets out; reviewers still generate findings on the general model, only the bounded verdict moves to `unic-decision` when `decisionPlane.families.review.stage` is enabled.
890
- - **Sidecar adapter**: `template_project/.claude/ukit/index/sidecar-decision.mjs` answers the six `.codex/settings.json` `smallTaskModel.decisionPolicy.decisions` via a bounded `unic-decision` batch (stage-gated `decisionPlane.families.workflow.stage`); adapter failure → deterministic rule answer, never another LLM.
891
- - **Engine parity**: `.codex/ukit` is a symlink to `.claude/ukit` (installed layout), `decisionAdapter` hints in `.codex/settings.json`; all three index CLIs' `isMainModule` gates now use `realpathSync` + basename equality — symlinked invocation previously compared unresolved paths and silently exited 0 without running `main()`.
892
- - **Docs/tests**: `docs/pstack/UNIC_DECISION_GUIDE.md` (family keys + adapters), `docs/GATEWAY.md` §8, `docs/MEMORY.md`; parity + symlink-invocation coverage in `tests/index/{unicDecision,reviewVerdictCli,sidecarDecision}.test.js`.
893
-
894
- ## 3.1.0 - 2026-09-26
895
-
896
- - **Flight recorder — Data Foundation wave (cycle C81)** — the observability pipeline grows from record/segment plumbing into a full local diagnostics surface; still opt-in behind `observability.stage` (default `off`, `off→shadow→canary→default` per seam, absolute kill switch):
897
- - **Envelope v1.1 + sampling**: additive `agent_id`/`project_instance_id`/`sampling` stamp fields and new semantic names (`memory.write`, `memory.retrieved`, `retrieval.query`, `outcome.observed`, `anomaly.detected`, `telemetry.crashed`); `observability.sampling` seeded-bucket keep-rates per importance level with `SAMPLED_OUT`/`CONFIG_INVALID` reason codes — `critical` is never sampled.
898
- - **Segments**: sealed segments compress to `.jsonl.zst` on Node ≥ 22.15 (plain `.jsonl` otherwise); readers, recovery, and quarantine handle both transparently.
899
- - **Crash capture + lifecycle**: bounded `crashes/crash-<boot>-<seq>.json` capture on uncaughtException/unhandledRejection/SIGINT/SIGTERM (≤10 files, FIFO, never throws); `getRecorder` memoized per (root, boot) with interval flush and deadline-bounded exit flush.
900
- - **Ingestion + instrumentation**: `ingestStoredTelemetry` pulls stored hook telemetry, route/decision ledgers, and memory/context items into segments; agentRuntime and memory/retrieval paths emit real trace/span ids with honest `UNKNOWN` resource provenance.
901
- - **CLI**: `ukit telemetry` — `status`, `collect`, `digest`, `export-support`, `import <path>`, `evaluate` (`--json` on status/digest/evaluate; exit 0/2, usage 1). `ukit doctor` gains a flight-recorder section (stage, segments, support lag, crashes — `unknown` when unavailable). `ukit feedback` emits `outcome.observed`.
902
- - **Support view**: `Documents/UKit Support` provisioned at install (never deleted by uninstall); support refresh is scheduled after collect and on the lifecycle interval, with crash list, anomaly section, and freshness lag stamped in `SUMMARY.md`; `import` validates bundles (manifest/checksums/traversal/decompression bounds).
903
- - **Anomaly detection + evaluation**: deterministic detectors (duration outliers, retry storms, cache-miss/drop-rate spikes, verification-failure clusters) produce `anomaly.detected` records with evidence refs; `runEvaluation` dispatches to a configured `observability.evaluator` provider — `skipped/no-provider` is the honest default — and appends validated findings to the optimization KB; expanded golden corpus with `--anomalies` bench flag.
904
- - **Docs**: `docs/OBSERVABILITY.md` — stages, privacy contract (what is never recorded), the support-folder zip-send flow, CLI and config reference.
905
-
906
- ## 3.0.12 - 2026-09-26
907
-
908
- - Re-publish of the 3.0.11 content: npm staged-publish left 3.0.11 in limbo (E409 "previously staged version"); re-published as 3.0.12 — same tree, version bump only.
909
-
910
- ## 3.0.11 - 2026-09-26 (staged, never published)
911
-
912
- - **C80 bug-sweep fix cycle — all 23 confirmed/high-confidence execution-path bugs fixed** (`docs/AI_HANDOFF/REPORT-C80-bug-sweep.md`):
913
- - Index CLIs (`query-index`, `triage`, `resolve-context`, `verify-context`, `impact-context`, `route-task`): top-level try/catch error boundary — unhandled-rejection crashes become clean exit(1) (C80-01..06).
914
- - `cache-utils.mjs` `readRecentCacheEntry(touch:true)`: touch-write failures degrade to in-memory entry, matching the token-utils prompt-cache contract — a full/unwritable cache can no longer reject a read (C80-02).
915
- - `index-core.mjs`: new `ensureIndexFresh` — cross-process `withFileLock` build lock + staleness re-check inside the lock; artifact caches invalidated before publish writes, not after (C80-07/08).
916
- - `frontend-vue` composables: `useRequest` ×3 `finally` decrement of `loading_count` (stuck spinner); `useWebSocket` retry dedup + cancellable timer + disposed guard; `useSession.getSession` corrupt-blob guard; `indexDBStore` promises now settle on transaction/clear errors (C80-09..16).
917
- - Skill scripts: `with_server.py` pipe deadlock + process-group kill; `init-project-docs.sh` sed escaping + backup-instead-of-rm; `document.py` deterministic `close()`; `rearrange.py` samefile compare; `find-polluter.sh` glob/quoting fixes (C80-17..22).
918
- - `supervisor.js`: listeners attach before awaited work post-spawn; liveness via injectable `probeImpl` (kill(pid,0)); `killGroup` revalidates ownership before signaling a possibly-recycled pgid (C80-23).
919
-
920
- ## 3.0.10 - 2026-09-25
921
-
922
- - Re-publish of the 3.0.9 content: npm staged-publish left 3.0.9 in limbo (E409 "previously staged version"); re-published as 3.0.10 — same tree, version bump only.
923
-
924
- ## 3.0.9 - 2026-09-25 (staged, never published)
925
-
926
- - **ukit-memory stack (cycles C57–C62, waves W1–W6)** — the full v2 memory layer lands behind staged rollout flags:
927
- - **Record store v2**: versioned `records.json` store (`src/core/memory/storeV2.js`, `recordStore.js`, `records.js`) with tombstones, generation counters, fingerprint dedupe, and a locked read-modify-write path in `mutateMemory`; automatic v1→v2 migration (`migrate.js`, `migrateMapping.js`) with `autoMigrate` config.
928
- - **Retrieval**: deny-by-default eligibility policy (`policy.js` — status/expiry/provenance/trust-tier/project-binding), generation-bound in-memory `recordIndex`, ranked hits (`memoryHit.js`, `retrieval.js`), and labeled `## Previous Context` injection that renders record text as data, never instructions.
929
- - **Freshness**: `memoryFreshness.js` resolves `evidence[].locator` with `lstat`+`realpath` containment — symlinks escaping `projectRoot` report `locator-unverifiable`, never `fresh`.
930
- - **Write safety**: `writeGuard.js`/`writeClassification.js` reject secret-bearing payloads before persist; `sensitiveValueScanner` shared.
931
- - **Backup/restore/purge**: `storeBackup.js` byte-copy backups with sha256 manifest (mode 0600), manifest boundary check (`backup-file-out-of-boundary`), tombstone precedence on restore; CLI `memory purge/export` lanes sweep `deletePromptCacheEntries` so purged content cannot resurrect from the prompt cache.
932
- - **Rollout flags (W6)**: `memoryV2.{eligibility,writer,index,decision}.stage` on the shared `off→shadow→canary→default` ladder, `canaryProjects`, and absolute `killSwitch` — read live on every operation, config-only reversal, no storage-format change. Ships at `default` for eligibility/writer/index, `off` for decision, `killSwitch: false`.
933
- - **Security review (W6)**: `tests/security/memorySecurity.test.js` (11 tests) — fixed symlink-follow in `resolveLocator` and manifest path escape in `restoreBackup`; 0 open high-severity findings.
934
- - **Gate G6**: canary delta clean (0 hit/query divergence on 2000-record seeded corpus), kill-switch drill pass on read and write legs — verdict **GO** (`docs/AI_HANDOFF/inventory/g6-verdict.md`).
935
- - **Installed mirror**: `template_project/.claude/ukit/runtime/memory-{flags,freshness,policy}.mjs` shipped for hook-side parity.
936
-
937
- ## 3.0.8 - 2026-09-24
938
-
939
- - Re-release of the 3.0.7 content: npm staged-publish left 3.0.7 in limbo (E409 "previously staged version"); re-published as 3.0.8. Tag v3.0.7 exists on the same tree.
940
-
941
- ## 3.0.7 - 2026-09-24
942
-
943
- - **Data foundation & flight recorder (cycle C54)** — new `src/core/observability/` pipeline, all behind `observability.stage` (default `off`, staged `off→shadow→canary→default` per seam with kill switch):
944
- - **Schema + privacy**: versioned record envelope (`schema_version: 1`), semantic/reason-code registry, and a two-gate privacy boundary — `sanitizeObserved` before any persistent write (allowlist + deny-list + redaction), `sanitizeForSupport` as an independent default-deny second gate.
945
- - **Recorder + segments**: bounded non-blocking `emit()` with live stage gate, span tracking, deadline-bounded flush, and append-only JSONL segments with rotation/retention and partial-tail recovery.
946
- - **Analytics**: deterministic trace summaries (p50/p95/p99, causal critical path, retry/drop/cache metrics), honest `telemetry_complete=false` on drops/gaps/UNKNOWN host usage, and rebuild-from-segments recovery.
947
- - **Support view**: `UKit Support` materialized projection under the OS-native Documents folder — bundle-local pseudonyms, atomic writes, byte caps, failure-promoted digests, and a validated import path (manifest/checksums/traversal/decompression bounds).
948
- - **Evaluation**: offline evaluator packet (summary → anomalies → digest → evidence) and an optimization knowledge base recording hypothesis → experiment → guardrails → decision → rollback.
949
- - **Rollout**: `resolveSeamStages`/`resolveSeamConfig`/`killSwitch` in `src/core/observability/rollout.js` — recorder activates at `shadow`, support projection at `canary`, evaluation at `default`; per-seam overrides are restrictive-only so a global `off` is an absolute kill.
950
- - **Privacy fix**: `error_detail` added to the deny-list (free-form text, not a code) and `REDACTION_VERSION` bumped to `df-redact-3` — fixture secrets can no longer persist in canonical segments.
951
- - **unic-decision docs**: `docs/pstack/UNIC_DECISION_GUIDE.md` documents the local Lava/JEV decision model (not an LLM), checkpoint IDs, typed `tool_calls` contract, and `modelRoles.decision` binding for omp.
952
-
953
- ## 3.0.6 - 2026-09-24
954
-
955
- - Clarified the project owner's `unic-decision` contract in owner instructions, project memory, the technical spec, and shipped internals: a local Lava/JEV model in UNIC Provider, not an LLM; the OpenAI-compatible API is transport for convenient integration, not evidence of remote hosting or generative-model pricing.
956
- - Documented the preferred bounded typed-decision usage and the existing stage-off rollout/fallback in package-side client/config comments and the installed adapter, without changing runtime behavior or enabling decision calls.
957
-
958
-
959
- ## 3.0.5 - 2026-09-24
960
-
961
- - **Review-fix hardening (cycle C53 fix round 1)** — defects found by the release reviewer after 3.0.4 shipped:
962
- - **Memory**: `appendCompactHistory` read-modify-write now runs under the store lock — concurrent appends can no longer lose entries (unlocked RMW race).
963
- - **Installed mirror**: restored the missing `index-core` declaration in the installed `.claude/ukit/` mirror so dev-mirror parity checks pass on hydrated workspaces.
964
- - **Shipped hooks**: `sensitive-data-guard` no longer bypassed by wrapper commands (`sudo`/`env`/`bash -c`/`xargs`) or basename-obfuscated invocations — the guard now unwraps wrappers and matches on the real binary name.
965
- - **Test scoping**: `payloadDocs` stale-prose sweep restricted to shipped surfaces (root docs, `template_project`, `src`, `bin`, `scripts`) — it no longer walks `docs/AI_HANDOFF/**` reports or gitignored runtime dirs; `mirrorPayload` parity now tolerates stale/runtime files under the gitignored installed mirror.
966
- - **Installed-mirror resync**: stale `index/detectProjectContext.js`, query-index cache, lock dirs, and resolve-context cache regenerated so the installed mirror matches the template payload.
967
-
968
- ## 3.0.4 - 2026-09-24
969
-
970
- - **Full source audit (cycle C53) — ~86 defects fixed across all 14 audit areas**; every fix carries a RED→GREEN regression test under `tests/audit/`:
971
- - **CLI** (`bin/ukit`, `src/cli/**`): watchdog `unref()` silent-exit-0 on hung `runCli`; `--tools=` empty value deselecting all adapters; `install --help` exiting 1; `update`/`status` silently ignoring positional/unknown args; unknown `--adapter` silently mapping to `.claude`; `--flag=a=b` truncation; `extractFlag` swallowing the next flag as a value; `memory` crash on null ledger receipt.
972
- - **Lifecycle** (`src/core` install/update/uninstall/plan): uninstall data loss — tracked *file* entries removed via recursive `fs.rm` (a user dir replacing a managed file was deleted wholesale); `cleanupEmptyParents` crash on ENOTEMPTY/ENOENT races.
973
- - **Hooks/policy/security**: `hookChainDoctor` TypeError on missing `projectRoot`; `permissionPolicy` non-array surface lists miscompiled/crashed → now fail-closed `UKIT_EPOLICY`; `unattendedDoctor` counted only `'prompt'` not `'ask'`; uppercase SHA-256 allowlist digests silently unmatched; `gatewayProbe`/`resolveGatewayApiKey` threw despite never-throw contracts; `detectCustomGatewayAsync` was a dead sync wrapper now truly async and wired.
974
- - **Handoff/contracts/compact/experiments**: 10 defects incl. forced anchors dropped past `maxLines` while still counted; unlocked read-modify-write race in `appendCompactHistory`; shallow freeze letting a judge hide hard-constraint violations; retry-corrupted `state.budget.remaining`.
975
- - **Codeintel/output/token**: duplicate call edges + edges to non-existent callee nodes; `JsonGraphStore` crash on corrupt codegraph; `semanticProvider` reading `raw.files` vs `{items}` shape (index-wide resolve always empty); `PATH_RE` misrouting "and/or"/"n/a"; `packetToText` never rendering `packet.memory`; `drainDirty` dropping `saturated` flag; `parseCheckLine` returning wrong stderr line; `summaries` provider bound to `process.cwd()`; `sweepTeeCache` unenforceable maxFiles cap; `appendOutputHistory` dropping empty-command entries.
976
- - **Memory**: `addRecord` never ran `ensureMigrated` (first v2 write stranded all v1 data); corrupt legacy JSON silently dropped and hidden from `needsMigration`; unbounded `observeLearningSignal` text; concurrent-run counter races.
977
- - **Index/routing**: `queryCodeIndex`/`queryAnalog` TypeError on non-string input; corrupt artifact `items` crashing `groupBy`; substring signal misclassification ('score'→'core', 'install '→'all '); importers ignoring aliased specifiers; `extends: "pkg"` resolving `pkg.json` not `pkg/tsconfig.json`; `shellEscape` dropping apostrophes; empty verification-plan floor; `test:*` scripts missed by `TEST_RUNNER_COMMAND`; installed index-core mirror drift re-synced.
978
- - **Decision plane**: `sanitizeValue` `__proto__` prototype mutation; half-open circuit breaker with no single-probe gate and never-refreshed `openedAt`; `invalidateLease` raw TypeError on malformed records.
979
- - **Diagnostics/render/skill/learning/stack/bug**: `ledgerFiles` omitted-limit NaN → empty results; `renderTemplate` `{{constructor}}`/`{{toString}}` rendering `[native code]`; `statusSkillAudit` crash on null entries; `knownSignaturesAndTexts` missing legacy `signature` collection; `detectStack` raw SyntaxError on corrupt package.json; `triageBug` ignoring declared `packageManager`.
980
- - **Scripts toolchain**: missing flag values silently defaulting across 9 scripts; unknown flags ignored; unhandled promise rejections; silent partial index on unreadable files; `audit-perf.mjs` unbounded `spawnSync`/`execFileSync` (hang) → 60s SIGKILL timeout.
981
- - **Shipped hooks** (`template_project/.claude/hooks`): `block-dangerous` deadline fail-open + missed bare `git push -f`; `record-execution` never armed deadline; `sensitive-data-guard` missed joined/`=` credential forms and wrapper-command bypass (`sudo`/`env`/`bash -c`/`xargs`); `session-episode` hardcoded stdin watchdog; `handoff-model-guard` silent crash exit; `auto-allow-bash` unquoted glob expansion corrupting allow rules.
982
- - **Template payload/manifests/docs**: stale dev telemetry shipped via `runtime-cache` manifest item; `pdf-processing-pro` frontmatter name mismatch; handoff-planner `§7` drift; PLAN.md seed format drift; `QUICK_START` `@ukit/cli` ref; `RULES.md` nonexistent `PLAN.md §7` reference; broken archive doc links.
983
- - **Test health**: `test:handoff` now self-installs UKit first (19/50 failures on fresh clones); stale pre-TASK-025 watchdog wiring assertion fixed; dead conditionals removed.
984
-
985
- ## 3.0.3 - 2026-09-23
986
-
987
- - Same content as 3.0.2 (npm staged-publish never finalized; re-published as 3.0.3).
988
-
989
- ## 3.0.2 - 2026-09-23
990
-
991
- - **v3 reshape leftovers + docs verify-and-close (cycles C49–C51)**:
992
- - Decision table v2: `MODEL_TIER_BY_CONTRACT` + `resolveModelTier` in `src/core/executionContracts.js` — contract→tier resolution is now data-driven.
993
- - `limits=` route-text segment behind `routing.rigor.stage` (`src/index/taskRouting.js` + `route-task.mjs` mirror; stage-off output byte-identical, 10-case suite).
994
- - Mechanical validators: `handoffDocValidator.js` + `reviewPanelAggregate.js` (+ `.mjs` CLIs) — handoff doc checks and review-panel aggregation now scriptable.
995
- - Exit-predicate loop in stop-coordinator; diversity-review contract; M05.1' program-gate verdict + pstack doc banners.
996
- - Docs: DOC-201..206 verified shipped (165/165 acceptance tests); stale STATUS.md queue pointer + 11 roadmap rows corrected.
997
-
998
- ## 3.0.1 - 2026-09-23
999
-
1000
- - **Template root split (breaking-scale layout change, kept on 3.0.x per owner decision)**: `templates/` → `template_project/` (project-level install surface) and `templates/user/` → `template_user/` (user-level `~/.ukit/` seeds). `buildPathConfig` gains `userTemplatesRoot`; `platform.user.yaml` sourceTemplates resolve relative to `template_user/`. Dev mirrors re-synced (C47 drift fixed). Pre-existing test debt fixed: `packageVersion` major pin, runtime config version, `routeCatalog` principle-skill map, `packageArtifact` negation handling, `artifactReferenceIntegrity` allowlist.
1001
-
1002
- ## 3.0.0 - 2026-09-23
1003
-
1004
- - Same content as 2.8.0 — re-versioned as a major: the UserLayer/ProjectLayer split plus the new `templates/user/` template set is a breaking-scale change and belongs on 3.x. 2.8.0 is deprecated on npm.
1005
-
1006
815
  ## 2.8.0 - 2026-09-23
1007
816
 
1008
817
  - **User-Level `.ukit` layer (cycle C46)**: new `~/.ukit/` layer resolved via `os.homedir()` (correct on Windows/Linux/macOS), immutable on `ukit update` (`level: "user"` manifests + `mergeStrategy: skip`).
@@ -1787,1012 +1596,6 @@ host.
1787
1596
  prompt-cache stats as `Local p-cache` — provider telemetry is reported `unknown`, never
1788
1597
  zero.
1789
1598
 
1790
- ## 2.4.3 - 2026-09-18
1791
-
1792
- C19 liveness-hardening release (23 handoff tasks): a full sweep of the shipped hook and
1793
- runtime surface against the freeze/stall/orphan classes behind the recurring "session
1794
- stands still mid-turn" reports, plus the regression instruments that keep them closed.
1795
-
1796
- - **Bounded hook stdin staging (H01)**: `hook-input.sh`/`hook-input.mjs` runtime helpers
1797
- plus bounded-staging fallback blocks in all 16 hook wrapper templates — a producer that
1798
- never closes the pipe can no longer hold a hook open (SIGKILL at the staging bound).
1799
- - **Deadline-aware hot-hook filesystem work**: hook runtime modules self-arm on
1800
- `UKIT_HOOK_DEADLINE_MS` so a wedged read or lock wait exits inside the hook budget
1801
- instead of orphaning a node child.
1802
- - **Process-tree + lock containment**: bounded process-tree kill when a descendant escapes
1803
- its group, atomic quarantine of validated stale lock generations, owner-stamp failure
1804
- no longer runs the callback under an ownerless lock, and deep-freeze + containment
1805
- fail-closed for discovery snapshot reuse.
1806
- - **Liveness suite + classifier**: `src/diagnostics/classifyHang.js`, `tests/liveness/`,
1807
- and the `test:liveness` script — evidence-only hang classification (an external signal
1808
- is not a TERM→KILL leak) with regression scenarios pinned in tests.
1809
- - **Execution-ledger hardening**: bounded route-scoped ledger journal, overflow guard on
1810
- drain commits, journal-local locking, and the Stop coordinator
1811
- (`stop-coordinator.mjs`) with its extracted watchdog path.
1812
- - **Runtime shipping fix**: the install pipeline ships every packaged
1813
- `.claude/ukit/runtime` module via the `ukit-runtime-scripts` directory item (TASK-035),
1814
- closing the class where a new runtime module shipped to npm but never installed.
1815
-
1816
- ## 2.4.2 - 2026-09-16
1817
-
1818
- Fix: the gateway resilience posture disabled the only recovery path a buffering gateway
1819
- leaves open — the direct client-side cause of the recurring "session stands still mid-turn
1820
- until the user interrupts and re-prompts" freeze. Live probes of the stall-class gateway on
1821
- 2026-09-16 proved the full chain: the gateway still buffers entire streams (a 16-token
1822
- probe returned 23 SSE events in ONE body read), so a long generation is silent until it
1823
- finishes; the non-streaming route is healthy (HTTP 200 + valid Anthropic Message); and the
1824
- managed env shipped since 2.3.16 kept the non-streaming fallback DISABLED with a 10-minute
1825
- stream-idle watchdog — meaning the client sat in dead air and, on abort, had no recovery
1826
- path at all. The managed posture now flips to fail-fast-and-recover.
1827
-
1828
- - **Posture flip** (`src/core/gatewayResilienceEnv.js`): `CLAUDE_CODE_DISABLE_NONSTREAMING_FALLBACK`
1829
- managed default `'1'` → `'0'` (fallback stays enabled — on a buffering gateway a
1830
- non-streaming POST is the one request shape without an idle watchdog), and
1831
- `CLAUDE_STREAM_IDLE_TIMEOUT_MS` `'600000'` → `'120000'` (a silent stream aborts after
1832
- 2 minutes and recovers via the healthy non-streaming route instead of hanging for 10).
1833
- Values equal to the previously shipped defaults are UKit's own earlier writes and are
1834
- migrated on the next `ukit install` (new `GATEWAY_RESILIENCE_ENV_LEGACY_DEFAULTS` map +
1835
- `migrated` report field, backup written as usual); genuinely user-tuned values are still
1836
- never touched.
1837
- - **Probe misdiagnosis fixed** (`src/core/gatewayProbe.js`): the probe 404'd healthy
1838
- alias-based gateways because it POSTed the built-in default `claude-sonnet-4-5`, which is
1839
- not provisioned there ("No active credentials for provider: claude", `model_not_found`,
1840
- reproduced live) while real sessions run on the `ANTHROPIC_DEFAULT_*_MODEL` lane aliases.
1841
- The probe now resolves `ANTHROPIC_MODEL` → `ANTHROPIC_DEFAULT_OPUS/SONNET/HAIKU_MODEL`
1842
- before the built-in default and reports the probed model. `anthropic-version` is now sent
1843
- for the Bearer scheme too (live-verified accepted), and the API key is resolved through
1844
- the same 3-tier order as the base URL (env → project settings → home settings) so plain
1845
- terminals no longer probe keyless (`resolveGatewayApiKey`).
1846
- - **request-id re-classified** (same file, `docs/GATEWAY.md` §3): a missing `request-id`
1847
- on an HTTP 200 + valid Anthropic Message is an advisory hint, not a FAIL — the real
1848
- gateway ships no request-id even on healthy responses and sessions complete fine. The
1849
- Message-shape hard gate still catches the 888-byte error-envelope class from 2.3.16.
1850
- - **Docs**: `docs/GATEWAY.md` intro/§1/§2/§3/§4/§5 updated for the fail-fast posture,
1851
- the 2026-09-16 buffering reconfirmation, the legacy-value migration, and the probe's
1852
- alias-model + key resolution.
1853
- - **Verification**: focused suites green (gatewayProbe 14, gatewayResilienceEnv 23,
1854
- packageVersion 3); full `yarn test` green; live re-probe after the fix reports the alias
1855
- model, a healthy non-streaming route, and the still-present buffering signature.
1856
- - **Orphan-leak class closed for the remaining hooks (2.4.1 follow-up)**: the 2.4.1 watchdog
1857
- shipped in exactly one hook (`skill-router.sh`); the other 18 node-spawning hooks could still
1858
- orphan a node grandchild to launchd when their work hung (wedged import, stalled mount — this
1859
- repo lives on an external volume). Every remaining hook now arms the same wall-clock
1860
- self-deadline: inline heredoc/`node -e` blocks carry
1861
- `setTimeout(() => process.exit(0), HOOK_DEADLINE_MS).unref()` directly, wrapper hooks pass
1862
- `UKIT_HOOK_DEADLINE_MS` (default 3000 ms) and their runtime scripts (`execution-ledger`,
1863
- `output-compression`, `reinject-context`, `post-edit-verify`, `pre-edit-backup`,
1864
- `stale-spec-check`) self-exit only when that env var is present, so CLI usage is never
1865
- self-killed. Lock-mutation blocks with a 5000 ms bounded wait (auto-allow-bash,
1866
- auto-prune-bash, reset-compact-pressure) use an 8000 ms deadline so the watchdog can never
1867
- fire while the mutation is legally waiting for the lock.
1868
- `tests/consistency/hookWatchdogCoverage.test.js` enforces the coverage for every future hook.
1869
- - **Bounded stdin transport for the hook chain (C19 wave 1, H01)**: hook payloads no longer
1870
- materialize unbounded in a shell variable or the exec environment — the exec-env path that
1871
- made large PreToolUse payloads fail `exec` outright (E2BIG) on macOS. New
1872
- `templates/.claude/ukit/runtime/hook-input.sh` (`ukit_stage_hook_input` via `mktemp` +
1873
- byte-capped `head`, drained producer, overflow policies `truncate`/`temp-file`/`refuse`)
1874
- and `hook-input.mjs` (streaming reader + CLI) stage every payload to a bounded temp file;
1875
- all 16 node-spawning wrapper hooks now pass `INPUT_FILE`, never the payload, with a
1876
- bounded inline fallback when the helper is absent. Sensitive-data-guard overflow is
1877
- fail-closed (`refuse`, silent exit 2); 32 MiB receipts verified < 10 s.
1878
-
1879
- - Machine-envelope lane in the sensitive-data gate: harness-injected notifications (task-notification / system-reminder / cross-session-message tags) now deliver with a redacted labels/counts advisory instead of being blocked when they quote secret-shaped test fixtures — ends the silent "Waiting for N background agents" stall. User-typed prompts, file/grep/bash channels, allowlist and overflow-refuse posture unchanged (fail-closed, default-ON, never echoes values).
1880
-
1881
- ## 2.4.1 - 2026-09-14
1882
-
1883
- Fix: the skill-router hook could hang the session and leak an orphaned process. `skill-router.sh`
1884
- runs on the `UserPromptSubmit`/`PreToolUse` hot path. Unlike its sibling hooks
1885
- (`task-watchdog.sh`, `handoff-resume.sh`), its node heredoc had no self-deadline watchdog: when
1886
- indexed-context resolution hung (a wedged import, a stalled mount), the host killed only the bash
1887
- wrapper with the node grandchild reparented to launchd and spinning forever — one orphan per run,
1888
- hundreds accumulated over days, adding sustained RSS pressure that presented as UKit freezing with
1889
- no message. The hook now arms the same wall-clock watchdog its siblings carry
1890
- (`setTimeout(() => process.exit(0), HOOK_DEADLINE_MS).unref()`, default 3000 ms, overridable via
1891
- `UKIT_HOOK_DEADLINE_MS`), so a hang can never outlive the hook. Early exit only drops the routing
1892
- hint — the same posture as a cache miss, and advisory-only as the hook already is. Applied
1893
- byte-identically to the live and shipped (template) copies.
1894
-
1895
- ## 2.4.0 - 2026-09-14
1896
-
1897
- Solution-discipline wording + offline instruments. This release is **additive**: it changes
1898
- instruction text that is already loaded in daily sessions and adds offline test instruments
1899
- under `tests/`, which the published tarball does not ship. It changes no runtime, config,
1900
- route, hook, or gateway behaviour, and it removes no existing behaviour.
1901
-
1902
- - **Solution ladder + carve-outs in the delivery lane.** `templates/.claude/skills/delivery/SKILL.md`
1903
- (and its active mirror) now carry the canonical ladder: choose the smallest solution that fully
1904
- meets the stated requirements and project conventions; prefer reuse of an equivalent codebase
1905
- helper, then the standard library / native API / an already-installed dependency, and treat new
1906
- custom code or a new dependency as the last resort. The carve-out is explicit: never drop
1907
- validation, security, accessibility, error handling, compatibility, or required tests to reduce
1908
- code, and never ship a weaker version and ask. The delivery "Tier 2 — Structure Scan" step now
1909
- prefers the project index/resolver and falls back to raw Glob/Grep only when the index is stale,
1910
- missing, or returns no match — understanding source before editing is never skipped.
1911
- - **Feature-implementer ladder (Claude Code + omp).** `templates/.claude/agents/feature-implementer.md`,
1912
- its active byte-twin, and `templates/.omp/agents/feature-implementer.md` gain the same ladder plus
1913
- a guard reminder that fewer lines are not a reason to drop a guard. The daily-mode test rule is
1914
- left verbatim: the ladder must not become an excuse to cut tests.
1915
- - **Reviewer rubric (Claude Code + omp).** The `code-reviewer` copies gain 5 evidence-first
1916
- solution-fit questions (duplicate semantics / standard library suffices / guard-dropping
1917
- simplification / shared root cause / speculative abstraction) and a rule that says
1918
- **never grade brevity or line count as a quality win**. The sidecar diff lane stays
1919
- non-blocking with no auto-delete; verdict and model-isolation contracts are unchanged.
1920
- - **Offline instruments (not shipped).** A pure metric protocol
1921
- (`tests/benchmarks/solution-discipline/protocol.mjs`), four acceptance fixtures under
1922
- `tests/fixtures/solution-discipline/` (F01 reuse-helper, F06 trust-boundary, F09 keep-failure-path,
1923
- F11 required-interface) with good/bad reference solutions, and a host driver core exercised through
1924
- fake hosts (nonzero exit, timeout, malformed events, duplicate usage, missing terminal event).
1925
- These live under `tests/`, which `package.json.files` does not publish, so they stay out of the
1926
- tarball by construction; the release check confirms the packed file list contains no `tests/` path.
1927
- - **Deferred, with reasons.** The paid pilot (roadmap PT-06) and confirmatory benchmark (PT-09) are
1928
- deferred: no spending cap is approved and no billable model call was made this cycle. The runtime
1929
- lifecycle work (PT-07/PT-08 — shared renderer plus route/lifecycle/omp integration) is deferred
1930
- because the evidence for instruction-only wording is sufficient to start and no runtime drift has
1931
- been observed yet. The remaining fixtures and live-host probing are queued in
1932
- `docs/AI_HANDOFF/PROPOSAL-C18-benchmark-fixtures.md` for the funded pilot cycle.
1933
- - **Evidence record.** The preflight inventory this release builds on is pinned in
1934
- `docs/plans/ponytail-evidence.md` (revision pin, existing/proposed inventory, command map, blockers).
1935
- - **Truthfulness.** Savings are unverified until a paid benchmark pilot runs; no token/LOC reduction
1936
- is claimed for this release.
1937
-
1938
- ## 2.3.24 - 2026-09-13
1939
-
1940
- Post-2.3.23 routing and self-install audit. Two real defects fixed, plus the repo-local
1941
- Release Policy mirror restored and guarded.
1942
-
1943
- - **`isInformationalPrompt` ported into the src canonical copy.** `src/index/taskRouting.js`
1944
- was missing the informational-prompt guard that the shipped copies in
1945
- `templates/.claude/ukit/index/route-task.mjs` and `templates/.claude/hooks/skill-router.sh`
1946
- received in 2.2.14. The 2.3.22 `consultationOnlySignal` only catches question-shaped
1947
- prompts (trailing `?`, a leading interrogative, or Vietnamese `…là gì / được không`), so a
1948
- prompt with an **embedded** interrogative and no leading marker — `"please tell me what the
1949
- auth module does"`, `"explain what files the installer writes"` — routed to `shared-edit`
1950
- with a write+verification contract in src while the shipped templates routed it
1951
- `informational`. That is exactly the fabricated-mutation-debt class 2.3.22 set out to fix,
1952
- still live in the copy that drives `ukit index route`. The helper is now byte-equivalent
1953
- across all three copies; implement/debug-worded questions still keep their lanes. Locked by
1954
- a new `tests/index/taskRouting.test.js` regression (verified RED without the call site).
1955
- - **Self-install detection no longer misfires on a local install.** The 2.3.23 guard treated
1956
- any `templates/` directory inside the install root as a self-install. A downstream project
1957
- that installs UKit locally (`node_modules/@ngockhoale/ukit/templates`) therefore matched,
1958
- and every `docs/` entry was downgraded to `skip` — so `ukit update` silently stopped
1959
- refreshing that project's docs. `isSelfInstall` now requires the package root itself to be
1960
- the project root (`<projectRoot>/templates` exactly) or the target `package.json` to name
1961
- `@ngockhoale/ukit`. Locked by a new `buildPlan` regression for the `node_modules` shape
1962
- (verified RED under the old containment test).
1963
- - **Release Policy mirror restored.** A `ukit install` run inside this repo (self-install)
1964
- had overwritten root `CLAUDE.md`/`AGENTS.md` from `templates/`, wiping the repo-local
1965
- Release Policy section that `docs/PROJECT.md` mandates at the top of both files. Restored
1966
- from the byte-identical pre-wipe copy; a new `tests/consistency/configDocsSync.test.js`
1967
- guard fails loudly if a future self-install wipes either copy again.
1968
- - **Verification.** `yarn test` 87 files / 1,553 tests green (also under `--sequence.shuffle`);
1969
- `yarn release:verify` exit 0; artifact unpacked ceiling raised once to 5,960,000 with
1970
- rationale in `tests/integration/packageArtifact.test.js`.
1971
-
1972
- ## 2.3.23 - 2026-09-13
1973
-
1974
- Self-install no longer clobbers UKit's own canonical docs. Running `ukit install` inside the UKit
1975
- source repository (e.g. the global CLI invoked from the repo) overwrote `docs/PROMPT_CACHING.md` —
1976
- the canonical 368-line ruleset — with the distilled 127-line copy shipped under `templates/docs/`,
1977
- because the manifest item is `overwrite_with_backup` and self-install went undetected.
1978
-
1979
- - **Self-install detection.** `buildInstallPlan` now recognizes an install targeting the UKit repo
1980
- by two independent signals: the templates resolving inside the install target (the repo has a
1981
- `templates/` directory, the global CLI does not), or the target `package.json` naming
1982
- `@ngockhoale/ukit`. This covers the common case where the global CLI runs inside the repo, which
1983
- the path-containment check alone misses.
1984
- - **Docs downgraded to seed-only.** On a detected self-install, every `overwrite_with_backup`
1985
- entry whose target lives under `docs/` is downgraded to `skip`: a missing doc is seeded, but an
1986
- existing canonical doc is never overwritten. Downstream projects are unaffected — their docs
1987
- refresh on `ukit update` as before.
1988
- - **Verification.** New `buildInstallPlan` regressions cover the containment signal, the
1989
- package-name signal, and the unchanged downstream path; the full suite stays green.
1990
-
1991
- ## 2.3.22 - 2026-09-13
1992
-
1993
- Consultation-question routing fix — pure questions no longer fabricate mutation debt that the
1994
- completion gate then enforces against an answer turn. Observed live the same day: two Vietnamese
1995
- consultation questions (no English signal word, no target file) scored every candidate mode ≤ 0,
1996
- the mode ladder's upward bias resolved the find-cause/shared-edit tie to `shared-edit`, and the
1997
- gate blocked the answer turn six times ("missing write-evidence / verification-evidence") until
1998
- the continuation cap released it.
1999
-
2000
- - **Consultation questions carry no completion contract.** A question-shaped prompt (trailing `?`,
2001
- a leading English or ASCII-folded Vietnamese interrogative, or a `là gì / được không` tail) with
2002
- no implement/review/debug/failure/impact signal and no target file routes `informational` — the
2003
- same no-mutation-debt lane delivery-only requests already use. Applied to
2004
- `src/index/taskRouting.js`, the standalone router `route-task.mjs`, and the hook-embedded
2005
- routing copy in `skill-router.sh` (live twins byte-identical).
2006
- - **Leading interrogatives override action words.** The router's signal regexes are English-only,
2007
- so Vietnamese how-questions mentioning an action ("Làm sao mà đo được khi tôi cài hệ thống
2008
- này…?") kept a mutation contract. A leading interrogative (làm sao / thế nào / tại sao / phải
2009
- làm gì / …) now marks the prompt consultative even when it contains implement verbs
2010
- (sửa / thêm / cài / cài đặt / …) — asking HOW something is done is not ordering the action
2011
- performed. Question-phrased edit orders ("bạn sửa giúp tôi… không?") keep their write contract.
2012
- - **Verification.** New routing regressions lock the two incident prompts to `informational` with
2013
- empty contract evidence, and lock both guard directions (English signal-word questions and
2014
- question-phrased Vietnamese edit orders stay in their lanes); full suite green.
2015
-
2016
- ## 2.3.21 - 2026-09-13
2017
-
2018
- C16 release — the prompt-caching ruleset turns from research into shipped guidance, and the
2019
- prompt-assembly surfaces that inject into model context are made deterministic. No new commands
2020
- and no default runtime behavior changes: the tool-call policy ships as guidance only, pending the
2021
- A/B required before any behavior change.
2022
-
2023
- - **Canonical prompt-caching ruleset (`docs/PROMPT_CACHING.md`, repo-local).** Distills the UNIC
2024
- caching roadmap into CTX-01..10 (MUST), the SHOULD set, and the never-do list, with
2025
- evidence-labeled vendor sections (Anthropic, OpenAI, DeepSeek, GLM, MiniMax) and an
2026
- adopt/adapt/reject matrix. Upstream vendor docs are reference only — never UNIC guarantees
2027
- (UNIC behavior is labeled `unknown`/`inferred`). Repo-local by design; not shipped.
2028
- - **Shipped caching guidance (`templates/docs/PROMPT_CACHING.md`).** The distilled CTX rules,
2029
- never-do list, and short tool-call policy now ship with UKit installs through a new manifest
2030
- item `docs-prompt-caching` (`mergeStrategy: overwrite_with_backup`, so `ukit update` refreshes
2031
- it). `templates/CLAUDE.md` and `templates/AGENTS.md` gain a matching `## Prompt Caching`
2032
- pointer section, and the repo-local `CLAUDE.md`/`AGENTS.md` carry a minimal pointer too.
2033
- - **Deterministic prompt assembly.** `templates/.claude/hooks/skill-router.sh` ordered
2034
- model-visible memory-recall output by volatile `updatedAt` timestamps, so the same state could
2035
- assemble different prompt bytes across runs and defeat prompt caching (CTX-01/CTX-04). Ordering
2036
- is now a stable sort with a deterministic tiebreak and no volatile timestamps in model-visible
2037
- output; the live `.claude/hooks/` twin is byte-identical. Locked by the new
2038
- `tests/hooks/promptAssemblyDeterminism.test.js` plus an ordering regression in
2039
- `tests/hooks/skillRouterHook.test.js`.
2040
-
2041
- ## 2.3.20 - 2026-09-13
2042
-
2043
- C15 bug-fix release record — this release completes the silent-stop class on top of the
2044
- already-published 2.3.19 (published to npm 2026-09-13, registry verified, carrying the C14
2045
- valve removal); it adds no new features. npm is the distribution channel and `ukit update`
2046
- pulls from npm, so an install on 2.3.19 (or older) needs an update to receive these fixes.
2047
-
2048
- - **`--evaluate-stop` never releases a routed stop silently.**
2049
- `templates/.claude/ukit/runtime/execution-ledger.mjs` had a final dispatch with no `else`, so any
2050
- evaluation result of `{continue:false, notify:false}` that was not `capped` wrote nothing at all
2051
- — the Stop was allowed and the session idled with no visible reason. That default path is now a
2052
- loud release: an invisible blocker and a route with empty/short completion evidence both emit a
2053
- `systemMessage` naming the cause and how to resume, instead of silence. Malformed stdin no longer
2054
- crashes the hook into a silent stderr exit — it blocks with the crash detail, bounded by a crash
2055
- counter that loudly releases after the threshold and resets on a clean evaluate.
2056
- - **Fail-loud completion-gate wrappers.**
2057
- `templates/.claude/hooks/completion-gate.sh` and `templates/.claude/hooks/record-execution.sh`
2058
- exited 0 silently when the runtime script was missing or failed; both now emit a
2059
- `systemMessage` naming the missing/failing runtime and the `ukit install` remedy.
2060
- - **omp reentrant stop gets the same never-silent contract as the CLI.**
2061
- `templates/.omp/hooks/pre/ukit-bridge.js` released a reentrant stop with a non-blocking notice
2062
- and no continuation; it now blocks with the actionable reason like any other stop, stays bounded
2063
- by the ledger's continuation cap, and releases loudly at the cap.
2064
-
2065
- ## 2.3.19 - 2026-09-12
2066
-
2067
- C14 bug-fix release record — one correctness fix is shipped; this release adds no new features.
2068
-
2069
- - **Completion gate no longer silently releases a reentrant stop.** `templates/.claude/ukit/runtime/execution-ledger.mjs` (`--evaluate-stop`) had a `stop_hook_active` valve:
2070
-
2071
- ## 2.3.18 - 2026-09-12
2072
-
2073
- C13 bug-sweep release record — two wave-1 correctness fixes are shipped; this release adds no new features.
2074
-
2075
- - **Task-budget validator heading and target-count fix.** `src/core/taskBudgetValidator.js` and the shipped twin `templates/.claude/ukit/index/task-budget-validator.mjs` now accept the template's `## Test Cases (REQUIRED — TDD)` heading without a false `missing-field` verdict and count only top-level `## Target Files` bullets, avoiding indented sub-bullet miscounts.
2076
- - **Task-progress guard multi-section fix.** `src/core/taskProgressGuard.js` now evaluates milestone entries across every `## Progress` section, so a fresh appended entry is not masked by an older first-section entry while malformed and drift checks remain active.
2077
-
2078
- Verification: version pin and targeted regression suites pass; `yarn release:verify` is the closing release gate.
2079
-
2080
- ## 2.3.17 - 2026-09-12
2081
-
2082
- Long-task resilience — a handoff run is now measured before planning, checkpointed during
2083
- execution, and auto-split on wall-clock overrun instead of silently wedging. Cycle C12 turns
2084
- three questions into enforced machinery: "is this task too big to hand to an executor?"
2085
- (answered with data before a task is ever marked `ready`), "did the executor actually record
2086
- where it last stood green?" (answered by a machine-checkable milestone protocol), and "what
2087
- happens when a task blows its time budget?" (answered by a watchdog that cuts the task in
2088
- half and keeps the pipeline moving). Also fixes a repo-level gitignore trap that could
2089
- silently swallow new template files.
2090
-
2091
- - **Task-budget validator — `needs_breakdown` as data, not prose.** New
2092
- `src/core/taskBudgetValidator.js` plus a behavior-identical shipped CLI twin at
2093
- `templates/.claude/ukit/index/task-budget-validator.mjs` (self-contained, no `src/`
2094
- dependency, so user installs get the same gate). Thresholds: `maxTargetFiles: 3`,
2095
- `maxTestCases: 8`, `maxVerificationMinutes: 10`, with a table-driven verification-minutes
2096
- estimator (`yarn test:release-core` = 3 min, `node scripts/release/verify-release.mjs` =
2097
- 2 min, `yarn vitest run` = 0.5 min per file argument, unknown commands flat 1 min) and an
2098
- `investigate`+`first` prose rule for spike-vs-build splits. The `handoff-planner` agents
2099
- (Claude Code + omp) run the twin on every candidate task and must mark over-budget
2100
- `needs_breakdown` instead of shipping it as `ready`. Missing required sections emit
2101
- `missing-field` reasons; the validator never throws and the CLI always exits 0 (advisory
2102
- gate). TDD: 14/14 vitest cases + 4/4 ship-contract checks.
2103
- - **Executor milestone protocol.** Task executors now append `## Progress` entries in a
2104
- fixed, parseable shape — `- <ISO-8601> · milestone: <name> · last-green: <what passed> ·
2105
- files: <paths> · drift: none|<why>` — and both task templates gain a `- Size: S|M|L`
2106
- line. New `src/core/taskProgressGuard.js` makes the entries machine-checkable, with the
2107
- staleness boundary at exactly 2 × `milestoneIntervalMin` (inclusive = ok, beyond = stale).
2108
- The feature-implementer agents (Claude Code + omp) and the `handoff-fullstack` command
2109
- carry matching protocol text as byte-identical pairs. TDD: 6/6 unit cases + 4/4 protocol
2110
- contract checks.
2111
- - **Wall-clock watchdog hook, `hardPolicy: "split"`.** New
2112
- `templates/.claude/hooks/task-watchdog.sh` + `templates/.claude/ukit/runtime/
2113
- task-watchdog.mjs`, wired through `.claude/settings.json` (Stop + PostToolUse Edit/Write,
2114
- timeout 4) and `manifests/platform.full.yaml` (`hook-task-watchdog`). Budgets come from
2115
- `handoff.taskBudgets`: S 8/15, M 15/30, L 25/45 soft/hard minutes, `milestoneIntervalMin:
2116
- 5` default, `hardPolicy` `"split"` (default) or `"pause"`. Soft overrun emits a visible
2117
- "checkpoint a milestone now" advisory; hard overrun under split policy emits a Stop
2118
- `decision=block` naming the follow-up `TASK-<id>-b` — blocking the stop IS the
2119
- auto-split-and-continue mechanism — capped at 2 blocks per task before degrading to an
2120
- advisory that hands back to the user. The hook can never hang a session: 3 s self-kill
2121
- (`HOOK_DEADLINE_MS`), all-async I/O, 64 KB stdin cap, fail-open `exit 0` on every path;
2122
- PostToolUse is advisory-only and never emits a decision. State lives at
2123
- `.ukit/storage/cache/task-watchdog/state.json`; config load is fail-open to
2124
- `DEFAULT_CONFIG`. TDD: 16 sandbox checks (hard-trip block, pause, cap, fail-open,
2125
- wiring, no-undefined advisories) + config-docs sync coverage.
2126
- - **Gitignore trap fixed at both layers.** An unanchored `.claude/` pattern treats every
2127
- directory named `.claude` at any depth as ignored, and `templates/.gitignore` is a
2128
- per-directory ignore for the `templates/` subtree — so it silently hid NEW files under
2129
- `templates/.claude/**` from `git status`/`diff`/`add` (already-tracked files were
2130
- unaffected, which is why the trap stayed invisible). It ate the TASK-014 CLI twin, which
2131
- a `git worktree remove --force` then destroyed. Root `.gitignore` runtime dirs are now
2132
- anchored (`/.claude/`, `/.codex/`, `/.omp/`, `/.ukit/`, `/.worktrees/`) and the
2133
- `templates/.gitignore` runtime-dir lines are removed with an explanatory NOTE; new
2134
- template files no longer need `git add -f`.
2135
-
2136
- ## 2.3.16 - 2026-09-11
2137
-
2138
- Gateway-stall root cause, part 5 — the operator's gateway stayed invisible in the repo. Wave 1
2139
- (TASK-011 + TASK-012) shipped the two client-side fixes that defend Claude Code against the
2140
- stall and the malformed-body incident; this release closes the loop with a written contract
2141
- the operator (UNIC or any other proxy in front of `ANTHROPIC_BASE_URL`) can be handed. The
2142
- two client-side fixes are also safe no-ops on the official Anthropic endpoint — they only
2143
- fire when a gateway is in the path, so uninstall does not need to clean them up.
2144
-
2145
- - **Managed gateway resilience env defaults.** When `ANTHROPIC_BASE_URL` is non-empty (env,
2146
- project `.claude/settings.json`, or home `~/.claude/settings.json`), `ukit install` now
2147
- writes `CLAUDE_CODE_DISABLE_NONSTREAMING_FALLBACK='1'` and
2148
- `CLAUDE_STREAM_IDLE_TIMEOUT_MS='600000'` into the project `.claude/settings.json` `env`
2149
- block via a new `merge_env_overwrite_with_backup` strategy. Never clobbers a user-set
2150
- value (a non-default value moves into the report's `skipped` list); re-running `ukit
2151
- install` is a no-op (`unchanged`); corrupt settings JSON fails safe without overwriting
2152
- the file. New module `src/core/gatewayResilienceEnv.js` + wiring in
2153
- `src/core/runInstallPipeline.js` and `src/cli/commands/install.js`. TDD: 12/12 unit
2154
- cases + 5/5 installCommand wiring cases green.
2155
- - **`ukit doctor --gateway` live probe.** New opt-in flag on `ukit doctor` posts one tiny
2156
- streaming and one tiny non-streaming probe to `/v1/messages` and prints a `✓`/`✗` per
2157
- requirement. Streaming is flagged as `buffered` when the first body read alone already
2158
- carries ≥2 SSE events (the exact stall signature). Non-streaming fails when the body is
2159
- HTTP 200 but not an Anthropic Message **or** the `request-id` header is missing — the
2160
- exact check whose absence let the 888-byte gateway error envelope slip through and kill
2161
- the user's turn. New module `src/core/gatewayProbe.js` (`fetchImpl` injectable, fully
2162
- hermetic test surface); wiring in `src/cli/commands/doctor.js` (`--gateway` added to
2163
- `KNOWN_FLAGS` + help; verdict is advisory and MUST NOT set `process.exitCode` so
2164
- scripted `ukit doctor` runs stay hermetic). TDD: 6/6 unit cases + 8/8 doctorCommand
2165
- wiring cases green.
2166
- - **Gateway operator requirements doc.** New `docs/GATEWAY.md` states the three
2167
- requirements the operator must satisfy — (1) SSE/bytes relayed incrementally (no
2168
- full-response buffering), (2) idle streams kept alive ≥600 s under the watchdog, (3)
2169
- non-streaming route returns a real Anthropic Message with a `request-id` header — plus a
2170
- client-side knob table (`CLAUDE_CODE_DISABLE_NONSTREAMING_FALLBACK`,
2171
- `CLAUDE_STREAM_IDLE_TIMEOUT_MS`, `ukit doctor --gateway`) and the explicit safe-no-op
2172
- guarantee on the official Anthropic endpoint. Probe hint lines from TASK-012's
2173
- `gatewayProbe.js` point at this doc.
2174
-
2175
- Residual unknown: `gatewayProbe.js` is exercised end-to-end against the real gateway only
2176
- through a hermetic `fetchImpl` (every test path uses an injected `ReadableStream`). A live
2177
- `ukit doctor --gateway` round-trip against the real gateway was NOT run in CI; it is a
2178
- manual post-release step on a gateway-connected machine. Recorded in `docs/STATUS.md`.
2179
-
2180
- ## 2.3.15 - 2026-09-11
2181
-
2182
- Vision-lane root cause, part 4 — the analyst never looked at the image. Found by mining the
2183
- user's own failing sessions across four real projects (UnicDB, VSDB, BAGuide, AI-Gateway). The
2184
- decisive record: a failed analyst subagent transcript is THREE lines with ZERO Read calls — the
2185
- analyst refused by name ("I am running on unic-lite, which is not a vision-capable model … I
2186
- must refuse to open, describe, or guess") without ever probing. The user confirmed the gateway's
2187
- vision routing is stable by design: unic-vision (backed by minimax/glm/chatgpt in their setup)
2188
- always reads images; nothing falls back to a non-visual lane. The failure was entirely
2189
- UKit-side, two stacked defects:
2190
-
2191
- - **Refusal by name instead of by probe.** The omp analyst template mandated refusing *before
2192
- touching any image* when the runtime model could not be confirmed vision-capable — and any
2193
- backend self-identification (`glm-5-turbo`, `MiniMax-M3`) or lite-lane label counted as "not
2194
- confirmed". Both agent templates now decide ONLY by the first image Read (the probe): if the
2195
- probe shows the image the lane reads it and reports the mapping it actually ran on in
2196
- `MODEL:`; a probe that fails to deliver the image is still `STATUS: WRONG_MODEL`.
2197
- - **No fallback after a refusal.** The honored-lane hint ordered the parent to dispatch the
2198
- specialist and simply continue, so a name-refusal left the image unread even though the parent
2199
- could read it natively (`STATUS: OK` ×14 from main Claude lanes in one VSDB transcript). The
2200
- hint now verifies the parent's own vision FIRST (step 2: Read the materialized files yourself,
2201
- write the receipts, do NOT dispatch), dispatches the specialist only when the parent's own
2202
- Read yields no image (step 3), and defines the fallback: on `WRONG_MODEL`/`NO_IMAGE` re-read
2203
- natively, analyse from your own view for pasted images, and never fabricate when no reader can
2204
- see it (step 4).
2205
-
2206
- Unchanged doctrine: never guess at image contents — the fix removes the two paths that turned
2207
- "don't guess" into "don't read". omp mirrors synced. TDD: `vision-router-hint` tests 13-14 and
2208
- `vision-agent` test 13 written RED first, then GREEN; all vision suites pass.
2209
-
2210
- ## 2.3.14 - 2026-09-11
2211
-
2212
- Vision-lane root cause, part 3 — the decisive one: the extractor could not see images in REAL
2213
- Claude Code transcripts at all. Found by reproducing the failure against the user's own real
2214
- session transcripts after they insisted the bug lived "right at the image" — grep proved the
2215
- transcripts contained `"type":"image"` while every extraction returned `imageCount: 0`. The
2216
- 2.3.12/2.3.13 suites were green because the fixtures modeled an invented transcript shape.
2217
-
2218
- **P1 — real transcript image envelopes were invisible to the extractor.** Verified against
2219
- real transcripts from four projects, Claude Code stores images in THREE shapes:
2220
-
2221
- - flat: `message.content[i] = { type: 'image', source: { type: 'base64', … } }` — the only
2222
- shape the pre-fix parser handled;
2223
- - pasted: a top-level `attachment` envelope (`type: 'attachment'`,
2224
- `attachment.prompt[]` = content blocks) — every real pasted image lives here, NOT in
2225
- `message.content`; the pre-fix parser extracted nothing from any pasted image;
2226
- - tool-returned: `message.content[i] = { type: 'tool_result', content: [ { type: 'image',
2227
- … } ] }` — screenshots coming back from tools nest one level down; also invisible.
2228
-
2229
- Fix: `extractImageBlocks()` now walks a bounded collector (depth ≤ 3) across
2230
- `message.content[]`, nested `content[]` arrays inside blocks, and the top-level
2231
- `attachment.prompt[]` / `attachment.content` envelopes. Same-base64 payloads across
2232
- envelopes dedupe by sha as before. Real-data validation after the fix: the same four
2233
- transcripts now extract valid images (PNG 2278×2154 from the paste envelope, JPEG 1400×884
2234
- from a tool_result, PNG/JPEG from the flat shape), and a live analyst dispatch read the
2235
- real pasted screenshot.
2236
-
2237
- Tests: `tests/handoff/cycle10/extract-image-contract.test.mjs` gains three cases whose
2238
- fixtures copy the real envelope structures verbatim (RED pre-fix: `imageCount 0`), plus a
2239
- cross-envelope dedupe pin. All cycle10 + cycle4 vision suites green.
2240
-
2241
- ## 2.3.13 - 2026-09-11
2242
-
2243
- Vision-lane root cause, part 2: the Codex model catalog could still deny the vision lane on
2244
- every gateway machine, even after the 2.3.12 plumbing sweep. Found by a fresh end-to-end
2245
- repro (install into a clean project → fire the hook → live dispatch) plus a live gateway
2246
- probe on 2026-09-11 that returned `STATUS: OK / MODEL: unic-vision` on a machine whose
2247
- `~/.codex/model-catalog.json` omits the alias.
2248
-
2249
- **P1 — the Codex model catalog could deny the Claude Code vision lane from another tool's
2250
- config.** `unic-gateway.mjs` derived `aliasAvailable` solely from
2251
- `~/.codex/model-catalog.json`: a catalog that omitted `unic-vision` — or was missing
2252
- entirely, the default on any machine that never used Codex CLI — produced
2253
- `aliasAvailable: false`, and both consumers (the vision router hint and route-task's
2254
- `resolveVisionModel`) then force-downgraded the lane to "read natively / do NOT dispatch"
2255
- or a config fallback. The catalog is a different tool's config and says nothing about what
2256
- the gateway resolves server-side for this session — the same principle TASK-007 already
2257
- established for endpoints. Fix: the catalog may now only CONFIRM the alias (new
2258
- `catalogListed` field); silence (absent, malformed, or alias-omitting catalog) leaves the
2259
- lane honored, with an informational advisory instead of a denial. The analyst agent's own
2260
- `WRONG_MODEL` self-check remains the in-band safety net: a genuinely dead alias fails
2261
- loudly and never guesses. `aliasAvailable: false` is reserved for a future source of
2262
- positive unavailability evidence, so the dormant fallback branches in both consumers are
2263
- unchanged and still covered by tests.
2264
-
2265
- Tests: `tests/handoff/cycle4/unic-gateway.test.mjs` and
2266
- `tests/handoff/cycle10/vision-lane-fallback.test.mjs` rewritten for the flip (catalog
2267
- silent → lane honored; catalog missing → lane honored; listing → positive confirmation),
2268
- with the strict `=== false` fallback contract kept as a source-level case.
2269
-
2270
- ## 2.3.12 - 2026-09-11
2271
-
2272
- Vision-lane freeze-sweep (post-2.3.11): the four defects that stranded the vision image lane on
2273
- nearly every image are fixed, the second consumer of the same advisory now honors the fallback,
2274
- and the installed vision-agent file mode is corrected. The cycle10 + cycle4 scripts prove the
2275
- plumbing; a real UNIC round-trip dispatch is not covered by the suite (see `docs/STATUS.md`).
2276
-
2277
- **P1 — `--detect` could not resolve absolute image paths outside the project, or paths wrapped
2278
- in quotes or trailing punctuation.** `extract-image.mjs`'s `--detect` arm accepted relative
2279
- paths and in-project absolutes, but the path-capture regex in `vision-router.sh` then refused an
2280
- out-of-project image ("did not resolve from the project root … Nothing was armed"), and
2281
- trailing punctuation / wrapping quotes (`'<abs>/x.png'.`, `"<abs>/x.png"`) broke the existence
2282
- check. Fix: `stripPathNoise()` in the extractor tries raw / soft-trailing-stripped /
2283
- wrapping-pair-stripped / both shapes against `fs.existsSync`; the hook-side regex now uses the
2284
- same tolerance. The interior of the path is never touched, and relative handling is unchanged.
2285
-
2286
- **P1 — marker receipts were leaked into `images[]`, so the dispatch hint could carry a
2287
- `pending-*.json` path to the analyst.** `--mark-pending --json` returned each marker receipt
2288
- (`{ path: 'pending-<sha>.json', bytes: 0 }`) inside the same `images[]` array that was supposed
2289
- to carry materialized images; downstream code that filtered "bytes > 0" still sometimes passed
2290
- the marker through, and the dispatch hint could carry a `pending-*.json` path the analyst would
2291
- not have materialized. Fix: `images[]` is now the materialized-only invariant (empty in
2292
- `--detect` / `--mark-pending` mode; every entry has bytes > 0 and a non-`.json` extension
2293
- otherwise); receipts live in a new top-level `pendingMarkers[]` carrying
2294
- `{ path, sha, bytes: 0, … }` per detection. On-disk marker format (`pending-<sha>.json`,
2295
- `bytes: 0`) is untouched — only JSON presentation changed.
2296
-
2297
- **P1 — the hook never forwarded the parent transcript, and default session discovery could
2298
- pick a newer-but-empty subagent transcript over the parent's image-bearing one.** When a
2299
- subagent spawn raced the paste, the subagent's empty transcript was the newest file in the
2300
- sessions root, so `discoverSessionFile()` returned it and the analyst got `imageCount: 0`. The
2301
- dispatch hint also lacked any `--session` argument, so the analyst could not materialize from
2302
- the parent transcript even when one was named in the payload. Fix: `discoverSessionFile()`
2303
- honors `CLAUDE_CONFIG_DIR` when set, calls `fs.realpathSync` so the macOS `/var` ↔ `/private/var`
2304
- symlinks do not drift the slug, and runs a bounded newest-first scan (`DISCOVERY_SCAN_BOUND = 5`)
2305
- with a cheap 64 KiB `transcriptHasImageHead()` peek — never an unbounded walk or full-content
2306
- parse. When nothing image-bearing is found, the script emits an explicit `STATUS: NO_IMAGE
2307
- scanned=<names>` (and a JSON line first under `--json`) instead of a fake success. The hook
2308
- hint now always carries `--session <payload.transcript_path>` whenever the payload provides one;
2309
- explicit `--session` still bypasses discovery and the NO_IMAGE branch entirely.
2310
-
2311
- **P1 — when the vision lane was unavailable, both consumers forced a failing dispatch instead
2312
- of degrading to native read.** `unic-gateway.mjs`'s `aliasAvailable: false` advisory was
2313
- ignored by `resolveVisionModel` in `route-task.mjs` and by the hook's hint builder, so a
2314
- gateway without vision routed the analyst task with `[model: unic-vision]` and the agent model
2315
- itself had to read the image, only to fail mid-dispatch. Fix: both consumers now honor
2316
- `aliasAvailable === false` — `resolveVisionModel` returns a non-`unic-vision` (native/main-
2317
- model) lane and states the unavailability in the routed output; the hook hint omits
2318
- `[model: unic-vision]`, says `vision lane unavailable`, and instructs a native read instead of
2319
- dispatching the analyst. The missing-field case preserves today's default; the
2320
- `unicMode === false` short-circuit is unchanged. Also: installed
2321
- `.claude/agents/ukit-vision-analyst.md` is now mode 0644 (template stays `100644` in git) — a
2322
- stale 755 from a prior install that was never regenerated by `ukit install` because
2323
- `copyFileSafe` preserves template mode.
2324
-
2325
- ## 2.3.11 - 2026-09-11
2326
-
2327
- Freeze-sweep wave 11 (post-2.3.10): the two deferred liveness candidates fixed via TDD, plus
2328
- a self-refresh downgrade trap repaired during verification. All template/live mirrors are
2329
- byte-synced.
2330
-
2331
- **P1 — SessionStart hook could hang the session forever.** `handoff-resume.sh`'s "advisory,
2332
- always exit 0" rested on `|| true`, which never fires when the embedded node process wedges
2333
- (hung runtime import, unresolved lock wait, stalled file read) — session start stalls mid-run
2334
- with no visible reason. A 3s wall-clock watchdog (`UKIT_HOOK_DEADLINE_MS`, env-tunable) now
2335
- exits 0 unconditionally, and the RUN.md read is async so sync I/O cannot block the timer.
2336
-
2337
- **P1 — router state writes could tear; route-audit merge lost entries.** All five
2338
- `skill-router-state.json` / `route-audit.json` writes were direct `writeFileSync`: a torn or
2339
- empty state parses as `{}` downstream and completion-gate.sh then releases a premature Stop
2340
- with no message. Writes now go through tmp+rename (`writeJsonFileAtomic`), and the audit
2341
- append runs under the standard PID + owner-token lock (5s bounded, fail-open). 16 concurrent
2342
- router runs previously kept only 13/16 audit entries; now 16/16.
2343
-
2344
- **Incident — post-release self-refresh downgraded live hooks.** Running `ukit install` from a
2345
- global CLI older than the published release rewrote six live hook mirrors with pre-release
2346
- content, resurrecting just-fixed lock-theft bugs in the development workspace. Recovered by
2347
- upgrading the global CLI and re-installing; the deferred guard candidate is a stale-CLI
2348
- warning in `ukit install`.
2349
-
2350
- ## 2.3.10 - 2026-09-11
2351
-
2352
- Freeze-sweep waves 7-10 (post-2.3.9): twelve verified mid-run-freeze defects fixed, each locked
2353
- by a regression reproducing the failure first. All affected template/live mirrors are byte-synced.
2354
-
2355
- **P1 — continuation budget reset on every route re-key.** The router re-keys `requestKey` per
2356
- tool call (the target file is part of the key), but the Stop-gate continuation budget was keyed
2357
- on `requestKey` — the count reset to 0 on every re-key, the cap was unreachable, and omp looped
2358
- forever (no `stop_hook_active` valve). Budget identity is now the logical prompt hash
2359
- (`promptKey`) everywhere, and omp gained `stop_hook_active` parity via `noteStopProgress`.
2360
-
2361
- **P1 — parallel execution receipts crashed and raced.** Same-process concurrent receipt writers
2362
- shared one temp path and crashed with ENOENT mid-hook; unlocked read-modify-write also dropped
2363
- receipts, and a missing/foreign route state could rebuild a session ledger from blank, erasing
2364
- banked evidence. Temp paths are unique, the whole receipt write runs under `withFileLock`, and
2365
- a missing route no longer blanks the ledger.
2366
-
2367
- **P1 — ledger lock waits exceeded the hook child budget.** `withFileLock` waited up to 5s but
2368
- the hook chain kills children at 4s, so a contended lock got the recording hook killed and omp's
2369
- fail-closed Edit|Write chain then blocked the edit. Ledger lock waits now cap at 2.5s and fail
2370
- open — a lost receipt beats a killed hook.
2371
-
2372
- **P1 — vibecode had no exit when verification kept failing identically.** Two adjacent identical
2373
- failed verifications (no edit between) now mint a visible `verification-loop` blocker; vibecode
2374
- additionally escapes after the same command fails 4× across edits.
2375
-
2376
- **P1 — clean map-impact Stop loop.** A completed analysis-only `map-impact` route still demanded
2377
- write + verification evidence. A narrow visible release valve permits a completed impact read
2378
- with no mutation attempt and no failed verification; incomplete analysis and partial edits stay
2379
- gated.
2380
-
2381
- **P1 — omp hook child timeouts falsely blocked edits.** A 4s-killed `protect-files` gate was
2382
- treated as its fail-closed verdict, freezing all edits on a slow machine. Timeouts now fail open
2383
- as infrastructure failures with a visible warning; `block-dangerous.sh` stays fail-closed. An
2384
- unknown mutation-shaped omp tool now normalizes to `Edit` and runs the normal safety chain
2385
- instead of emitting an impossible "add host mapping" block.
2386
-
2387
- **P1 — hard-cap grace slots crossed session boundaries.** Global grace slots let one session
2388
- spend or reset another session's landing allowance, stranding it mid-edit. Slots and advisory
2389
- state are now session-keyed.
2390
-
2391
- **P2 — transcript fallback rescanned up to 4MB per mutation.** A persisted, session-bound
2392
- 2-second boundary-probe cache coalesces mutation bursts to one scan; `skill-router.sh` also
2393
- skips its redundant prompt-only Node spawn on tool payloads.
2394
-
2395
- **P1 — lock stale-reclaim could steal a live owner.** The shared runtime lock used mtime-only
2396
- reclaim: a slow-but-alive holder was deleted after 10s, then deleted its successor's lock in
2397
- `finally` — lost receipts re-triggered completion debt. All lock implementations (runtime
2398
- mirror, verification guard, auto-allow, auto-prune, compact-pressure reset) now stamp
2399
- PID + random owner tokens, reclaim only provably-dead owners, and release only their own token.
2400
-
2401
- **P3 — stale verification-guard enforcement env var froze runs.** An inherited
2402
- `UKIT_VERIFICATION_GUARD_ENFORCE=1` turned an advisory test-order recommendation into an
2403
- exit-2 block. The guard is now exclusively advisory; real safety gates keep enforcement.
2404
-
2405
- Also in wave 7: piped/redirected verification (`yarn test 2>&1 | tail -6`) counts as targeted,
2406
- and delivery-only requests ("push this to git") route `informational` with no fabricated
2407
- mutation debt in all three routing copies.
2408
-
2409
- Full suite: 81 files, 1,439 tests green (plus wave 9-10 focused regressions). No npm tag
2410
- policy change; artifact unpacked ceiling raised once to 5,785,000 with dated rationale.
2411
-
2412
- ## 2.3.9 - 2026-09-10
2413
-
2414
- Freeze-sweep wave 5: fixes for completion-gate loops, worker-agent dead ends, and malformed
2415
- context-cap configuration that could otherwise halt all mutation progress.
2416
-
2417
- **P1 — clean `find-cause` audits were forced into a Stop-hook loop.** A recommend-only
2418
- investigation that found no actionable bug still required write and verification evidence, so
2419
- the completion gate blocked the honest outcome and demanded a fabricated edit. The execution
2420
- ledger now permits that narrow clean-audit outcome while retaining normal recovery blocks after
2421
- a failed verification or incomplete mutation.
2422
-
2423
- **P1 — routed workers could wait for a user they cannot contact.** The Claude Code and omp
2424
- `bug-debugger` / `feature-implementer` agents instructed workers to “ask the user” on unclear
2425
- or non-reproducible work. They now perform one bounded next diagnostic step and return a
2426
- structured `STATUS: BLOCKED` report with the exact missing artifact or decision to the parent
2427
- agent, which owns user communication.
2428
-
2429
- **P1 — malformed context-cap configuration could brick mutations.** Invalid
2430
- `compact.hardCapTokens` could collapse the cap to one token, invalid
2431
- `hardCapGraceCalls` could eliminate the landing window, and wrong-shaped present
2432
- `hardCapBlock` values could unexpectedly leave the hard gate enabled. The shared source/runtime
2433
- threshold logic and Claude hook now accept only positive integer budgets, while malformed
2434
- non-boolean `hardCapBlock` values fail open; the documented absent-key default remains enabled.
2435
- The context-window advisory uses the same hard-cap validation. Regression coverage includes
2436
- negative/zero/fraction/string/boolean/null budgets and malformed toggle values.
2437
-
2438
- Full suite: 81 files, 1,396 tests green.
2439
-
2440
- ## 2.3.8 - 2026-09-10
2441
-
2442
- Freeze-sweep wave 4: every fix in this release targets the "agent silently stops working"
2443
- class — lost permission rules that turn into human-waiting prompts, a session start that
2444
- wipes a sibling session's near-cap warnings, torn state files, and lost concurrency
2445
- bookkeeping. All found by verified reproducers and fixed with regression coverage.
2446
-
2447
- **P1 — SessionStart wiped a sibling session's compact-pressure state.** The SessionStart
2448
- reset hook deleted the whole project-wide `compact-pressure.json`, so starting a second
2449
- session in the same project zeroed the first session's pressure history: its near-cap
2450
- warnings stopped firing, it ran into the real context cap, and it stalled. Pressure state
2451
- is now a session-keyed document (`{"v":2,"sessions":{<session_id>:{…}}}`) with the newest
2452
- record's flat fields still projected at the top level for raw readers. Every writer and
2453
- reader threads the hook payload's `session_id` (compact-threshold CLI, output-compression,
2454
- reinject-context PreCompact, context-hardcap-gate); a brand-new session id starts clean
2455
- and never inherits a sibling's totals; the reset hook removes only the calling session's
2456
- record; sessions are pruned to the 8 most recent; a legacy flat file upgrades in place.
2457
- Ships in both `src/core/compact/threshold.js` and the runtime mirror.
2458
-
2459
- **P1 — concurrent auto-allow invocations lost Bash permission rules.** The hook's
2460
- read-modify-write of `settings.local.json` and `permission-usage.json` was unlocked, and
2461
- 30 concurrent invocations kept only 26/30 rules and 23/30 usage records — a lost rule
2462
- means the next run of that command prompts for permission again, i.e. the agent sits
2463
- waiting for a human click. Both files are now written inside one mkdir lock on
2464
- `<permission-usage.json>.lock` (protocol-compatible with `withFileLock`, fail-open ≤5s,
2465
- parent directory created before locking) with atomic tmp+rename writes, so Claude Code
2466
- can never observe a torn settings file either — a torn parse would drop the entire allow
2467
- list and prompt on every command. `auto-prune-bash.sh` now shares the same lock and
2468
- atomic writes.
2469
-
2470
- **P2 — index cache writes lost entries under concurrency.** `cache-utils.mjs`
2471
- read-modify-write cycles were unlocked: 20 concurrent writers kept 2 entries. All cache
2472
- reads-modify-writes (write + touch paths) now run under `withFileLock` with atomic
2473
- compact writes (cache files stay single-line JSON by contract).
2474
-
2475
- **P2 — verification-progress and execution-ledger counters lost concurrent updates.**
2476
- `verification-guard.sh` now records attempts through a locked re-read + merge (sync
2477
- `Atomics.wait` backoff so the hook's `process.exit` flow is untouched) and writes
2478
- atomically; `execution-ledger.mjs`'s continuation/notified counters re-read inside
2479
- `withFileLock` so parallel subagent Stop hooks cannot reset each other's budgets.
2480
-
2481
- Full suite: 81 files, 1,373 tests green, including two shuffled runs.
2482
-
2483
- ## 2.3.7 - 2026-09-10
2484
-
2485
- Bug-sweep wave 3: a data-loss escape in uninstall, cross-process races on shared runtime
2486
- state, one flaky test, and one vulnerable runtime dependency — all found by verified
2487
- reproducers and fixed with regression coverage.
2488
-
2489
- **P0 — uninstall could delete files outside the project root.** Tracked-path ownership
2490
- checks were purely lexical: with `.claude` (or any parent directory) symlinked to an
2491
- external location, uninstall's recursive remove resolved through the symlink and deleted
2492
- whatever it pointed at — e.g. a shared dotfiles directory. Uninstall now inspects every
2493
- directory component between the project root and each tracked entry (the entry itself may
2494
- still be a tracked symlink, which is unlinked, never followed); entries with a symlinked
2495
- parent are refused, warned, and reported in a new `skippedSymlinkParents` field in both
2496
- dry-run and real results.
2497
-
2498
- **P1 — concurrent state mutations silently lost updates.** `appendOutputHistory` and the
2499
- compact-pressure writers (prompt, output, plan, and the plain state write) performed
2500
- unsynchronized read-modify-write cycles on files under `.ukit/storage/cache/`. With
2501
- parallel subagents firing hooks in separate processes, 30 concurrent updates left a single
2502
- surviving output-history entry (of a 25 cap) and 17 of 510 accumulated sessionTokens —
2503
- understating context pressure and delaying compaction. All mutations now run under
2504
- `withFileLock`, a directory-lock protocol beside each state file (atomic `mkdir`, stale
2505
- reclaim after 10s, fail-open after 5s so a stuck lock can never freeze a hook). The lock
2506
- ships in both `src/core/fileOps.js` and the runtime mirror `token-utils.mjs` using the
2507
- same `<file>.lock` path, so CLI processes and hook processes serialize against each
2508
- other; mirror state writes also became atomic (tmp + rename). An interop test runs both
2509
- implementations against one project root to keep the protocols locked together.
2510
-
2511
- **Flaky test** — the `--no-outline` index-tools test queued a `getFileOutline` once-mock
2512
- its own flag guaranteed would never be consumed; `vi.clearAllMocks()` drains no once-queues,
2513
- so test order leaked the stale value into the next test (18/30 shuffled solo runs failed).
2514
- The dead queue is gone; the full suite is now 3/3 green under `--sequence.shuffle`.
2515
-
2516
- **Dependency** — runtime dependency `yaml` 2.8.2 → 2.9.0 (GHSA-48c2-rrv3-qjmp, stack
2517
- overflow via deeply nested YAML — UKit parses project-supplied manifests). Production
2518
- dependency audit is now 0 findings.
2519
-
2520
- Full suite: 78 files, 1,359 tests green.
2521
-
2522
- ## 2.3.6 - 2026-09-10
2523
-
2524
- Anti-stall coverage parity release: the compact-recovery and stop-reason directives that
2525
- UKit hooks inject at runtime on Claude Code and omp now also reach harnesses that have no
2526
- hook system at all.
2527
-
2528
- A new `## Long-Run Continuity` section ships in both `templates/CLAUDE.md` and
2529
- `templates/AGENTS.md` (byte-identical, enforced by the per-section context-docs parity
2530
- test). Codex and OpenCode load no hooks, so root `AGENTS.md` is their only instruction
2531
- channel — before this release those sessions never saw the near-cap recovery order (LAND
2532
- one thing → DEFER the rest to `docs/STATUS.md` → DELEGATE broad work to subagents → only
2533
- then compact) or the post-compact discipline (no rereads of pre-compact context; if the
2534
- first turn after a compact still sits at ≥60% of the cap, recover by delegating or starting
2535
- fresh from disk state instead of burning the window again).
2536
-
2537
- The same session closed the long-running stall investigation with debug-log evidence: the
2538
- observed "runs a while, then goes silent" behaviour is UNIC-gateway/network streaming
2539
- latency (repeated 30s slow-first-byte, one 300s byte-idle abort), not UKit hooks —
2540
- hook-error cache empty, exec ledgers healthy. When a dead stream ends a turn early, the
2541
- existing ≥2.3.3 Stop-hook completion gate blocks the premature stop, so staying current
2542
- (`ukit update`) plus restarting stale sessions (hook config loads at session start) is the
2543
- full remediation available in-repo; gateway-side idle/failover fixes belong upstream.
2544
-
2545
- ## 2.3.5 - 2026-09-10
2546
-
2547
- Source-audit hardening release: the code index cannot corrupt itself, and a corrupt runtime
2548
- cache can no longer take down `ukit status` or `ukit memory`.
2549
-
2550
- Index artifacts (`files`, `symbols`, `imports`, `calls`, `tests-map`, `hotspots`,
2551
- `archetypes`, `relations`, `analogs`, `meta`) are now written through same-directory
2552
- `.tmp-<timestamp>-<random>` files followed by an atomic `rename`, in both the source builder
2553
- (`src/index/buildIndex.js`) and the shipped `templates/.claude/ukit/index/lib/index-core.mjs`
2554
- runtime mirror. A build that crashes mid-write — or two builds racing in one repo — can no
2555
- longer leave a half-written artifact that poisons every subsequent index read; failed writes
2556
- clean their temp file up before rethrowing.
2557
-
2558
- `ukit status` and `ukit memory` now read their cache/memory JSON through tolerant readers:
2559
- a corrupt `compact-history.json`, `compact-pressure.json`, `prompt-cache.json`,
2560
- `output-history.json`, or memory file prints a warning naming the exact file path and falls
2561
- back to defaults instead of crashing the whole command mid-report. `readJsonIfExists` itself
2562
- stays strict everywhere else, so genuinely bad callers still fail loudly.
2563
-
2564
- Nested test layouts (`packages/widget/tests/unit/...`) are now recognized as tests by the
2565
- source path classifier and both runtime-mirror predicates — those files previously slipped
2566
- past test detection, broke archetype classification, and never appeared in the test map.
2567
-
2568
- Each fix ships with regression coverage: a rename-spy test asserting all ten artifacts move
2569
- through temp files, corrupt-fixture tests asserting the warned paths and surviving output,
2570
- and a nested-`tests/` mapping/archetype test. Full suite: 77 files, 1,348 tests green.
2571
-
2572
- ## 2.3.4 - 2026-09-10
2573
-
2574
- Silent-stall audit and compact-recovery release. Two themes: every block reports a
2575
- user-visible reason, and compaction must actually buy back context.
2576
-
2577
- Security hooks can no longer be bypassed or silently disabled. `block-dangerous.sh` catches
2578
- split recursive/force flags (`rm -r -f`, `rm --force -r`) and evaluates every delete target
2579
- per shell segment, so one allowlisted word can no longer legitimise a sibling target
2580
- (`rm -rf dist /`); a bare `/` stays classified unsafe, wrapped forms keep the whole-command
2581
- fallback, and detections surface as structured `ask` decisions that never echo the raw
2582
- command. `block-dangerous.sh`, `protect-files.sh`, and `auto-allow-bash.sh` fall back to
2583
- Node when `jq` is absent (stock macOS), so a missing optional binary cannot disable a gate.
2584
- `protect-files.sh` matches exact sensitive basenames and directory components instead of
2585
- substrings — `.env.d.ts` and `app.envrc` are source files, not secrets — and emits a
2586
- structured human-decision response on real blocks. `sensitive-data-guard.sh` only treats
2587
- `-u/--user` as credentials on tools that authenticate with it, so `docker run --user
2588
- 1000:1000` no longer false-blocks while `curl -u user:pass` still does.
2589
-
2590
- Stops always carry a reason. `handoff-model-guard.sh` pairs its stderr refusal with a
2591
- structured `systemMessage`; the completion gate reports a lost route state after real
2592
- session activity instead of releasing silently; hard-cap grace and sensitive-data blocks
2593
- already speak `systemMessage` from 2.3.3. `Phase: done …` with trailing status text now
2594
- counts as finished (`^done\b`, not `^done$`) in `handoff-resume.sh`,
2595
- `context-hardcap-gate.sh`, and `context-window-guard.sh`, so annotated done-phases stop
2596
- being resumed forever. Multi-file resume intents survive compaction: identity is session +
2597
- prompt key, because the router re-keys `requestKey` on every tool call and that churn is
2598
- what made post-compact resume a silent no-op.
2599
-
2600
- The hard-cap grace budget is race-proof. Parallel subagents hitting the cap in one episode
2601
- used to race a single read-modify-write counter and multiply the budget; each spent call
2602
- now claims an exclusive-create sentinel file, so the sentinels present are the true count
2603
- and one claim can never be counted twice (verified by an 8-process parallel test: exactly
2604
- the configured grants, the next call blocked).
2605
-
2606
- omp payloads moved off argv. PostToolUse Bash payloads embed whole tool outputs and exceed
2607
- macOS's ~256KB-per-argument limit, failing exec with E2BIG before any hook ran. The bridge
2608
- now writes the payload to a temp file (`@path` marker, hourly sweep, inline fallback for
2609
- read-only roots) and `hook-chain-runner.mjs` reads the marker; raw JSON never starts with
2610
- `@`, so both forms stay unambiguous.
2611
-
2612
- Compact recovery, directed. Near-cap advisories now order the work: land the smallest
2613
- finishable item end-to-end, defer the rest as one-line notes to disk, delegate broad
2614
- reads/searches to subagents, then ask the user to compact. A new post-compact check fires
2615
- once per compact boundary when the live context after the boundary is still ≥60% of the
2616
- cap: stop re-reading old files (the fastest way to re-inflate a just-compacted session),
2617
- delegate, or finish in a fresh session — UKit resume state carries the goal across with a
2618
- near-empty window. The reinjected PROJECT CONTEXT block carries the same discipline.
2619
-
2620
- Also fixed: `ukit install|diff --with-codegraph` crashed before the flag was consumed;
2621
- `route-task.mjs` helper commands use POSIX single-quote escaping instead of `JSON.stringify`
2622
- (printed commands were open to `$(...)`/backtick expansion) and reject absolute outside-root
2623
- targets instead of routing foreign-file context.
2624
-
2625
- ## 2.3.3 - 2026-09-10
2626
-
2627
- False-stop and long-context release. Four fixes that share one theme: UKit must run a prompt
2628
- to a finished result, and any stop must say why.
2629
-
2630
- Session-bound completion gate. Project-scoped route state could outlive the session-scoped
2631
- execution ledger, so a new session could inherit an older session's completion contract and
2632
- stop with a false `missing write-evidence` message. `skill-router.sh` now binds fresh, cached,
2633
- and route-less state to `sessionId`; `execution-ledger.mjs` accepts route state only when its
2634
- session matches the hook payload and ignores unbound legacy state for session-aware payloads.
2635
- Same-session gating and prompt-scoped evidence carry remain intact. Regression coverage now
2636
- covers mismatched sessions, unbound legacy state, and prior-session route isolation.
2637
-
2638
- Orchestration envelopes no longer corrupt the active route. `<task-notification>`,
2639
- `<tool-result>`, `<system-reminder>`, and `<local-command-caveat>…</local-command-stdout>`
2640
- payloads delivered through the prompt boundary were treated as explicit user prompts,
2641
- rewriting route/cache/audit state mid-run. `skill-router.sh` now ignores complete envelopes
2642
- before routing (fail-open, opening-tag attributes accepted); router exceptions surface on
2643
- stderr instead of disappearing. Related ownership fixes: Stop evaluation loads route state
2644
- with the current session payload, execution-ledger/route-task reject incompatible explicit
2645
- session ownership without inventing identity, subagent tool calls cannot rewrite the main
2646
- route, and cache entries are not touched before ownership is established.
2647
-
2648
- Ordinary long-context tasks preserve and resume. A natural-language routed task with no
2649
- `docs/AI_HANDOFF/RUN.md` previously hit the hard-cap gate with no landing window and no
2650
- resume cursor after compaction. Ordinary ledger state now gets the existing finite
2651
- `hardCapGraceCalls` landing budget (only with explicit session ownership, matching
2652
- session/prompt/request identity, unfinished evidence, and no blocker); the first grace call
2653
- writes a 30-minute hash-only resume intent that `handoff-resume.sh` consumes once and
2654
- emits as a continuation instruction with no raw prompt/command data. The
2655
- `context-window-guard.sh` fallback moved from 220k to the shipped 500k default.
2656
-
2657
- New `vibecode` autonomy level. One typed prompt must run to a finished result: with
2658
- `autonomy.level: vibecode`, the completion gate opts out of the continuation cap entirely and
2659
- keeps blocking (including the reentrant `stop_hook_active` Stop) until completion evidence
2660
- arrives or a genuine blocker is recorded — every block carries its reason. `deriveTaskRoute`
2661
- now propagates `autonomyLevel` and a `continuousExecution` policy
2662
- (`{ enabled, stopOn, maxContinuations }`) into `routeSummary` for every level, and
2663
- `validateRuntimeConfig` accepts the fourth level.
2664
-
2665
- Dangerous commands are a human decision, not a silent block. `block-dangerous.sh` now emits a
2666
- structured `permissionDecision: "ask"` (PreToolUse JSON) with the raw command scrubbed from
2667
- all output — arguments and comments can carry secrets — while exit 2 still refuses the call
2668
- for harnesses that ignore structured output. The omp bridge chain layer translates the same
2669
- structured decision into an `ask` verdict; because omp has no native ask, its host boundary
2670
- surfaces it as a block carrying the decision reason.
2671
-
2672
- ## 2.3.2 - 2026-09-09
2673
-
2674
- Docs-contract release. "Every stop says why — no silent idle" is now a shipping Execution
2675
- Contract rule, born from a real incident: a turn ended waiting for the user's `npm login`,
2676
- the request sat at the bottom of a long report, the user did their part (created
2677
- `~/.npmrc`), and the idle session looked exactly like a stall for 79 minutes.
2678
-
2679
- The new contract (identical in `CLAUDE.md` and `AGENTS.md`, parity-test enforced): when a
2680
- turn ends only because the user must act (login, approval, protected-file edit), the reply
2681
- opens with one line naming the exact action — `WAITING ON YOU: <command/action>` — and a
2682
- one-shot wakeup (~20-30 min) is scheduled when the harness provides one, so the session
2683
- re-checks and auto-continues once the user has acted. An ended turn cannot observe
2684
- external/auth changes by itself; without that line the idle session is indistinguishable
2685
- from a stall. Companion rule: any error (failed command, hook, test, publish) is reported
2686
- verbatim in the same turn, never silently retried past the user.
2687
-
2688
- Decision recorded in `docs/MEMORY.md` with the incident as the reason. Verified: all
2689
- doc-referencing suites 298/298 (incl. the CLAUDE↔AGENTS parity test, which caught the
2690
- first one-sided edit before it could ship), consistency 194/194.
2691
-
2692
- ## 2.3.1 - 2026-09-09
2693
-
2694
- "1 prompt mà đứng 10 lần" is fixed at the root. Four stall vectors in the completion
2695
- gate and router are gone, no stop is silent anymore, and routine backend model swaps
2696
- are now worked through instead of stalled on. All found by root-cause debugging with a
2697
- failing regression test per fix.
2698
-
2699
- 1) Stop-hook recursion: `execution-ledger.mjs --evaluate-stop` re-blocked the reentrant
2700
- Stop event (Claude Code re-invokes Stop with `stop_hook_active: true` after a block), so
2701
- one block became a self-sustaining block/continue chain ending in a cap-forced mid-task
2702
- stop. The gate now honors `stop_hook_active` and, when evidence is still missing, emits
2703
- a user-visible `systemMessage` instead of silently ending.
2704
-
2705
- 2) requestKey churn wiped evidence: `skill-router.sh` rebuilds requestKey per tool call
2706
- (commandText/targetFile are hashed in), so the first verification command re-keyed the
2707
- route mid-request and `--record` took the freshLedger path, erasing the write/verification
2708
- evidence the same request had produced — the gate then re-blocked until the cap forced a
2709
- silent stop. The ledger now keys evidence identity by the user prompt text
2710
- (`promptKey`); a re-key within one logical request carries evidence forward, a genuinely
2711
- new prompt starts clean.
2712
-
2713
- 3) Subagent stalls: subagent tool calls run the same hooks against the same session
2714
- ledger and route state (docs-confirmed; sidechain payloads carry `agent_id`/
2715
- `agent_type`). A subagent's Edit could re-route the request to a different
2716
- executionMode, which both broke the old promptKey identity (wiping main evidence) and
2717
- replaced the main route's completionEvidence. Fixes: promptKey is the prompt text alone
2718
- (null prompt never carries), and `skill-router.sh` early-exits on sidechain payloads so
2719
- subagent tool calls never touch the main route state. omp's bridge invokes the same
2720
- script, so every harness is covered.
2721
-
2722
- 4) No silent endings: the non-gated modes' `notify` and the post-cap `capped` paths now
2723
- emit a `systemMessage` alongside their stderr line — previously these ended turns with
2724
- the user seeing nothing.
2725
-
2726
- Gateway model swaps (limit hit → a different vendor model behind the same alias) are
2727
- detected from the transcript's per-assistant `message.model` and surfaced in
2728
- `context-window-guard.sh` as ONE routine line per hour: keep working, do not restart or
2729
- re-plan; if a tool call errors after a swap, re-check the tool and call it again. The
2730
- swap itself cold-reads the prompt cache once — that latency is transport-level and
2731
- cannot be removed by hooks; everything after it now continues automatically.
2732
-
2733
- Integrated on top of 2.3.0 (rebased; not published as 2.2.17): 2.3.0's stricter gates
2734
- made the re-key carry load-bearing for `targetedVerificationSucceeded`/`sourceFiles`
2735
- too — without carrying them, a mid-request re-key re-demanded targeted evidence and
2736
- re-introduced the stall this release fixes (regression-tested RED→GREEN). The 2.3.0
2737
- notify test that expected a silent stdout was updated to the no-silent-stops contract.
2738
-
2739
- Verified: executionLedgerCli 29/29, skillRouterHook 33/33, contextWindowGuard 18/18;
2740
- full suite 1280/1280 (74 files) and `release:verify` green on the integrated tree;
2741
- template↔live mirrors byte-identical (live settings.json re-rendered through the install
2742
- pipeline, not copied raw).
2743
-
2744
- ## 2.3.0 - 2026-09-08
2745
-
2746
- Model-agnostic hardening release. Every configured model name is treated as a gateway
2747
- mapping whose backend can change at any time, so correctness now comes from stable role
2748
- contracts, explicit evidence, and regression fixtures — never provider identity.
2749
-
2750
- **Sensitive-data gate (fail-closed, default ON).** NEW `sensitive-data-guard.sh` scans
2751
- PreToolUse Read/Grep paths, Bash commands (secret-dump shapes, inline credentials,
2752
- high-confidence token patterns like `sk-…`), and UserPromptSubmit text; on suspicion it
2753
- blocks with exit 2 and shows only redacted previews (3-char prefix + length + sha256
2754
- prefix) — never the value. The only approval path is the USER editing the protected
2755
- allowlist `.ukit/storage/security/allowlist.json` (sha256 of the value, or an allowed file
2756
- path); `security.sensitiveDataGate: true` ships as the default and the gate can be disabled
2757
- in `.ukit/storage/config.json` for debugging. Wired into Claude settings hook chains, the
2758
- omp bridge, and the install manifest. Live-fire verified across all four channels.
2759
-
2760
- **Contract tables unified to one source.** NEW `src/core/executionContracts.js` is the
2761
- canonical table set (execution modes, contracts, contract→tier mapping, risk profiles).
2762
- `taskRouting.js` imports it, runtime config defaults derive from it, and the shipped
2763
- `route-task.mjs` keeps a literal copy locked by a new sync test — fixing a real drift where
2764
- route-task's `local-build` contract was missing verification evidence and the post-edit
2765
- review policy. `config.json` no longer duplicates `modelTier` per contract.
2766
-
2767
- **Tier-role wiring.** Route state now carries a `tierLane` hand-off: silent when the
2768
- contract tier is `code` (the default implementation lane), an explicit "hand this to an
2769
- agent bound to the lite/smart tier" instruction otherwise, and it follows `escalatedTier`
2770
- on repeat failures. This surfaced and fixed a real gap: `compactRouteSummary` is a
2771
- whitelist and was silently dropping `expectedSourceFiles`, which made target-aware
2772
- completion evidence inert on the real CLI path.
2773
-
2774
- **Evidence tightening.** Completion-gate `impact-evidence` now requires reading one of the
2775
- routed target files (any random read no longer counts), and verification receipts record
2776
- `targeted` vs `broad` scope against the routed verification plan; recovery instructions
2777
- name the exact files expected.
2778
-
2779
- **Vision flow smoothing.** Already-analysed images no longer re-trigger route hints
2780
- (`alreadyAnalyzed[]` from `extract-image.mjs --json`); unresolvable image paths get a short
2781
- note instead of a wrong remedy; the vision analyst gets a capability self-check (first
2782
- image Read is the probe), a task envelope carrying the ORIGINAL user prompt verbatim, and
2783
- an observations-vs-inference output block; hook-chain budgets now scale with chain size so
2784
- growing Edit/Write chains never orphan the runner.
2785
-
2786
- **Mapping fingerprint fixtures.** New consistency tests lock agent↔tier bindings across
2787
- Claude Code and omp, the omp modelRoles → `unic-*` labels, and the tier structure
2788
- (vision stays a capability tier outside the escalation ladder) — provider identities are
2789
- deliberately left unpinned so gateway mappings can change freely without breaking
2790
- behavior contracts.
2791
-
2792
- Verified: `yarn test` 1277/1277 (74 files), `test:release-core` 1270, `test:artifact` 7,
2793
- `release:verify` all checks passed, 13/13 handoff node suites, sensitive-data-guard
2794
- live-fire 5/5 as designed.
2795
-
2796
1599
  ## 2.2.1 - 2026-08-22
2797
1600
 
2798
1601
  UKit gains a fourth runtime and loses one. omp (Oh My Pi) reaches full parity with the Claude Code workspace — same agents, same skills, same hooks, same `/ukit:*` commands — and the Antigravity adapter, unused and unmaintained, is gone. The parity is deliberate rather than incidental: the port reuses the existing `.claude/` assets wherever omp's discovery can already reach them, so there is one source of truth per capability, not two that drift.
@@ -2824,4 +1627,4 @@ UKit gains a fourth runtime and loses one. omp (Oh My Pi) reaches full parity wi
2824
1627
 
2825
1628
  **Known gap:** omp was not installed on the machine this release was built on. Every omp assertion in the test suite is against the generated `.omp/` tree and the bridge module's shape — the packed-tarball test confirms `templates/.omp/**` actually publishes, but nothing here observes omp's runtime behaviour. The three open verification items (does omp emit `session_start` on a post-compact continuation; omp's real base-URL key; omp's real auto-compact-window key) are recorded in `docs/AI_HANDOFF/tasks/TASK-008.md`.
2826
1629
 
2827
- Entries for 2.1.0 through 2.2.16 (except 2.2.1) are archived in the repository at `docs/archive/CHANGELOG-2.1.0-2.2.16.md`; entries for 1.0.0 through 2.0.7 at `docs/archive/CHANGELOG-1.0.0-2.0.7.md` (neither is shipped in the npm package).
1630
+ Entries for 3.0.0 through 3.3.3 are archived in the repository at `docs/archive/CHANGELOG-3.0.0-3.3.3.md`. Entries for 2.1.0 through 2.2.16 (except 2.2.1) are archived in the repository at `docs/archive/CHANGELOG-2.1.0-2.2.16.md`; entries for 1.0.0 through 2.0.7 at `docs/archive/CHANGELOG-1.0.0-2.0.7.md` (neither is shipped in the npm package).