codex-workflow-v2 2.0.0-beta.11 → 2.0.0-beta.12

package/docs/validation-report.md

@@ -1,124 +1,98 @@
-# V2 beta.11 Validation Report
+# V2 beta.12 Validation Report
 
-Release candidate `2.0.0-beta.11` was validated on 2026-08-24 with Node.js 24.17.0.
+Release candidate `2.0.0-beta.12` was validated on 2026-08-27 with Node.js 24.17.0.
 
 ## Automated release evidence
 
 - `npm ci` completed from the committed lockfile with 0 reported vulnerabilities.
-- The final `npm run validate` passed `319/319` sequential tests with no failures, skips,
-  cancellations, or todos. The focused Signal recovery suite passed independently (`5/5`).
-- `npm run pack:check` passed. The beta.11 tarball contains 269 files; package size is approximately
-  951 kB and unpacked size is 3.7 MB.
-- `npm run smoke:downstream` packed and installed the actual beta.11 tarball in an empty temporary
+- The final `npm run validate` passed `321/321` sequential tests with no failures, skips,
+  cancellations, or todos. The focused Signal T04 recovery suite passed independently (`5/5`).
+- `npm run pack:check` passed outside the filesystem-restricted sandbox. The beta.12 tarball
+  contains 269 files; package size is 955.6 kB and unpacked size is 3.7 MB.
+- `npm run smoke:downstream` packed and installed the actual beta.12 tarball in an empty temporary
   project, then passed the packaged CLI handshake. The first sandboxed attempt was network-blocked
