codex-workflow-v2 2.0.0-beta.12.10 → 2.0.0-beta.12.11

package/docs/delegated-approval.md

@@ -90,7 +90,7 @@ uses the grant and passes `--delegation-grant` to the Core transition.
 
 Ordinary semantic Milestone scope changes remain journaled, human-only lifecycle actions. A
 contract delegate may evolve only the membership graph inside the cryptographically bound
-semantic scope. The separate beta.12.10 `milestone remediation-materialize` route is not delegation
+semantic scope. The separate beta.12.11 `milestone remediation-materialize` route is not delegation
 and does not widen this allow-list: Core derives it only from a current blocking Plan Risk Audit and
 a previously authorized active Milestone. Its topology effect is fixed to one new required upstream
 Task plus one dependency edge, with all Milestone semantics preserved. The resulting

package/docs/pdf/sources/codex-workflow-v2-architecture-ru.md

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: архитектура beta.12.10
+title: Codex Workflow V2: архитектура beta.12.11
 subtitle: Источники истины, lifecycle, роли, delegation, зависимости Tasks и границы доверия
 part: Часть 1 из 3 | Архитектура
 document_version: 2.0
 date: 31 августа 2026
-subject: Архитектура и границы Codex Workflow V2 beta.12.10
+subject: Архитектура и границы Codex Workflow V2 beta.12.11
 ---
 
 # 1. Назначение и граница системы
@@ -18,7 +18,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
 Система рассчитана на одного пользователя и одну машину. Она не предоставляет distributed locking,
 криптографическую идентификацию actor string или безопасную синхронизацию state между компьютерами.
 
-## 1.1. Что beta.12.10 гарантирует
+## 1.1. Что beta.12.11 гарантирует
 
 - exact project-local npm package и совместимый handshake до lifecycle действий;
 - Discovery до materialization Task или Milestone;
@@ -41,7 +41,7 @@ Codex Workflow V2 - локальный state machine поверх Codex App, Git
   один additive remediation Task без нового Human gate; Core сохраняет Milestone semantics и выводит
   authority из текущей Milestone authorization и exact audit evidence.
 
-## 1.2. Что beta.12.10 не гарантирует
+## 1.2. Что beta.12.11 не гарантирует
 
 - правильность продуктовой идеи или автоматически выбранного provider Task;
 - semantic sufficiency Plan, если точные факты нельзя доказать поддерживаемым analyzer;
@@ -296,7 +296,7 @@ beta.12.9 закрывает исторический provenance gap corrective
 регистрирует dependency и historical authority одной revision. Оба пути сохраняют dirty bytes текущего
 Step, не переписывают Git и завершаются fresh обычным `step-complete` flow.
 
-beta.12.10 закрывает иной класс тупика до начала выполнения. Если current Plan Risk Audit required Task
+beta.12.11 закрывает иной класс тупика до начала выполнения. Если current Plan Risk Audit required Task
 записал `stop-escalate`, потому что нужной upstream capability нет в scope этой Task, Core рекламирует
 audited remediation. Coordinator сначала формализует capability обычным Discovery. Затем одна Project
 transaction append-only создаёт required remediation Task на exact merged predecessor frontier исходной
@@ -307,6 +307,13 @@ memberships. Scope-change event связан с Task revision, Brief/Plan и aud
 обычный Plan, audit, C1, commits и reviews. После её merge исходная Task обязана заменить отвергнутый Plan,
 пройти fresh audit и продолжить Step. Final Milestone acceptance не выводится автоматически.
 
+Dependency-only update не должен создавать промежуточный Human gate. Если stale Knowledge отличается
+только content hash `package.json`, все package surfaces уже равны runtime version, checkout clean, а
+каждый Git commit, менявший `package.json` после approved hash, затрагивает ровно manifest/lock и только
+Workflow pin, Core переносит reconcile и `corrective-derived` approval внутрь той же atomic remediation
+transaction. Изменение любого другого Knowledge source, classification, gap или conflict fail-closed
+остаётся в обычном явном approval flow.
+
 Docker socket `EPERM` в sandbox не является доказательством сломанного daemon. Gateway один раз
 повторяет exact health probe или Plan check с sandbox escalation без расходования remediation attempt.
 Restart Docker Desktop требует отдельного разрешения и допустим только после escalated daemon failure.
