PRT-043 channel interaction runtime contracts

.memory-bank/guides/reference/npm-package-release-runbook.md

@@ -2,7 +2,7 @@
 file: .memory-bank/guides/reference/npm-package-release-runbook.md
 description: Practical runbook for versioning, verifying, publishing and post-release checking the `@dd-bot-platform/*` npm packages.
 purpose: Read when preparing or executing a real npm release for the first publishable framework packages so maintainers can follow one short canonical checklist instead of reconstructing the process from workflow files, Changesets config, and protocol notes.
-version: 1.2.0
+version: 1.3.0
 date: 2026-04-20
 status: ACTIVE
 parent: .memory-bank/guides/reference/index.md
@@ -14,6 +14,9 @@ related_files:
   - .github/workflows/release-packages.yml
   - scripts/publish-private-packages.mjs
 history:
+  - version: 1.3.0
+    date: 2026-04-26
+    changes: Added `@dd-bot-platform/channel-runtime` to the explicit runbook package set and pack/post-publish checklist after PRT-043 release readiness proved it is already controlled by the publish script allowlist.
   - version: 1.2.0
     date: 2026-04-22
     changes: Widened the allowed publish set to include `@dd-bot-platform/core` after the broader Wave 2 runtime-helper pack made the package a real framework seam rather than a bootstrap-only stub, and added package-cleanliness guidance for stale `dist` prevention before `pack`/publish.
@@ -27,6 +30,7 @@ history:
 ## Use this runbook when
 
 - releasing `@dd-bot-platform/api-contract`;
+- releasing `@dd-bot-platform/channel-runtime`;
 - releasing `@dd-bot-platform/core`;
 - releasing `@dd-bot-platform/scenario-system`;
 - confirming whether a merged framework package change is actually ready to go to npm.
@@ -53,6 +57,7 @@ If both packages change together, bump each package according to its own consume
 This runbook currently applies only to:
 
 - `@dd-bot-platform/api-contract`
+- `@dd-bot-platform/channel-runtime`
 - `@dd-bot-platform/core`
 - `@dd-bot-platform/scenario-system`
 
@@ -68,6 +73,7 @@ Do not widen publication beyond this allowlist until the owning protocol wave ex
    - `pnpm build`
 4. Run package artifact proof:
    - `pnpm --filter @dd-bot-platform/api-contract pack --pack-destination <tmp-dir>`
+   - `pnpm --filter @dd-bot-platform/channel-runtime pack --pack-destination <tmp-dir>`
    - `pnpm --filter @dd-bot-platform/core pack --pack-destination <tmp-dir>`
    - `pnpm --filter @dd-bot-platform/scenario-system pack --pack-destination <tmp-dir>`
    - inspect `package/package.json` from each tarball
@@ -136,6 +142,9 @@ For each released package:
 
 1. Check the registry version:
    - `npm view @dd-bot-platform/api-contract version`
+   - `npm view @dd-bot-platform/channel-runtime version`
+   - `npm view @dd-bot-platform/core version`
+   - `npm view @dd-bot-platform/scenario-system version`
 2. Check dist-tags if needed:
    - `npm dist-tag ls @dd-bot-platform/api-contract`
 3. Verify installability from a clean temp project.

.memory-bank/plans/index.md

@@ -2,8 +2,8 @@
 file: .memory-bank/plans/index.md
 description: 'Plans hub для bot-platform: framework epics, ADRs, protocols, current status и verification planning.'
 purpose: Читать для понимания delivery contour `bot-platform`, не смешивая framework delivery с SellerAgent и Docoved product waves.
-version: 0.7.0
-date: 2026-04-25
+version: 0.11.0
+date: 2026-04-26
 status: DRAFT
 tags: [plans, bot-platform, adr, epics, protocols, delivery]
 parent: .memory-bank/index.md
@@ -14,6 +14,18 @@ children:
   - protocols/index.md
   - verification-matrix.md
 history:
+  - version: 0.11.0
+    date: 2026-04-26
+    changes: Marked PRT-043 phase-2 implementation planning complete and linked the subagent execution companion and task workspace.
+  - version: 0.10.0
+    date: 2026-04-26
+    changes: Marked PRT-043 phase-1 review complete and noted new ownership, boundary contract, MBB routing, verification, release/rollback, and no-storage safeguards.
+  - version: 0.9.0
+    date: 2026-04-26
+    changes: Noted that PRT-043 phase-0 elaboration is complete and expanded the plans hub summary with command normalization, safe failures, config compatibility, idempotency, anti-abuse, and observability requirements.
+  - version: 0.8.0
+    date: 2026-04-26
+    changes: Added PRT-043 as the draft follow-up for channel interaction runtime after PRT-042 closed the canonical response document first wave.
   - version: 0.7.0
     date: 2026-04-25
     changes: Marked PRT-042 closed after first-wave channel-runtime implementation and retained publication/product direct-consumption as explicit follow-up.