-  while fetching `ajv`; the authorized network retry and the final post-`npm ci` run passed.
-- `npm run plugin:check`, the plugin-creator structural validator, the skill validator,
-  `npm run docs:pdf:check`, `npm run release:check`, and `git diff --check` passed. The bundled
-  gateway cachebuster is `0.1.0+codex.20260824113210`.
-
-## Bounded Plan-integrity recovery evidence
-
-- Recovery becomes applicable only after the first ordinary `checks-failed` remediation for a
-  guarded failed Step when at least one Plan check is an exact root `npm run[-script] <name>`
-  command whose named script is absent from the root `package.json`, and that manifest is outside
-  the Step's exact `allowedWrites` boundary.
-- Fresh evidence binds the Task revision, first remediation event ID/hash, current Plan and Step
-  definition, root manifest path/hash, Git HEAD, exact check commands, missing script names, and
-  current dirty-file set into one canonical conflict hash.
-- An eligible `next` advertises only `task plan-integrity-recover`. The mutation appends one
-  schema-validated `replan-required` corrective decision and does not modify the worktree or invent
-  a second failed execution attempt.
-- Existing C1 ownership remains authoritative. A claimed Worker must execute the advertised
-  recovery and then yield its claim before the existing journaled, Human-gated corrective-replan
-  transition can prepare replacement Plan authority.
-- The route fails closed when `package.json` is writable by the Step, no missing-script check
-  matches the bounded npm-script grammar, unrelated dirty files exist, bindings drift, or
-  persisted evidence is malformed or tampered.
-
-## Regression coverage
-
-- Four dedicated beta.11 regressions cover the exact happy path, the in-scope-manifest exclusion,
-  dirty-worktree rejection, and sidecar evidence tampering.
-- Existing remediation-mode recovery retains higher navigation priority than the new assessment;
-  the legacy malformed-third-attempt regression passes unchanged.
-- The corrective-replan serialized definition SHA moved to
-  `c601cc100790a19e6ece2a1d60fb46d1e1d52e6922e6104d84f4b6ffe7ba0225` because the decision event
-  schema now admits the bounded ordinal-2 recovery record. Its runtime semantic fingerprint remains
-  `bd4e7a0ddfcb6abc0c5eb107775e6aea7e08c4606dda4d945d77af8a4520710d`, and the runtime catalog hash
-  remains `fa1d11860d4f07978c3b8e85d1f91cd3d15b17284b05f41e05d462d3bb092aed`.
-- The beta.10 dependency-provenance and exact Signal T04 revision-26 regressions remain green.
-- The read-only Milestone projection still preserves `T03 cancelled → T08 replacement`, and the
-  monotonic chat registry/title fallback regressions remain green.
-
-## Trusted-harness release replay
-
-- A fresh disposable project installed the actual current beta.11 tarball, declared the exact
-  `2.0.0-beta.11` dependency, and passed package handshake plus `doctor` with protocol 2 and state
-  schema 2. Its Git checkout remained clean.
-- The automatic trusted harness invoked the real packaged CLI and append-only recorded Discovery
-  bootstrap, sequential `status → next` checkpoints, Project Knowledge scan/approval, and
-  Discovery-to-Task materialization through the resulting `task plan-set` boundary.
-- The semantic lifecycle log validated `24/24` events with no failed or unadvertised mutation and
-  no missing checkpoint. Its SHA-256 is
-  `5c1d666aa3bc27c4b6687b836a565823a1f567227e93f76b2c3285217fb9a0b7`.
-- The matched raw result log contains 12 successful CLI results, no C1 credential fields, and has
-  SHA-256 `a51bae7221fa0ff30bd571ca3800bf8ac44911d7746f68e5e86987b6c357ccf6`.
-  The exercised tarball SHA-256 is
-  `3b7ed19961ba8394625d3a481fafb196dd80be5b138635a0bd1ce084a47fc06e`.
-- This targeted real-agent replay validates release navigation discipline and package integration;
-  it does not claim a second full product Milestone. Deeper P01/P04 lifecycle behavior is covered
-  by the deterministic and integration suites listed below.
+  while fetching pinned `ajv`; the authorized network retry passed.
+- `npm run plugin:check`, the official Codex plugin validator, `npm run docs:pdf:check`, exact
+  `RELEASE_TAG=v2.0.0-beta.12 npm run release:check`, and `git diff --check` passed. The bundled
+  gateway cachebuster is `0.1.0+codex.20260827003726`.
+
+The first full post-version-bump validation exposed three failures before the Signal T04 runtime
+scenario began: a historical read-only snapshot truthfully targeted beta.11, while its replay
+assertion incorrectly required the current package version. The fix keeps the snapshot immutable at
+`2.0.0-beta.11`, binds the synthetic replay dependency to current `PACKAGE_VERSION`, and makes the
+release check verify both identities separately. The focused suite then passed `5/5`, and the final
+complete suite passed `321/321`.
+
+## Continuable remediation and review-routing evidence
+
+- A guarded Task remains in the same Task/Step and reaches a passing strict review after five
+  consecutive failed review cycles. Attempts 1–2 are ordinary; attempts 3+ are corrective
+  diagnostics but remain executable and review-gated.
+- Attempt count no longer selects a terminal lifecycle transition. It is retained as diagnostic
+  history only; explicit `split-required` and `stop-escalate` remain the stop authorities.
+- A failed review defaults to `route=fix` (or an omitted route) and continues the same Task/Step.
+  `route=replan` is valid only with exact `planClause`, `whyFixCannotFit`, and `minimalPlanChange`
+  evidence.
+- Replan returns to ordinary `task plan-set`; objective, requirements, and acceptance remain
+  immutable, while only implementation Steps may change. The replacement Plan still passes the
+  normal Plan Risk Audit and execution-authorization gates.
+- Failed-review routing evidence is hash-chained in the public Step Review event schema. Drift,
+  malformed evidence, unrelated Knowledge changes, forged actors, and corrupt chains remain
+  fail-closed.
+
+## Retained dependency, feasibility, and recovery evidence
+
+- P04-A retains the canonical Milestone dependency DAG, atomic initial Plan transaction/recovery,
+  dependency-bound handoff/claim/start, legacy fail-closed policy, and unconditional structural
+  replacement shutdown.
+- P01-A retains three versioned read-only analyzers, canonical in-event evidence/hash binding,
+  exact pre-start and corrective source selection, and phase-aware freshness before claim/start/run.
+- The exact Signal T04 revision-26 fixture still proves that only a verified historical Step Review
+  can retain its completion commit across corrective replan. Pending review is never trusted, and a
+  corrupt strict-review hash chain is rejected.
+- Bounded beta.11 `task plan-integrity-recover` compatibility remains green for its exact first
+  ordinary checks-failed case. It does not edit the Plan, package manifest, or worktree and still
+  fails closed for writable-manifest scope, unrelated dirty files, binding drift, or tampering.
+- Read-only Milestone progress still preserves `T03 cancelled → T08 replacement`; project-monotonic
+  chat allocation and deterministic long-title fallback/readback remain green.
+
+## Packaged real-agent lifecycle replay
+
+- A fresh disposable Git project installed the locally packed beta.12 tarball, declared the exact
+  `2.0.0-beta.12` dependency, and passed packaged `gateway handshake` plus `doctor` with protocol 2,
+  state schema 2, current dependency identity, and a clean checkout.
+- The trusted harness invoked the real packaged CLI sequentially for handshake, doctor, direct first
+  Discovery bootstrap, `status`, and fresh `next`. The resulting navigation advertised
+  `project-memory scan`.
+- `node scripts/validate-lifecycle-transcript.mjs` accepted all `10/10` post-provenance events with
+  no failed invocation, unadvertised mutation, or missing checkpoint. The semantic log SHA-256 is
+  `ab4ef10ad00e2fd9f54810ec5d0bbfb4106e1b211b3a185869d8a46787a5062d`; the raw packaged-result
+  log SHA-256 is `e693a839604c7ba2055f99e43c49c5ab63ac0cf6e790adc901db5dd8eb0ffae9`.
+- Credential-marker inspection found no writer, claim, delegation, bearer, or secret material, and
+  the disposable product checkout remained clean. Logs and external workflow state stayed outside
+  this repository.
+
+This replay validates package resolution, clean bootstrap, one real mutation, and mandatory
+post-mutation navigation discipline. It does not claim a second full product Milestone replay;
+deeper remediation, P01-A, and P04-A behavior is covered by deterministic and integration tests.
+
+## beta.12 PDF release documentation evidence
+
+- Three tracked Russian PDFs were deterministically regenerated from reviewable Markdown sources
+  under `docs/pdf/sources/`; `npm run docs:pdf:check` reported an empty stale set.
+- All 24 pages were rendered and visually inspected: architecture is 6 pages, the delegated
+  chat-only guide is 8 pages, and the technical reference is 10 pages. No blank, clipped, or orphaned
+  page was found.
+- Visible titles, headers, package commands, and release gates identify beta.12. The content covers
+  continuable remediation, evidence-bound fix/replan routing, Milestone dependency authority,
+  P01-A mechanical feasibility, C1 credentials, external-sealed review, Plan-integrity compatibility,
+  structural-replacement shutdown, and the limited derived-graph role of `codebase-memory-mcp`.
 
 ## Not claimed
 
 - Validation itself performs no npm publication, Git tag, push, Signal Workflow mutation, or local