@@ -316,7 +323,7 @@ Restart Docker Desktop требует отдельного разрешения
 # 10. Operational checklist
 
 - exact package version установлен, bundled gateway соответствует release и переустановлен;
-- handshake подтверждает protocol 2, state schema 2 и beta.12.10 capabilities;
+- handshake подтверждает protocol 2, state schema 2 и beta.12.11 capabilities;
 - каждый mutation следует свежему `status -> next` и exact option contract;
 - Docker permission failure сначала классифицируется как sandbox boundary, а не как infra retry;
 - semantic unknowns и human gates не маскируются delegation;

package/docs/pdf/sources/codex-workflow-v2-chat-only-guide-ru.md

@@ -1,13 +1,13 @@
 ---
 title: Codex Workflow V2: delegated chat-only guide
-subtitle: Актуальный beta.12.10 путь от нового Discovery до принятого Milestone без ручного CLI
+subtitle: Актуальный beta.12.11 путь от нового Discovery до принятого Milestone без ручного CLI
 part: Часть 2 из 3 | Практика
 document_version: 2.0
 date: 31 августа 2026
-subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.10
+subject: Практическое руководство по delegated Discovery и Milestone в Workflow V2 beta.12.11
 ---
 
-# 1. Рабочая модель beta.12.10
+# 1. Рабочая модель beta.12.11
 
 Пользователь работает в одном Codex Project и формулирует продуктовый outcome. Coordinator выполняет
 CLI, создаёт отдельные Task/Reviewer chats и ведёт supervision loop. Workflow Core остаётся authority
@@ -40,7 +40,7 @@ Blocking unknown, scope change, grant issuance или unrecoverable integrity co
 # 2. Подготовка проекта перед новым Discovery
 
 1. Убедитесь, что checkout чистый и выбран правильный repository root.
-2. Установите beta.12.10 как точную devDependency после публикации release.
+2. Установите beta.12.11 как точную devDependency после публикации release.
 3. Обновите и переустановите bundled `codex-workflow-gateway` этого release.
 4. Проверьте, что declared и installed package versions равны.
 5. Запустите новый Coordinator chat, не fork старого Milestone conversation.
@@ -56,7 +56,7 @@ AGENTS.md
 -> doctor только как дополнительная диагностика
 ```
 
-Handshake beta.12.10 должен сообщать `packageVersion=2.0.0-beta.12.10`, `protocolVersion=2`,
+Handshake beta.12.11 должен сообщать `packageVersion=2.0.0-beta.12.11`, `protocolVersion=2`,
 `stateSchemaVersion=2`, dependency DAG, initial Plan transaction, mechanical feasibility,
 Milestone autonomy и structural replacement disabled capabilities.
 
@@ -117,7 +117,7 @@ delegate, scope, transitions и expiry. DGR передаётся только е
 ```text
 НОВЫЙ COORDINATOR CHAT
 
-Проведи новый Milestone через Codex Workflow V2 beta.12.10 в delegated режиме.
+Проведи новый Milestone через Codex Workflow V2 beta.12.11 в delegated режиме.
 Repository: <ABSOLUTE-REPOSITORY-ROOT>.
 Milestone ID: AUTO.
 Delegate actor: agent:milestone-coordinator.
@@ -315,7 +315,7 @@ Task chat записывает его только при совпадении p
 Plan-integrity recovery не редактирует Plan, package.json или worktree и не синтезирует второй failure.
 P04-A не переносит completed Steps и не rewires dependencies при split.
 
-Audited remediation beta.12.10 не является generic scope-change. Coordinator использует только exact
+Audited remediation beta.12.11 не является generic scope-change. Coordinator использует только exact
 route из fresh `next`: создаёт Discovery для доказанной отсутствующей upstream capability, доводит его
 до ready и вызывает `milestone remediation-materialize` с текущими revisions и exact
 `requiredPredecessorTaskIds`. Core не принимает новый Milestone Plan: сохраняет outcome/success signal,