@@ -76,11 +88,38 @@ history:
 - `protocols/PRT-040-governed-content-source-processing-and-workflow-backed-import-substrate.md`
 - `protocols/PRT-041-cross-repo-contract-dependency-boundary-realignment.md`
 - `protocols/PRT-042-channel-runtime-canonical-document-command-and-rendering.md`
+- `protocols/PRT-043-channel-interaction-runtime-command-render-thread-delivery.md`
+- `protocols/PRT-043-channel-interaction-runtime-implementation-plan.md`
+- `protocols/PRT-043-channel-interaction-runtime-review-details.md`
 - `verification-matrix.md`
 
 ## Immediate planning priorities
 
-### 1. Closed channel-runtime first wave
+### 1. Draft channel interaction runtime follow-up
+
+`protocols/PRT-043-channel-interaction-runtime-command-render-thread-delivery.md` is the draft follow-up to closed `PRT-042`.
+
+Phase state:
+- стадия проработки протокола: фаза 0 выполнена.
+- стадия проработки протокола: фаза 1 выполнена.
+- стадия проработки протокола: фаза 2 выполнена.
+
+Draft scope:
+- actor-aware command runtime policy for system admins, workspace admins, employees/members, known external users, unknown external users, and anonymous actors;
+- channel-neutral command input normalization and typed safe command failures;
+- canonical command responses through `CanonicalResponseDocument`;
+- channel-owned rendering from canonical markdown-compatible content;
+- channel-instance threading behavior such as email `Re:` and Telegram reply-to-message;
+- outbound delivery intent/result contracts;
+- command-policy compatibility migration from legacy product fields such as `commandAccessPolicy`;
+- idempotency, anti-abuse/rate-limit hooks, fallback diagnostics, and logging-first observability with no framework DB/UI in the first implementation;
+- Docoved and SellerAgent adoption waves with beta verification.
+
+The protocol must reuse `spec/runtime/command-framework-contract.md` and must not create a second command framework inside `channel-runtime`.
+Implementation code must not start until the pre-code gates in `PRT-043` are resolved.
+Implementation task packets and subagent execution rules live in `protocols/PRT-043-channel-interaction-runtime-implementation-plan.md`.
+
+### 2. Closed channel-runtime first wave
 
 `protocols/PRT-042-channel-runtime-canonical-document-command-and-rendering.md` is closed for the first-wave shared channel-runtime seam.
 
@@ -108,7 +147,7 @@ Still deferred by design:
 
 The stable runtime vocabulary belongs in `spec/runtime/channel-runtime-contract.md`; product mappings belong in product-local Memory Banks.
 
-### 2. Closed dependency-boundary cleanup
+### 3. Closed dependency-boundary cleanup
 
 `protocols/PRT-041-cross-repo-contract-dependency-boundary-realignment.md` is now closed for the concrete post-handoff package-boundary defect.
 
@@ -118,7 +157,7 @@ Closed result:
 - Memory Bank navigation treats adoption packets as closed baselines;
 - `sales-agent` links remain lineage rather than normative sources.
 
-### 3. Keep closed convergence docs as baseline
+### 4. Keep closed convergence docs as baseline
 
 `protocols/PRT-036-platform-framework-and-product-repo-split.md` остается closed lineage for the repo split.
 `protocols/PRT-038-platform-product-line-convergence-and-shared-substrate-extraction.md` остается closed baseline for the three-layer handoff.
@@ -127,7 +166,7 @@ Closed detailed child packets:
 - `protocols/PRT-039-shared-control-plane-access-channel-and-management-substrate.md`
 - `protocols/PRT-040-governed-content-source-processing-and-workflow-backed-import-substrate.md`
 
-### 4. Separate framework epics from product epics
+### 5. Separate framework epics from product epics
 
 В `epics/index.md` должны остаться только инициативы, которые после split-а по-настоящему принадлежат `bot-platform`, например:
 - foundation/repo topology;
@@ -139,7 +178,7 @@ Closed detailed child packets:
 
 SellerAgent и Docoved epic families здесь быть не должны.
 
-### 5. Keep one framework status snapshot
+### 6. Keep one framework status snapshot
 
 `current-status-report.md` нужен сразу, чтобы не потерять ответ на вопросы:
 - какие packages уже существуют в skeleton;