-  plugin reinstall.
-- The implementation and package gates prove the bounded route. A real blocked project must still
-  install the published beta.11 package and follow its fresh project-local `handshake → doctor →
-  status → next → advertised recovery` navigation.
-
-## Post-beta.11 combined P04-A/P01-A candidate evidence
-
-This later evidence was recorded on 2026-08-24 on branch `codex/p04-task-dependencies` and was
-incorporated into the final beta.11 candidate.
-
-- P04-A adds the canonical Milestone dependency DAG, atomic initial Plan transaction/recovery,
-  dependency-bound handoff/claim/start, legacy fail-closed policy, and unconditional pre-write
-  structural replacement shutdown.
-- P01-A adds three versioned read-only analyzers, canonical in-event evidence/hash binding,
-  exact pre-start and corrective source selection, and phase-aware freshness before claim/start/run.
-- After final source review added a pre-Git-mutation start race guard, `npm test` passed the exact
-  final sequential `319/319` suite with zero failures, skips, cancellations, or todos. The 13/13
-  focused P01-A suite, 84/84 affected P01/P04/Task lifecycle selection, and 4/4 beta.11
-  late-recovery compatibility tests also passed.
-- `npm run typecheck`, `npm run plugin:check`, `npm run release:check`, schema validation inside
-  the full suite, the focused packaged-handshake capability test, and `git diff --check` passed.
-- The changed bundled gateway uses cachebuster `0.1.0+codex.20260824113210`; it was validated but
-  not reinstalled.
-- No merge, package install, tag, publication, plugin reinstall, Signal mutation, or brief status
-  transition to `implemented` is claimed by this candidate evidence.
-
-## beta.11 PDF release documentation evidence
-
-The Russian PDF set was regenerated and revalidated on 2026-08-24 against the combined beta.11
-candidate described above.
-
-- The three tracked PDF binaries now have reviewable Markdown authorities under
-  `docs/pdf/sources/` and one deterministic ReportLab generator. `npm run docs:pdf:check`
-  regenerated all outputs and reported an empty stale set.
-- All 24 pages were rendered and visually inspected: architecture is 6 pages, the delegated
-  chat-only guide is 8 pages, and the technical reference is 10 pages. Text extraction found no
-  empty pages. The architecture orphan-page defect found during inspection was removed, and the
-  complete delegated Discovery prompt no longer splits its readiness checklist across pages.
-- The content documents beta.11 delegated Discovery, the Milestone Autonomy Contract, explicit
-  `dependsOnTaskIds`, P04-A runnable routing and structural-replacement stop, P01-A mechanical
-  feasibility, C1 credential boundaries, external-sealed review, Plan-integrity recovery, and the
-  limited derived-graph role of `codebase-memory-mcp`.
-- `npm run pack:check` passed with an isolated writable npm cache. The 269-file dry-run tarball
-  contains all three PDFs, all three Markdown sources, the PDF README and pinned requirement, and
-  both generator/check scripts.
-- On the same beta.11 code tree, `npm run validate` passed `319/319`; `npm run typecheck`,
-  `npm run plugin:check`, `npm run release:check`, and `git diff --check` also passed.
-
-This evidence makes the documentation package-ready for beta.11. The release action remains a
-separate Git/tag operation after all final gates pass on the exact candidate tree.
+  plugin reinstall. Tagging and remote push are separate actions after the exact candidate gates.
+- Structural replacement remains intentionally disabled; beta.12 does not claim P04-B replacement
+  materialization or completed-Step adoption.
+- A real project must install the published exact beta.12 package, update/reinstall the bundled
+  gateway, and follow fresh project-local `handshake → doctor → status → next` navigation.