@@ -326,6 +326,13 @@ acceptance/checks и старые memberships, append-only добавляет о
 Audit и как минимум следующему Step. Dirty checkout, lease/transaction, stale audit, started Task,
 неполный predecessor frontier или повторное использование audit означают hard stop.
 
+После обновления package fresh `next` может добавить
+`auditedRemediation.dependencyKnowledgeRefresh`. Продолжайте без Human approval только при
+`eligible=true`: Core доказал clean checkout, exact aligned version surfaces, единственный изменённый
+Knowledge path `package.json` и dependency-only Git chain. Refresh будет применён атомарно во время
+`milestone remediation-materialize`. Если объект отсутствует или содержит blockers, не маскируйте
+документационный/product drift под update — используйте обычный Project Knowledge flow.
+
 `task downstream-proof-recover` также не редактирует product files и не создаёт новую Task. Он сохраняет
 dirty worktree/HEAD, append-only фиксирует invalidated predecessor evidence, освобождает C1 и возвращает
 текущую Task к `task plan-set`. Если fresh `next` не рекламирует этот переход, вызывать его нельзя.
@@ -375,7 +382,7 @@ Task/project DGR. `dependencyBinding` для standalone handoff равен null.
 
 # 14. Итоговый checklist пользователя
 
-- beta.12.10 exact package и новый bundled gateway установлены;
+- beta.12.11 exact package и новый bundled gateway установлены;
 - новый Coordinator chat не является fork старого Milestone;
 - bootstrap DGR, если нужен, выдан отдельным exact human confirmation;
 - Discovery не materialized при blocking unknowns;

package/docs/pdf/sources/codex-workflow-v2-technical-reference-ru.md

@@ -1,10 +1,10 @@
 ---
-title: Codex Workflow V2: технический справочник beta.12.10
+title: Codex Workflow V2: технический справочник beta.12.11
 subtitle: Protocol 2, state schema 2, transactions, credentials, dependency authority, review и recovery
 part: Часть 3 из 3 | Technical reference
 document_version: 2.0
 date: 31 августа 2026
-subject: Технический контракт Codex Workflow V2 beta.12.10
+subject: Технический контракт Codex Workflow V2 beta.12.11
 ---
 
 # 1. Runtime contract
@@ -13,9 +13,9 @@ Workflow V2 предоставляет локальные revisioned transitions
 и `value` либо структурированную ошибку с `code`, `message` и `details`. Chat, PDF и gateway не создают
 authority сами: mutating permission определяется runtime state и свежим `next`.
 
-| Параметр beta.12.10 | Значение |
+| Параметр beta.12.11 | Значение |
 |---|---|
-| npm package | `codex-workflow-v2@2.0.0-beta.12.10` |
+| npm package | `codex-workflow-v2@2.0.0-beta.12.11` |
 | protocolVersion | 2 |
 | stateSchemaVersion | 2 |
 | lifecycle epoch | 2 |
@@ -37,7 +37,7 @@ Gateway выполняет:
 5. вызов только package-local `dist/src/cli.js --repo <root>`;
 6. `gateway handshake` до lifecycle действий.
 
-Ключевые beta.12.10 capabilities:
+Ключевые beta.12.11 capabilities:
 
 | Группа | Capabilities |
 |---|---|
@@ -402,7 +402,7 @@ exact `HEAD^`/`HEAD`, package/version surfaces и SHA-256 dirty worktree. Recove
 update-route, dependency provenance в одной Task revision. Fresh `status -> next` после transition
 должен вернуть обычный credential/`task step-complete` flow текущего Step.
 
-# 13.4. beta.12.10 audited remediation topology
+# 13.4. beta.12.11 audited remediation topology
 
 `milestone remediation-materialize` применим только к required Task в
 `awaiting_execution_authorization`, если ни один Step не начат и последний audit текущей
