{
  "id": "page:docs-release-incident-2026-08-13",
  "_kind": "Page",
  "_file": "wiki/docs/release-incident-2026-08-13.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/release-incident-2026-08-13.md",
    "sourceKind": "repo-docs",
    "title": "Release incident record — stale `latest` dist-tags (2026-08-13)",
    "displayName": "Release incident record — stale `latest` dist-tags (2026-08-13)",
    "slug": "docs/release-incident-2026-08-13",
    "articlePath": "wiki/docs/release-incident-2026-08-13.md",
    "article": "\n# Release incident record — stale `latest` dist-tags (2026-08-13)\n\nStatus: WAVE-0 containment record (remediation program, `fix/remediation-program`)\nIncident IDs: FIX-001 (stale `latest` promotion), with directly observed side findings FIX-002, FIX-004, FIX-005\nRegistry snapshot captured: 2026-08-13 (read-only `npm view` queries; no registry state was mutated to produce this record)\nSnapshot method: for every public workspace package, `npm view <name> dist-tags versions time.modified --json`\n\n## Summary\n\nThe intended production-current release of the babysitter monorepo is **6.0.3** (root `package.json` version on `main` at commit `120926cf0`). Registry observation shows that publication of 6.0.3 partially succeeded but channel promotion did not: **37 of 43** public packages still resolve `latest` to the stale **6.0.0** artifact even though a 6.0.3 artifact exists for them, **5** packages already resolve `latest=6.0.3`, and **1** package (`@a5c-ai/hooks-adapter-genty`) has never been published at all. One additional package (`@a5c-ai/genty-ui`) has no 6.0.3 release version on the registry (only `6.0.3-staging.*` prereleases), so it cannot be promoted to 6.0.3 as-is.\n\nThis split-brain state is the concrete manifestation of FIX-001 in the remediation plan: the release tag path can reassign `latest` to the stale version read from checked-out workspace manifests (which are still 6.0.0) instead of the synchronized release version (6.0.3).\n\n## Why `latest` moved backward\n\n`latest` did not fail to advance — it was actively moved back. Nothing in the pipeline\npublished a wrong artifact; the 6.0.3 tarballs are on the registry and are fine. What\nwent wrong is that **four separate places each answered \"what version are we releasing?\"\nindependently**, and the last one to answer won the dist-tag:\n\n1. `.github/workflows/publish.yml` computed a publish version and synchronized every\n   workspace manifest to it — but only inside a **temporary** publication workspace. The\n   checked-in manifests on `main` stayed at 6.0.0.\n2. `.github/workflows/release-tags.yml` then named the release tag by re-reading the root\n   manifest of the **original** checkout. The tag therefore named a version that was not\n   what had just been published.\n3. That tag triggered `.github/workflows/publish-packages-from-tag.yml`, which\n   re-synchronized manifests only for **staging** tags. A `main` tag was published from\n   the stale checked-in 6.0.0 manifests.\n4. `scripts/publish-package-from-tag.mjs` read each stale workspace manifest, found 6.0.0\n   already on the registry, skipped the publish as a no-op — and then assigned the channel\n   dist-tag to **that** version.\n\nStep 4 is the damage. `npm dist-tag add <pkg>@6.0.0 latest` is a perfectly successful\ncommand; it succeeds just as readily when it moves a channel backward. Nothing compared\nthe version being tagged against the version that had been validated, and nothing checked\nwhether the channel was moving forward, so the pipeline reported a green release while\n`latest` silently regressed for 37 of 43 packages. Consumers running\n`npm install @a5c-ai/<pkg>` after the \"successful\" 6.0.3 release received 6.0.0 —\nincluding the two artifacts with known runtime defects (`@a5c-ai/tasks-adapter@6.0.0`,\nmissing its MCP SDK dependency (FIX-002), and the unusable\n`@a5c-ai/extensions-adapter@6.0.0` tarball (FIX-004)).\n\nThree properties were missing, and all three are now enforced (see the FIX-001 and FIX-010\nstatus sections below):\n\n- **One version, passed explicitly.** `scripts/lib/release-version.cjs` resolves the\n  release version exactly once; every downstream surface receives and validates it instead\n  of re-deriving it. An unknown branch or unparseable tag is a hard error, never a guess.\n- **Publication cannot write a channel.** Publishing writes only the immutable\n  `candidate-<version>` dist-tag. `scripts/release-promotion.cjs promote` is the single\n  channel mutation, and it refuses to run without evidence that this exact version passed\n  clean-consumer validation.\n- **Channels cannot move backward.** `release-version.cjs assert-channel-tags` runs\n  `preflight` before anything is published and `final` over all 43 packages afterwards, so\n  a regression is caught before it can reach a consumer rather than discovered by audit.\n\n### Recovered versions\n\nRecovery does not repair 6.0.3 in place. Existing versions are immutable and are not\nunpublished or overwritten; the fix is a **new patch version** (6.0.4 or later — verify it\nis unused across all 43 packages against a freshly refreshed snapshot) that is published as\na candidate, validated at that exact version from a clean consumer, and only then promoted\nto `latest`. That release also carries the first-ever publication of\n`@a5c-ai/hooks-adapter-genty` and the first `X.Y.Z` release of `@a5c-ai/genty-ui`, the two\npackages the snapshot below shows could not be promoted to 6.0.3 at all. The operator\ncommand sequence is [docs/release-recovery-runbook.md](./release-recovery-runbook.md).\n\n## Containment decisions (in force as of 2026-08-13)\n\n1. **Production promotion is PAUSED.** No automated or manual promotion of any production channel dist-tag (`latest`) may occur until FIX-001 has a passing regression test and the release owner approves the corrected flow. This pause applies to all publish paths: `.github/workflows/publish.yml`, `.github/workflows/publish-packages-from-tag.yml`, `.github/workflows/release-tags.yml`, and any manual `npm dist-tag` invocation.\n2. **No overwrites, no unpublish.** Existing npm versions (including the broken `@a5c-ai/tasks-adapter@6.0.0` and `@a5c-ai/extensions-adapter@6.0.0` artifacts) must NOT be overwritten, unpublished, or force-republished. Recovery goes through a **new patch version** (a version unused across all 43 public packages, i.e. 6.0.4 or later at the time of the recovery release) followed by **explicit dist-tag correction** once the new version passes exact-version clean-consumer validation.\n3. **Registry mutations require explicit approval.** Any `npm publish`, `npm unpublish`, `npm deprecate`, or `npm dist-tag` action against `@a5c-ai/*` is an operational change, not an ordinary code-review step. Each such action requires prior sign-off from the release owner and must be recorded (command, actor, timestamp, result) in this incident record or the recovery release issue.\n4. **Snapshot must be refreshed before recovery.** Registry state is time-sensitive. The table below is authoritative for 2026-08-13 only; re-run the snapshot immediately before executing the recovery release.\n\n## Intended production-current release\n\n- **Intended version: 6.0.3** — the root `package.json` version on `main`.\n- Checked-in workspace package manifests are still mostly `6.0.0` (two exceptions: `@a5c-ai/babysitter-observer-dashboard` and the root manifest are `6.0.3`); manifest synchronization to the release version happens only in temporary publication workspaces. This divergence is the FIX-001 root cause and must be closed before promotion resumes.\n- **Release owner for FIX-001 and the recovery release: Yossi Elkrief** (repository release manager, per the remediation program kickoff).\n\n## Registry snapshot — all 43 public packages\n\nInventory basis: every tracked workspace `package.json` where `private !== true` and `publishConfig.access === \"public\"` (43 packages; this matches the audit count exactly). Coverage is complete — this is a full census, not a sample.\n\nDist-tags observed on the registry were `latest` and `staging` only; no package carried any other dist-tag. All 42 published packages share the same staging tag value, `6.0.3-staging.f5f113c68e2c` (staging prerelease of commit `f5f113c68`).\n\n| Package | Workspace dir | Manifest version | `latest` | `staging` | 6.0.3 on registry | State |\n| --- | --- | --- | --- | --- | --- | --- |\n| `@a5c-ai/adapters` | `packages/adapters/sdk` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/adapters-cli` | `packages/adapters/cli` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/adapters-codecs` | `packages/adapters/codecs` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/adapters-gateway` | `packages/adapters/gateway` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/adapters-harness-mock` | `packages/adapters/harness-mock` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/adapters-observability` | `packages/adapters/observability` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/atlas` | `packages/atlas` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/babysitter` | `packages/babysitter` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/babysitter-observer-dashboard` | `packages/observer-dashboard` | 6.0.3 | 6.0.3 | 6.0.3-staging.f5f113c68e2c | yes | latest already current |\n| `@a5c-ai/babysitter-sdk` | `packages/babysitter-sdk` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/channels-adapter` | `packages/adapters/channels` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/comm-adapter` | `packages/adapters/core` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/config-adapter` | `packages/adapters/config` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/extensions-adapter` | `packages/adapters/extensions` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged; 6.0.0 tarball is known-broken (FIX-004) |\n| `@a5c-ai/genty` | `packages/genty/cli` | 6.0.0 | 6.0.3 | 6.0.3-staging.f5f113c68e2c | yes | latest already current |\n| `@a5c-ai/genty-core` | `packages/genty/core` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/genty-platform` | `packages/genty/platform` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/genty-runtime` | `packages/genty/runtime` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/genty-tui` | `packages/genty/tui` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/genty-ui` | `packages/genty/ui` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | no | stale latest; no 6.0.3 release exists (only 6.0.3-staging.* prereleases) |\n| `@a5c-ai/hooks-adapter-antigravity` | `packages/adapters/hooks/adapter-antigravity` | 6.0.0 | 6.0.3 | 6.0.3-staging.f5f113c68e2c | yes | latest already current |\n| `@a5c-ai/hooks-adapter-claude` | `packages/adapters/hooks/adapter-claude` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-cli` | `packages/adapters/hooks/cli` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-codex` | `packages/adapters/hooks/adapter-codex` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-copilot` | `packages/adapters/hooks/adapter-copilot` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-core` | `packages/adapters/hooks/core` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-cursor` | `packages/adapters/hooks/adapter-cursor` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-gemini` | `packages/adapters/hooks/adapter-gemini` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-genty` | `packages/adapters/hooks/adapter-genty` | 6.0.0 | (absent) | (absent) | no | package has never been published (FIX-005); the hooks CLI's exact pin is deliberately deferred until this package first publishes (`//deferred-dependency` note in `packages/adapters/hooks/cli/package.json`; `adapter-loader.ts` excludes `genty` from `KNOWN_ADAPTERS`, so the CLI does not consume it today) — added as a checklist step of the recovery runbook § 3.8 |\n| `@a5c-ai/hooks-adapter-hermes` | `packages/adapters/hooks/adapter-hermes` | 6.0.0 | 6.0.3 | 6.0.3-staging.f5f113c68e2c | yes | latest already current |\n| `@a5c-ai/hooks-adapter-oh-my-pi` | `packages/adapters/hooks/adapter-oh-my-pi` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-openclaw` | `packages/adapters/hooks/adapter-openclaw` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-opencode` | `packages/adapters/hooks/adapter-opencode` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/hooks-adapter-pi` | `packages/adapters/hooks/adapter-pi` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/kradle` | `packages/kradle/core` | 6.0.0 | 6.0.3 | 6.0.3-staging.f5f113c68e2c | yes | latest already current |\n| `@a5c-ai/kradle-installer` | `packages/kradle/installer` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/launch-adapter` | `packages/adapters/launch` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/policy-adapter` | `packages/adapters/policy` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/tasks-adapter` | `packages/adapters/tasks` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged; 6.0.0 omits its MCP SDK runtime dependency (FIX-002) |\n| `@a5c-ai/tools-adapter` | `packages/adapters/tools` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/transport-adapter` | `packages/adapters/transport` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/triggers-adapter` | `packages/adapters/triggers` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n| `@a5c-ai/trust-core` | `packages/trust-core` | 6.0.0 | 6.0.0 | 6.0.3-staging.f5f113c68e2c | yes | stale latest; 6.0.3 exists but is untagged |\n\nTally: 43 public packages total — 37 stale `latest=6.0.0`, 5 `latest=6.0.3`, 1 never published. 41 packages have a 6.0.3 release version on the registry; `@a5c-ai/genty-ui` and `@a5c-ai/hooks-adapter-genty` do not.\n\n## Recovery plan (requires release-owner approval before execution)\n\nRecovery is Wave 5 of the remediation program and must not begin until FIX-001 (Wave 4) has a passing regression test and Waves 1-3 close the known-broken package artifacts. The recovery release will:\n\n1. Refresh this registry snapshot (npm state is time-sensitive).\n2. Select a new patch version unused across all 43 public packages (6.0.4 or later; verify against the refreshed snapshot).\n3. Build, run all fast checks and the FIX-011 packed-artifact matrix, and publish dependency-ordered candidates under a **non-production** dist-tag — publishing `@a5c-ai/hooks-adapter-genty` for the first time, and before `@a5c-ai/hooks-adapter-cli`.\n4. Validate the exact candidate version via the published-consumer workflow (FIX-010).\n5. Only then move `latest` to the tested exact version via explicit, approved `npm dist-tag` corrections, and assert every public package's channel tag equals that version.\n6. Consider `npm deprecate` notices for the known-broken `@a5c-ai/tasks-adapter@6.0.0` and `@a5c-ai/extensions-adapter@6.0.0` artifacts (separate approval; never unpublish as ordinary remediation).\n\n## FIX-001 remediation status (landed on `fix/remediation-program`)\n\nThe version/dist-tag path described above is now closed in code:\n\n- `scripts/lib/release-version.cjs` + `scripts/release-version.cjs` are the single resolver,\n  validator and channel-assertion surface; `scripts/__tests__/release-version.test.mjs` reproduces\n  this incident as a fixture (root 6.0.3 with 6.0.0 workspace manifests) and proves it now fails.\n- `scripts/publish-package-from-tag.mjs` refuses to publish or dist-tag when the workspace manifest\n  version, the passed release version and the tag version disagree — the exact step that promoted\n  `latest` back to 6.0.0.\n- `.github/workflows/publish.yml` resolves the release version once, verifies the synchronized\n  workspace, refuses backward channel movement before publishing, and asserts every public\n  package's channel tag after publishing.\n- `.github/workflows/release-tags.yml` accepts and validates that version instead of re-reading\n  divergent manifests, and records provenance in the annotated tag.\n- `.github/workflows/publish-packages-from-tag.yml` is recovery-only: it derives the version from\n  the tag, synchronizes every manifest on every channel, skips tags the publish workflow already\n  published from, and publishes in dependency-graph order.\n\n## FIX-010 remediation status (landed on `fix/remediation-program`)\n\nThe recovery sequence above (publish candidates → validate the exact version → promote) is no\nlonger a manual procedure: it is the only path the workflows implement.\n\n- `scripts/publish-package-from-tag.mjs` publishes under the non-production candidate dist-tag\n  `candidate-<version>` and never writes `latest`, `staging` or `develop`.\n- `.github/workflows/live-stack-published.yml` takes the EXACT version as a required\n  `workflow_call` / `workflow_dispatch` input (dist-tags and ranges are rejected), installs that\n  exact version from npm, and records machine-readable validation evidence as a workflow artifact.\n- `scripts/verify-published-release.mjs` installs every public package at the exact version into a\n  clean consumer, imports each root and exported subpath, and smokes every declared bin.\n- `scripts/release-promotion.cjs promote` is the only channel mutation in the pipeline; it refuses\n  to run without evidence that this exact version passed every required check, and re-asserts the\n  channel afterwards.\n- A failed validation therefore leaves the candidate versions installable by exact version and\n  under their candidate tag for diagnosis, with the channel still on the previous release.\n\nRegistry recovery itself (Wave 5) is unchanged and still requires release-owner approval. The\nexact command sequence the release owner must run — candidate publication, published-consumer\nvalidation of the exact version, channel promotion, full-inventory channel assertion, and the\nseparately approved `npm deprecate` notices for the known-broken 6.0.0 tasks/extensions artifacts —\nis documented in [docs/release-recovery-runbook.md](./release-recovery-runbook.md), together with\nthe Wave 5 local candidate rehearsal evidence.\n\n## Containment exit criteria status\n\n- [x] Production promotion pause is documented and in force (this record). Operational enforcement in CI/GitHub settings (e.g. environment protection on the publish workflows) is a release-owner action tracked for FIX-001.\n- [x] The intended release version (6.0.3) is documented.\n- [x] A release owner is assigned to FIX-001 and the final recovery release (Yossi Elkrief).\n- [x] Current versions and dist-tags for every public package are recorded (full 43-package census above; not a sample).\n- [x] Recovery is planned through a new patch version and explicit dist-tag correction; no overwrite or unpublish of existing versions.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs",
      "to": "page:docs-release-incident-2026-08-13",
      "kind": "contains_page"
    }
  ]
}