package/package.json

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

package/plugins/codex-workflow-gateway/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-workflow-gateway",
-  "version": "0.1.0+codex.20260824113210",
+  "version": "0.1.0+codex.20260827003726",
   "description": "Thin personal Codex gateway for exact project-local Codex Workflow V2 packages and codebase-memory-mcp.",
   "author": {
     "name": "Codex Workflow Maintainers"

package/plugins/codex-workflow-gateway/references/protocol.md

@@ -1,6 +1,6 @@
 # Gateway Protocol V2
 
-## beta.11 coordinator projections, retained review provenance, chat registry, and Plan-integrity recovery
+## beta.12 continuable remediation, coordinator projections, and retained recovery compatibility
 
 - When fresh `next` advertises `task plan-integrity-recover`, consume its exact Task revision,
   Step, actor, and writer-token contract. This route is valid only for the Core-derived
@@ -63,7 +63,7 @@ Current capability set:
 - `task-c1-handoff-sidecar-v1`
 - `task-mechanical-feasibility-v1`
 - `semantic-plan-risk-audit-v2`
-- `guarded-remediation-hard-stop-v1`
+- `guarded-remediation-continuation-v1`
 - `milestone-reverse-membership-integrity-v1`
 - `task-c1-handoff-bundle-v2`
 - `alpha6-adoption-posture-v1`
@@ -169,18 +169,23 @@ one hostile counterexample, expected safe result, and exact executable evidence
 unguarded Plan. Missing, stale, `split-required`, or `stop-escalate` evidence blocks
 authorization.
 
-For guarded remediation, `next.correctivePlanGate` or the runtime gate blocks a third
-ordinary retry on the same guarded Step until a current corrective decision exists. Record it
-with:
+For guarded remediation, the first two failed cycles are recorded as `ordinary` and later cycles as
+`corrective`. This mode is diagnostic: a third or later retry remains executable and still requires
+a fresh strict review. A finding defaults to `route=fix`; `route=replan` is accepted only with exact
+Plan-conflict evidence and routes to ordinary `task plan-set` for implementation-Step changes.
+
+An explicit corrective disposition can still be recorded when the actor deliberately chooses a
+stop, split, or compatible historical recovery route:
 
 ```text
 codex-workflow task corrective-decision --repo <git-root> \
   --id <TASK-ID> --step <STEP-ID> --expected-revision <REVISION> --file <decision.json>
 ```
 
-Only `continue-fix` permits bounded continuation. `replan-required`, `split-required`, and
-`stop-escalate` are stop or redirection decisions. If the third corrective review fails, a
-fourth run is prohibited; only split or stop may be recorded.
+`continue-fix` permits continuation; `replan-required`, `split-required`, and `stop-escalate` are
+explicit stop or redirection decisions. They are never inferred from attempt count. Without such an
+explicit decision, another failed strict review continues the same Task through its evidence-bound
+`fix`/`replan` route.
 
 ## Context refresh
 

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

@@ -376,9 +376,12 @@ only for membership changes; any change to outcome, success signal, acceptance,
 discovery, or base branch requires the ordinary human scope-change gate. Never self-renew or
 replace the contract.
 
-After two failed Task reviews, follow `next.correctivePlanGate`: obtain a distinct read-only
-corrective Auditor result and pass it through `--corrective-audit-file`. Do not continue for
-replan, split, or stop decisions.
+Repeated failed Task reviews remain on the same Task and do not require a separate corrective
+Plan audit based only on count. Follow fresh `next`: ordinary findings default to `route=fix`;
+`route=replan` is valid only with the exact Plan clause, obstruction, and minimal Plan change
+retained by Core. A remediation Plan may change implementation Steps but must preserve the Task
+objective, requirements, and acceptance. Explicit split or stop decisions still stop ordinary
+continuation.
 
 When `next.strictStepReview.recommendedMode` is `external-sealed`, do not launch the nested local
 reviewer from inside a Codex App sandbox. Run the advertised read-only `task step-review-packet`,

package/references/state-machine.md

@@ -37,16 +37,17 @@ bindings, supersedes execution authorization, and returns the Task to
 `awaiting_execution_authorization`. It cannot run while a Step is `in_progress` or while the
 Task is `blocked`; unrelated blocks must be resolved through their owning transition.
 
-For guarded remediation, two ordinary remediation attempts are allowed. Corrective posture is
+For guarded remediation, the first two attempts use mode `ordinary`; later attempts use mode
+`corrective`. Corrective posture is
 derived from the guarded Step, current Plan Risk Audit, remediation history, and
 corrective-decision history rather than from `Task.status` alone, so the same gate survives
-content-only Knowledge refresh, Task Knowledge rebind, and later reauthorization. A third
-ordinary retry is blocked until a current corrective decision exists for the same Step and
-Plan binding. `continue-fix` allows exactly the third corrective attempt; `replan-required`
-requires an actual new Plan posture before execution; `split-required` and `stop-escalate`
-stop ordinary execution. A failed third corrective attempt is a hard stop: `next` must
-report the stop without throwing, no fourth run is allowed, and no new `continue-fix` or
-`replan-required` decision is accepted.
+content-only Knowledge refresh, Task Knowledge rebind, and later reauthorization. Attempt count
+does not block execution: every new completion still requires exact strict-review evidence, while
+the same Task may continue until review passes. A failed finding defaults to `route=fix`.
+`route=replan` requires exact Plan-conflict evidence and routes to `task plan-set`; it may change
+implementation Steps but not the Task objective, requirements, or acceptance. Explicit
+`replan-required`, `split-required`, and `stop-escalate` decisions retain their redirect/stop
+semantics and outrank ordinary continuation.
 
 Milestone authorization is bound to its Plan and membership revision. Plan amendments
 supersede authorization. Milestone validation and acceptance are bound to the current base

package/references/validation-and-review.md

@@ -13,10 +13,17 @@ upgrade, concurrent state includes deterministic races, restart/replay claims in
 windows, and provider integrations include failure injection plus hidden-default checks.
 Happy-path green tests do not replace this evidence.
 
-After two failed independent reviews, another corrective Plan requires a distinct Auditor.
-The Auditor covers every latest finding and records `continue-fix`, `replan-required`,
-`split-required`, or `stop-escalate`. Only `continue-fix` may be passed to `task plan-set`
-through `--corrective-audit-file`; the other decisions stop implementation.
+Failed review does not impose a Task-lifecycle attempt limit. The first two guarded remediation
+events are recorded as `ordinary`; later events are `corrective`, remain executable, and each
+requires another fresh strict review. A failed-review finding defaults to `route=fix`. It may use
+`route=replan` only with exact `planClause`, `whyFixCannotFit`, and `minimalPlanChange` evidence;
+Core then routes to ordinary `task plan-set`, where only implementation Steps may change. Task
+objective, requirements, and acceptance remain immutable during remediation.
+
+The explicit corrective-decision journal remains available for intentional `continue-fix`,
+`replan-required`, `split-required`, and `stop-escalate` dispositions and for compatible historical
+recovery. It is not an attempt-count gate. Explicit split and stop decisions still stop or redirect
+execution; repeated review failure alone does not create either decision.
 
 The strict path is `task review-launch`. It starts an ephemeral Codex process with user
 configuration and rules ignored, a read-only sandbox, structured output, and an attempted

package/schemas/review-result.schema.json

@@ -22,7 +22,23 @@
           "requirement": { "type": ["string", "null"] },
           "summary": { "type": "string", "minLength": 1 },
           "evidence": { "type": "string", "minLength": 1 },
-          "requiredAction": { "type": "string", "minLength": 1 }
+          "requiredAction": { "type": "string", "minLength": 1 },
+          "route": { "enum": ["fix", "replan"] },
+          "planConflict": {
+            "anyOf": [
+              { "type": "null" },
+              {
+                "type": "object",
+                "additionalProperties": false,
+                "required": ["planClause", "whyFixCannotFit", "minimalPlanChange"],
+                "properties": {
+                  "planClause": { "type": "string", "minLength": 1 },
+                  "whyFixCannotFit": { "type": "string", "minLength": 1 },
+                  "minimalPlanChange": { "type": "string", "minLength": 1 }
+                }
+              }
+            ]
+          }
         }
       }
     }