@@ -435,6 +435,16 @@ Current Milestone execution authorization superseded и заменён `correcti
 mechanical feasibility, C1, Step checks/commits/reviews и final Milestone acceptance не меняются.
 После merge remediation Task исходная Task получает `task plan-set` и проходит fresh audit/authority.
 
+Если перед этим exact package update сделал Knowledge Map stale, navigation может вернуть
+`auditedRemediation.dependencyKnowledgeRefresh`. Eligibility требует: ранее active approved map;
+inspected status `stale`; единственный изменённый Knowledge path `package.json`; clean checkout;
+runtime/declared/locked/installed/HEAD/Milestone-base version равны; approved package content найден в
+Git ancestry; каждый последующий commit, трогавший manifest, меняет ровно `package.json` и
+`package-lock.json`, причём после удаления `codex-workflow-v2` обе JSON-структуры совпадают с parent.
+Materialization тогда дополнительно пишет active Knowledge Map с revision +2 и approval mode
+`corrective-derived` в той же Project transaction. Это не разрешает автоматически принимать README,
+docs, commands, classification, authority, gaps или conflicts.
+
 # 14. P04-A structural replacement boundary
 
 Command shape `task replacement-materialize` retained только для compatibility diagnostics. Любая попытка
@@ -497,7 +507,7 @@ Docker socket/CLI `EPERM`, `operation not permitted` или `permission denied`
 После каждой successful mutation обязателен sequential `status`, затем fresh `next`. Failed status/next
 не разрешает direct mutation. Syntax help read-only и не заменяет navigation authority.
 
-# 18. Public command surface beta.12.10
+# 18. Public command surface beta.12.11
 
 | Область | Actions |
 |---|---|
@@ -525,7 +535,7 @@ running Step и active/stale writer lease. Исключения — докуме
 active-downstream-proof bridge, beta.12.7 exact stranded-replan bridge и beta.12.9 historical-Step
 dependency bridge; все они fail-closed и не дают общего разрешения dirty update.
 
-Перед beta.12.10 tag обязательны `npm ci`, `npm run validate`, `npm run test:signal-remediation-e2e`, `npm run pack:check`,
+Перед beta.12.11 tag обязательны `npm ci`, `npm run validate`, `npm run test:signal-remediation-e2e`, `npm run pack:check`,
 `npm run smoke:downstream`, `npm run plugin:check`, official plugin/skill validators,
 `npm run docs:pdf:check`, `npm run release:check` с exact tag binding и validation
 append-only real-agent lifecycle log.

package/docs/release.md

@@ -28,7 +28,7 @@ The PDF check deterministically regenerates all three Russian documents from
 `docs/pdf/sources`, binds the visible package version to the root manifest, and fails when any
 tracked PDF is stale. Source and binary PDFs are one release unit.
 
-For beta.12.10, the release gate also relies on `npm run release:check` to fail if:
+For beta.12.11, the release gate also relies on `npm run release:check` to fail if:
 
 - canonical entity schema 2 shapes drift;
 - protocol 2 is not the active public contract, or intact protocol-1 adoption evidence stops being readable through the bounded compatibility window;

package/docs/updating-existing-project.md

@@ -22,12 +22,12 @@ state schema. Совпадение `stateSchemaVersion` до и после об
 нужна. Для alpha.6 при `stateSchemaVersion: 2` применяется не migration, а sidecar-only
 adoption posture.
 
-### beta.12.10: audited remediation вместо ручной смены Milestone scope
+### beta.12.11: audited remediation и dependency-only Knowledge refresh
 
 После безопасного обновления существующий active Milestone может продолжить работу без пересоздания,
 если current `next` показывает pre-execution `stop-escalate` и объект `auditedRemediation`. Это не
 update compatibility bridge и не разрешение вручную менять state. Сначала выполните обычный
-`update preflight`; установите exact beta.12.10 только при `safe=true`, clean checkout, отсутствии
+`update preflight`; установите exact beta.12.11 только при `safe=true`, clean checkout, отсутствии
 running Step и leases, затем снова выполните repository-local handshake, `status` и `next`.
 
 Далее следуйте только свежему route: remediation Discovery -> ready ->
@@ -40,6 +40,14 @@ repository priority и пройти обычную реализацию/review/m
 вернуться к `task plan-set`, fresh Risk Audit и следующему Step. Если fresh `next` не рекламирует этот
 контракт, не вызывайте команды напрямую и не редактируйте Milestone state.
 
+Если exact dependency-only update сделал approved Knowledge Map stale только по `package.json`,
+`auditedRemediation.dependencyKnowledgeRefresh` должен подтвердить clean checkout, aligned
+declared/locked/installed/HEAD/base versions и полную Git-цепочку commits, меняющих только Workflow pin
+в `package.json`/lock. Такой content refresh не требует Human approval: он применяется в той же Project
+transaction, что и `milestone remediation-materialize`, с `corrective-derived` evidence. Любой другой
+Knowledge diff (включая README, документацию, classification, gap или conflict) не допускается в этот
+маршрут и остаётся в обычном reconcile/approval flow.
+
 ### Исключение для lifecycle-дедлока alpha.6
 
 Обычный `update preflight` намеренно блокирует обновление при `in_progress` Step. Если alpha.6

package/docs/validation-report.md

@@ -1,105 +1,113 @@
-# V2 beta.12.10 Validation Report
+# V2 beta.12.11 Validation Report
 
-Release candidate `2.0.0-beta.12.10` was validated on 2026-08-31 (Europe/Moscow) with
+Release candidate `2.0.0-beta.12.11` was validated on 2026-08-31 (Europe/Moscow) with
 Node.js 24.17.0.
 
 ## Automated release evidence
 
-- `npm ci` completed from the exact lockfile with 0 reported vulnerabilities.
-- `npm run validate` passed typecheck and `344/344` sequential tests with no failures, skips,
-  cancellations, or todos in 2,087,253.659208 ms.
-- `npm run test:signal-remediation-e2e` passed the focused Signal-shaped end-to-end scenario.
-  The test starts from an active Milestone whose required Task has a current `stop-escalate` Plan
-  Risk Audit, materializes one audited upstream remediation Task, completes its Plan/audit/C1/Step/
-  review/accept/merge lifecycle, replans the original Task, and completes a later Step there.
-- Negative coverage rejects a non-exact predecessor frontier, duplicate remediation, stale revisions,
-  non-required or non-active Milestone posture, topology drift, reused audit evidence, and ordinary
-  standalone/post-execution `stop-escalate` cases that must keep the existing `task plan-set` route.
-- The complete lifecycle inventory names `milestone remediation-materialize` and
-  `WorkflowService.materializeAuditedRemediationTask`; read-only purity, transaction rollback/
-  roll-forward, concurrent writers, credentials, Core receipts and prior Signal compatibility tests
-  all passed.
-- Package dry-run produced `codex-workflow-v2-2.0.0-beta.12.10.tgz` with 278 files, 1,050,219 bytes
-  packed and 4,196,113 bytes unpacked. The broad `docs` package allowlist was narrowed so the
-  repository-local `docs/quality` observation journal cannot enter the tarball. The first invocation
-  encountered a root-owned user npm cache (`EPERM`); the exact retry used an isolated temporary cache.
+- `npm ci` completed from the exact lockfile. No dependency version changed outside the release pin.
+- `npm run validate` passed typecheck and `345/345` sequential tests with no failures, skips,
+  cancellations, or todos in 1,974,837.33 ms.
+- `npm run test:signal-remediation-e2e` passed two focused scenarios. The positive E2E starts with an
+  approved Knowledge Map bound to beta.12.9, commits an exact dependency-only update to beta.12.11,
+  proves the stale map from Git and all version surfaces, materializes an audited upstream remediation
+  Task, completes its Plan/audit/C1/Step/review/accept/merge lifecycle, replans the original Task, and
+  completes a later Step there. The negative E2E changes README and proves that unrelated Knowledge
+  drift is not auto-approved while standalone reconcile remains executable.
+- Existing negative coverage still rejects non-exact predecessor frontiers, duplicate remediation,
+  stale revisions, non-required or non-active Milestone posture, topology drift, reused audit evidence,
+  unsafe Knowledge paths, classification/gap/conflict drift, dirty checkouts, unaligned package
+  surfaces and wider Git commits.
+- Package dry-run produced `codex-workflow-v2-2.0.0-beta.12.11.tgz` with 278 files, 1,057,906 bytes
+  packed and 4,224,300 bytes unpacked. The tarball excludes repository-local `docs/quality`. The first
+  invocation encountered a root-owned user npm cache (`EPERM`); the exact retry passed with an isolated
+  temporary cache.
 - `npm run smoke:downstream` built and installed the tarball in a disposable consumer project and
-  returned `ok=true`. The sandboxed attempt could not resolve npm (`ENOTFOUND`); the same command
-  passed with network access.
-- `npm run plugin:check` passed for bundled gateway
-  `0.1.0+codex.20260830183000`.
-- `npm run docs:pdf:check` reported an empty stale set and exact beta.12.10 package binding.
-- `RELEASE_TAG=v2.0.0-beta.12.10 npm run release:check` and `git diff --check` passed after this
-  report and the exact package allowlist were recorded.
-
-## Root cause corrected by beta.12.10
-
-An active Milestone could reach a genuine pre-execution dead end when a required Task's current Plan
-Risk Audit truthfully returned `stop-escalate` because an upstream capability did not exist. The old
-choices were insufficient: replanning the same Task could not manufacture the missing capability,
-while the generic scope-change path required a separate human approval and permitted a much wider
-semantic change than the evidence justified.
-
-The problem was missing bounded topology authority, not an insufficient number of implementation or
-review attempts. Repeating the blocked Task could only reproduce the same unmet prerequisite.
+  returned `ok=true`. The sandboxed attempt could not resolve npm (`ENOTFOUND`); the same command passed
+  with network access.
+- `npm run plugin:check` passed for bundled gateway `0.1.0+codex.20260830183000`.
+- `npm run docs:pdf:check` reported an empty stale set and exact beta.12.11 package binding.
+- `RELEASE_TAG=v2.0.0-beta.12.11 npm run release:check` and `git diff --check` passed.
+
+## Root causes corrected
+
+beta.12.10 added the bounded audited-remediation topology for a required pre-execution Task whose
+current Plan Risk Audit truthfully returned `stop-escalate` because an upstream capability was absent.
+Real installation in Signal exposed a second deadlock before that route could run:
+
+1. the dependency-only package commit changed the approved `package.json` content hash;
+2. repository `next` correctly observed stale Project Knowledge and advertised standalone reconcile;
+3. standalone reconcile tried to discover a delegated Task context owner;
+4. the same blocking Plan Risk Audit rejected that inspection, so the advertised transition could not
+   execute; and
+5. even an ordinary reconcile would have required a Human approval and Task rebind that invalidated the
+   exact audit binding needed by remediation.
+
+The primary defect was incomplete composition between package update, Knowledge authority and audited
+remediation, not an insufficient retry count. A one-command bypass or broad auto-approval would have
+hidden unreviewed product/documentation changes.
 
 ## Implemented lifecycle contract
 
-- Fresh `next` advertises audited remediation only for an `awaiting_execution_authorization`
-  required Task of an active Milestone with a current `stop-escalate` Plan Risk Audit. Standalone,
-  post-execution, `split-required`, and other stop postures preserve their existing routes.
-- Coordinator first records a normal capability Discovery. `milestone remediation-materialize`
-  then performs one project transaction that appends exactly one required remediation Task and adds
-  exactly one dependency edge from the blocked Task to it.
-- The new Task must inherit the blocked Task's exact direct predecessor frontier, and every predecessor
-  must already be merged. Milestone outcome, success signal, acceptance, checks, base, old memberships
-  and all unrelated dependency edges remain byte-semantically unchanged.
-- The scope-change event binds Milestone revision, blocked Task revision, Brief/Plan hashes, exact Plan
-  Risk Audit event/hash, remediation Discovery revision, new Task identity and predecessor frontier.
-  Reuse or topology drift fails closed.
-- A `corrective-derived` authorization, bound to the audited evidence and exact actor
-  `agent:milestone-remediation:<MS-ID>`, replaces the superseded Milestone execution authorization.
-  It authorizes only current required Task execution acceptance transitions; it is neither a general
-  delegation grant nor human impersonation.
-- The remediation route requires no human approval. After its Task merges, the original Task returns
-  to `task plan-set`, must receive a semantically new Plan and fresh Plan Risk Audit, and then proceeds
-  through the ordinary C1, checks, commits and reviews.
-- Public handshake capabilities include `audited-remediation-topology-v1` and
-  `corrective-derived-task-authority-v1`.
+- Fresh `next` advertises audited remediation only for an unstarted
+  `awaiting_execution_authorization` required Task of an active Milestone with a current
+  `stop-escalate` Plan Risk Audit.
+- When Project Knowledge is stale, the route continues without a Human gate only if Core proves all of
+  the following: the previously stored map is active and approved; the sole changed Knowledge path is
+  `package.json`; checkout is clean; runtime, declared, locked, installed, HEAD and Milestone-base
+  versions equal; the approved manifest bytes exist in current Git ancestry; and every subsequent
+  commit that touched `package.json` changed exactly `package.json` and `package-lock.json` with no
+  structural difference after removing the Workflow dependency.
+- `next.auditedRemediation.dependencyKnowledgeRefresh` exposes the evidence and blockers without writes.
+  Discovery start/update stays available only when this assessment is eligible.
+- `milestone remediation-materialize` atomically writes the consumed Discovery, one required remediation
+  Task, additive Milestone topology, scope-change evidence and—when required—the reconciled active
+  Knowledge Map at revision +2 with `corrective-derived` approval. No actor, confirmation code,
+  delegation grant or Human approval is accepted.
+- The new Task inherits the blocked Task exact direct predecessor frontier. Milestone outcome, success
+  signal, acceptance, checks, base, old memberships and unrelated dependency edges remain unchanged.
+- The corrective-derived actor remains `agent:milestone-remediation:<MS-ID>` and authorizes only the
+  advertised required Task execution/final-acceptance transitions. Final Milestone acceptance remains
+  an ordinary Human/delegated gate.
+- After remediation merge, the original Task returns to `task plan-set`, receives a fresh Knowledge
+  binding, Plan and Risk Audit, then proceeds through ordinary C1, checks, commits and reviews.
+- Unsafe or unrelated Knowledge drift never enters this route. Standalone reconcile now remains
+  executable instead of throwing while it checks whether a blocked Task can own delegated refresh;
+  subsequent explicit approval semantics are unchanged.
+- Handshake adds `audited-remediation-dependency-knowledge-refresh-v1` while protocol and state schema
+  remain `2/2`.
 
 ## Signal-shaped evidence
 
-The release E2E mirrors the observed Signal deadlock: four already merged provider Tasks, one blocked
-required consumer Task, a current pre-execution `stop-escalate` audit, and a missing upstream
-capability. It proves the entire recovery cycle rather than only the new materialization command.
+The focused E2E reproduces the real post-install boundary, including an older approved manifest hash,
+an exact package/lock update commit, a stale Knowledge observation, an active Milestone, one blocked
+required consumer and the later ordinary Step. It proves the complete continuation rather than only
+the Knowledge assessment or materialization command.
 
-Live Signal installation and mutation are intentionally separate post-publication actions. They must
-use exact repository-local beta.12.10, a clean/idle update boundary, fresh `status -> next`, and the
-advertised compatibility/recovery route if the dependency update advances active Milestone base
-state. No manual state edit, Git history rewrite, Task cancellation, or duplicate Milestone is part of
-the release mechanism.
+Live Signal installation and mutation remain post-publication actions. They must install exact
+repository-local beta.12.11, commit only package/lock, run sequential handshake/status/next, follow the
+advertised audited-remediation route and confirm Core readback. No manual state edit, Git history
+rewrite, Task cancellation or duplicate Milestone is part of the recovery.
 
 ## PDF release documentation evidence
 
-- All three tracked Russian PDFs were regenerated from beta.12.10 Markdown sources.
+- All three tracked Russian PDFs were regenerated from beta.12.11 Markdown sources.
 - Architecture is 8 pages, the delegated chat-only guide is 10 pages, and the technical reference is
-  12 pages. All 30 pages were rendered and visually inspected; the changed recovery sections were
-  checked at full-page resolution.
-- Titles, package bindings, Cyrillic text, tables, code blocks, margins, footers and section transitions
-  have no visible clipping, overlap or unreadable content.
+  13 pages. All 31 pages were rendered to PNG and visually inspected.
+- Titles, package bindings, Cyrillic text, tables, code blocks, margins, footers and the new
+  dependency-Knowledge sections have no visible clipping, overlap or unreadable content.
 
 ## Existing boundaries and non-claims
 
-- The new route does not permit arbitrary Task insertion, task removal, semantic Milestone scope
-  change, arbitrary dependency rewiring, completed-Step adoption or `split-required` replacement.
-- Human approval is removed only from this exact evidence-derived corrective topology transition.
-  Final Milestone acceptance and generic semantic scope changes retain their existing authority model.
-- Protocol version remains 2 and state schema remains 2; older projects remain readable without a
-  state migration.
-- No Git commit, tag, remote push, npm publication or live Signal recovery is claimed by this
-  pre-publication report.
-
-Confidence is high for the package implementation, topology invariants, no-human corrective authority,
-regression compatibility, tarball composition, downstream installation, plugin and documentation.
-Live Signal confidence remains conditional on successful publication, exact dependency installation,
-fresh Core readback and Coordinator completion of the advertised remediation route.
+- The route does not permit arbitrary Task insertion, Task removal, semantic Milestone scope change,
+  arbitrary dependency rewiring, completed-Step adoption or `split-required` replacement.
+- It does not auto-approve README, documentation, commands, classifications, authorities, gaps,
+  conflicts, dirty files or package commits containing any non-Workflow change.
+- Protocol version remains 2 and state schema remains 2; no state migration is required.
+- This report does not claim Git tag/push, npm publication or live Signal recovery before those
+  post-gate operations are read back separately.
+
+Confidence is high for the package implementation, bounded no-Human dependency Knowledge refresh,
+transaction atomicity, regression compatibility, tarball composition, downstream installation,
+gateway and documentation. Live Signal confidence remains conditional on exact publication,
+installation and fresh Core/Coordinator readback.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-v2",
-  "version": "2.0.0-beta.12.10",
+  "version": "2.0.0-beta.12.11",
   "description": "Requirements-first Codex development workflow with local state and explicit Git ownership.",
   "repository": {
     "type": "git",

package/plugins/codex-workflow-gateway/skills/codex-workflow-gateway/SKILL.md

@@ -156,6 +156,16 @@ free-form Milestone scope change. Follow only the advertised route:
    record a fresh Risk Audit, use the same current derived approval only when advertised, and
    continue through at least the next ordinary Step boundary.
 
+An exact package update may make the approved Knowledge Map stale while this route is active. Continue
+without a Human approval only when fresh `next` includes
+`auditedRemediation.dependencyKnowledgeRefresh.eligible=true`. Core must prove that `package.json` is
+the sole changed Knowledge source, every version surface equals the repository-local runtime, and every
+Git commit that changed the approved manifest content altered only the exact Workflow dependency in
+`package.json`/`package-lock.json`. Do not run standalone reconcile first. The refresh is committed
+atomically by `milestone remediation-materialize` with corrective-derived evidence. Any other Knowledge
+path, classification, gap, conflict, dirty checkout, unaligned version or wider commit returns to the
+ordinary explicit Knowledge flow.
+
 This is an idempotent, additive topology transition bound to one exact Plan Risk Audit. Dirty Git,
 any lease/transaction/Core operation, a started blocked Task, stale Task/Milestone/audit bindings,
 non-merged or non-exact predecessors, duplicate use of the audit, or any changed Milestone semantic