package/schemas/step-review-event.schema.json

@@ -34,6 +34,21 @@
     "eventType": { "enum": ["pending", "review-recorded", "attestation-verified"] },
     "decision": { "enum": ["pending", "passed", "failed", "unverified"] },
     "reviewerAttestationHash": { "$ref": "#/$defs/nullableHash64" },
+    "remediationRoute": { "enum": ["fix", "replan", null] },
+    "planConflicts": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "additionalProperties": false,
+        "required": ["findingId", "planClause", "whyFixCannotFit", "minimalPlanChange"],
+        "properties": {
+          "findingId": { "type": "string", "minLength": 1 },
+          "planClause": { "type": "string", "minLength": 1 },
+          "whyFixCannotFit": { "type": "string", "minLength": 1 },
+          "minimalPlanChange": { "type": "string", "minLength": 1 }
+        }
+      }
+    },
     "previousEventHash": { "$ref": "#/$defs/nullableHash64" },
     "recordedAt": { "type": "string", "format": "date-time" },
     "eventHash": { "$ref": "#/$defs/hash64" }

package/scripts/generate-pdf-docs.py

@@ -44,6 +44,7 @@ SOURCE_DIR = ROOT / "docs" / "pdf" / "sources"
 OUTPUT_DIR = ROOT / "docs" / "pdf"
 PACKAGE = json.loads((ROOT / "package.json").read_text(encoding="utf-8"))
 PACKAGE_VERSION = PACKAGE["version"]
+RELEASE_LABEL = PACKAGE_VERSION.rsplit("-", 1)[-1]
 
 DOCUMENTS = (
     ("codex-workflow-v2-architecture-ru.md", "codex-workflow-v2-architecture-ru.pdf"),
@@ -396,7 +397,7 @@ def draw_page(canvas_obj: canvas.Canvas, doc: SimpleDocTemplate, title: str) ->
     canvas_obj.setFont("WorkflowBody", 7)
     canvas_obj.setFillColor(MUTED)
     canvas_obj.drawString(LEFT, PAGE_HEIGHT - 10 * mm, title[:74])
-    canvas_obj.drawRightString(PAGE_WIDTH - RIGHT, PAGE_HEIGHT - 10 * mm, f"beta.11 | {PACKAGE_VERSION}")
+    canvas_obj.drawRightString(PAGE_WIDTH - RIGHT, PAGE_HEIGHT - 10 * mm, f"{RELEASE_LABEL} | {PACKAGE_VERSION}")
     canvas_obj.line(LEFT, 11 * mm, PAGE_WIDTH - RIGHT, 11 * mm)
     canvas_obj.drawString(LEFT, 7 * mm, "Codex Workflow V2")
     canvas_obj.drawRightString(PAGE_WIDTH - RIGHT, 7 * mm, f"Страница {doc.page}")