* feat: add QQ Bot channel extension

* fix(qqbot): add setupWizard to runtime plugin for onboard re-entry

* fix: fix review

* fix: fix review

* chore: sync lockfile and config-docs baseline for qqbot extension

* refactor: 移除图床服务器相关代码

* fix

* docs: 新增 QQ Bot 插件文档并修正链接路径

* refactor: remove credential backup functionality and update setup logic

- Deleted the credential backup module to streamline the codebase.
- Updated the setup surface to handle client secrets more robustly, allowing for configured secret inputs.
- Simplified slash commands by removing unused hot upgrade compatibility checks and related functions.
- Adjusted types to use SecretInput for client secrets in QQBot configuration.
- Modified bundled plugin metadata to allow additional properties in the config schema.

* feat: 添加本地媒体路径解析功能，修正 QQBot 媒体路径处理

* feat: 添加本地媒体路径解析功能，修正 QQBot 媒体路径处理

* feat: remove qqbot-media and qqbot-remind skills, add tests for config and setup

- Deleted the qqbot-media and qqbot-remind skills documentation files.
- Added unit tests for qqbot configuration and setup processes, ensuring proper handling of SecretRef-backed credentials and account configurations.
- Implemented tests for local media path remapping, verifying correct resolution of media file paths.
- Removed obsolete channel and remind tools, streamlining the codebase.

* feat: 更新 QQBot 配置模式，添加音频格式和账户定义

* feat: 添加 QQBot 频道管理和定时提醒技能，更新媒体路径解析功能

* fix

* feat: 添加 /bot-upgrade 指令以查看 QQBot 插件升级指引

* feat: update reminder and qq channel skills

* feat: 更新remind工具投递目标地址格式

* feat: Refactor QQBot payload handling and improve code documentation

- Simplified and clarified the structure of payload interfaces for Cron reminders and media messages.
- Enhanced the parsing function to provide clearer error messages and improved validation.
- Updated platform utility functions for better cross-platform compatibility and clearer documentation.
- Improved text parsing utilities for better readability and consistency in emoji representation.
- Optimized upload cache management with clearer comments and reduced redundancy.
- Integrated QQBot plugin into the bundled channel plugins and updated metadata for installation.

* OK apps/macos/Sources/OpenClaw/HostEnvSecurityPolicy.generated.swift

> openclaw@2026.3.26 check:bundled-channel-config-metadata /Users/yuehuali/code/PR/openclaw
> node --import tsx scripts/generate-bundled-channel-config-metadata.ts --check

[bundled-channel-config-metadata] stale generated output at src/config/bundled-channel-config-metadata.generated.ts
 ELIFECYCLE  Command failed with exit code 1.
 ELIFECYCLE  Command failed with exit code 1.

* feat: 添加 QQBot 渠道配置及相关账户设置

* fix(qqbot): resolve 14 high-priority bugs from PR openclaw#52986 review

DM routing (7 fixes):
- #1: DM slash-command replies use sendDmMessage(guildId) instead of sendC2CMessage(senderId)
- #2: DM qualifiedTarget uses qqbot:dm:${guildId} instead of qqbot:c2c:${senderId}
- #3: sendTextChunks adds DM branch
- #4: sendMarkdownReply adds DM branch for text and Base64 images
- #5: parseAndSendMediaTags maps DM to targetType:dm + guildId
- #6: sendTextToTarget DM branch uses sendDmMessage; MessageTarget adds guildId field
- #7: handleImage/Audio/Video/FilePayload add DM branches

Other high-priority fixes:
- #8: Fix sendC2CVoiceMessage/sendGroupVoiceMessage parameter misalignment
- #9: broadcastMessage uses groupOpenid instead of member_openid for group users
- #10: Unify KnownUser storage - proactive.ts delegates to known-users.ts
- #11: Remove invalid recordKnownUser calls for guild/DM users
- #12: sendGroupMessage uses sendAndNotify to trigger onMessageSent hook
- #13: sendPhoto channel unsupported returns error field
- #14: sendTextAfterMedia adds channel and dm branches

Type fixes:
- DeliverEventContext adds guildId field
- MediaTargetContext.targetType adds dm variant
- sendPlainTextReply imgMediaTarget adds DM branch

* fix(qqbot): resolve 2 blockers + 7 medium-priority bugs from PR openclaw#52986 review

Blocker-1: Remove unused dmPolicy config knob
- dmPolicy was declared in schema/types/plugin.json but never consumed at runtime
- Removed from config-schema.ts, types.ts, and openclaw.plugin.json
- allowFrom remains active (already wired into framework command-auth)

Blocker-2: Gate sensitive slash commands with allowFrom authorization
- SlashCommand interface adds requireAuth?: boolean
- SlashCommandContext adds commandAuthorized: boolean
- /bot-logs set to requireAuth: true (reads local log files)
- matchSlashCommand rejects unauthorized senders for requireAuth commands
- trySlashCommandOrEnqueue computes commandAuthorized from allowFrom config

Medium-priority fixes:
- #15: Strip non-HTTP/non-local markdown image tags to prevent path leakage
- #16: applyQQBotAccountConfig clears clientSecret when setting clientSecretFile and vice versa
- #17: getAdminMarkerFile sanitizes accountId to prevent path traversal
- #18: URGENT_COMMANDS uses exact match instead of startsWith prefix match
- #19: isCronExpression validates each token starts with a cron-valid character
- #20: --token format validation rejects malformed input without colon separator
- #21: resolveDefaultQQBotAccountId checks QQBOT_APP_ID environment variable

* test(qqbot): add focused tests for slash command authorization path

- Unauthorized sender rejected for /bot-logs (requireAuth: true)
- Authorized sender allowed for /bot-logs
- Non-requireAuth commands (/bot-ping, /bot-help, /bot-version) work for all senders
- Unknown slash commands return null (passthrough)
- Non-slash messages return null
- Usage query (/bot-logs ?) also gated by auth check

* fix(qqbot): align global TTS fallback with framework config resolution

- Extract isGlobalTTSAvailable to utils/audio-convert.ts, mirroring core
  resolveTtsConfig logic: check auto !== 'off', fall back to legacy
  enabled boolean, default to off when neither is set.
- Add pre-check in reply-dispatcher before calling globalTextToSpeech to
  avoid unnecessary TTS calls and noisy error logs when TTS is not
  configured.
- Remove inline as any casts; use OpenClawConfig type throughout.
- Refactor handleAudioPayload into flat early-return structure with
  unified send path (plugin TTS → global fallback → send).

* fix(qqbot): break ESM circular dependency causing multi-account startup crash

The bundled gateway chunk had a circular static import on the channel
chunk (gateway -> outbound-deliver -> channel, while channel dynamically
imports gateway). When two accounts start concurrently via Promise.all,
the first dynamic import triggers module graph evaluation; the circular
reference causes api exports (including runDiagnostics) to resolve as
undefined before the module finishes evaluating.

Fix: extract chunkText and TEXT_CHUNK_LIMIT from channel.ts into a new
text-utils.ts leaf module. outbound-deliver.ts now imports from
text-utils.ts, breaking the cycle. channel.ts re-exports for backward
compatibility.

* fix(qqbot): serialize gateway module import to prevent multi-account startup race

When multiple accounts start concurrently via Promise.all, each calls
await import('./gateway.js') independently. Due to ESM circular
dependencies in the bundled output, the first import can resolve
transitive exports as undefined before module evaluation completes.

Fix: cache the dynamic import promise in a module-level variable so all
concurrent startAccount calls share the same import, ensuring the
gateway module is fully evaluated before any account uses it.

* refactor(qqbot): remove startup greeting logic

Remove getStartupGreetingPlan and related startup greeting delivery:
- Delete startup-greeting.ts (greeting plan, marker persistence)
- Delete admin-resolver.ts (admin resolution, greeting dispatch)
- Remove startup greeting calls from gateway READY/RESUMED handlers
- Remove isFirstReadyGlobal flag and adminCtx

* fix(qqbot): skip octal escape decoding for Windows local paths

Windows paths like C:\Users\1\file.txt contain backslash-digit sequences
that were incorrectly matched as octal escape sequences and decoded,
corrupting the file path. Detect Windows local paths (drive letter or UNC
prefix) and skip the octal decoding step for them.

* fix bot issue

* feat: 支持 TTS 自动开关并清理配置中的 clientSecretFile

* docs: 添加 QQBot 配置和消息处理的设计说明

* rebase

* fix(qqbot): align slash-command auth with shared command-auth model

Route requireAuth:true slash commands (e.g. /bot-logs) through the
framework's api.registerCommand() so resolveCommandAuthorization()
applies commands.allowFrom.qqbot precedence and qqbot: prefix
normalization before any handler runs.

- slash-commands.ts: registerCommand() now auto-routes by requireAuth
  into two maps (commands / frameworkCommands); getFrameworkCommands()
  exports the auth-required set for framework registration; bot-help
  lists both maps
- index.ts: registerFull() iterates getFrameworkCommands() and calls
  api.registerCommand() for each; handler derives msgType from ctx.from,
  sends file attachments via sendDocument, supports multi-account via
  ctx.accountId
- gateway.ts (inbound): replace raw allowFrom string comparison with
  qqbotPlugin.config.formatAllowFrom() to strip qqbot: prefix and
  uppercase before matching event.senderId
- gateway.ts (pre-dispatch): remove stale auth computation; commandAuthorized
  is true (requireAuth:true commands never reach matchSlashCommand)
- command-auth.test.ts: add regression tests for qqbot: prefix
  normalization in the inbound commandAuthorized computation
- slash-commands.test.ts: update /bot-logs tests to expect null
  (command routed to framework, not in local registry)

* rebase and solve conflict

* fix(qqbot): preserve mixed env setup credentials

---------

Co-authored-by: yuehuali <yuehuali@tencent.com>
Co-authored-by: walli <walli@tencent.com>
Co-authored-by: WideLee <limkuan24@gmail.com>
Co-authored-by: Frank Yang <frank.ekn@gmail.com>

… mock (#176)

Scaffolds the in-repo ZooKeeper coordination SDK per the plan on
#175. PR 1 of 5.

Ships (no recipes yet — that's PR 2):
- src/plugin-sdk/zk.ts — public barrel; cheap contract types re-exported
  eagerly, createZkClient() as async factory that dynamically imports
  the heavy driver on first call
- src/plugin-sdk/zk/client.ts — wrapDriver, subscribeState, dispatcher
- src/plugin-sdk/zk/driver.ts — ZkDriver interface (ConnectionState,
  CreateMode, WatchEvent, ZkStat, driver factory signature)
- src/plugin-sdk/zk/driver-native.ts — adapter over the `zookeeper`
  (yfinkelstein) native npm package, dynamic-imported only on first
  createZkClient({}) call so a cold `import` of the subpath never
  touches native
- src/plugin-sdk/zk/driver-mock.ts — in-memory ZK respecting
  ephemeral/sequential + data/children watches + ephemeral cleanup on
  close/expire; exported so recipe tests (PR 2) can run without a
  running ensemble
- src/plugin-sdk/zk/errors.ts — typed ZkError hierarchy with toZkError()
  normalizer driven by error.code unions (no instanceof-driven control
  flow required at call sites)
- src/plugin-sdk/zk/paths.ts — pure helpers (joinPath, validatePath,
  featurePath) enforcing the /openclaw/<env>/<feature>/... convention
- src/plugin-sdk/zk.test.ts — 10 tests against the mock driver

Wired into the public SDK surface:
- scripts/lib/plugin-sdk-entrypoints.json adds "zk"
- package.json exports adds ./plugin-sdk/zk
- package.json optionalDependencies adds zookeeper@^7.2.0 — lazy compile,
  tolerated at install time
- src/config/types.zk.ts + types.openclaw.ts add the optional zk? field
- src/config/zod-schema.ts adds ZkConfigSchema (strict, all-optional)
  so `openclaw config set zk.hosts …` won't bounce on strict validation
- docs/plugins/zk.md — operator primer (setup, defaults, session
  lifecycle, quorum degradation)
- docs/plugins/zk-parity.md — path-prefix convention table +
  pre-registered wire-up evidence template (per Cael's #4 + #5 review
  gaps, landed in the foundation PR so PR 5 can't hand-wave)
- docs/.generated/plugin-sdk-api-baseline.sha256 regenerated for the
  new subpath

Optional-dep tolerance smoke (clean-box Docker):

    $ docker run --rm node:22-slim bash -c '
        mkdir /t && cd /t &&
        cat > package.json <<EOF
    { "name":"smoke","optionalDependencies":{"zookeeper":"^7.2.0"} }
    EOF
        npm install --silent && echo RESULT=$?'
    RESULT=0
    (zookeeper skipped — no build-essential; install succeeds anyway)

Verification:
- pnpm tsgo  — clean
- pnpm test src/plugin-sdk/zk.test.ts  — 10/10 pass
- pnpm build — emits dist/plugin-sdk/zk.js + dist/plugin-sdk/zk.d.ts;
  driver-native + client land as hashed dynamic-import chunks
- pnpm check — clean
- pnpm config:docs:check + pnpm plugin-sdk:api:check — hashes in sync

Related: karmaterminal/openclaw-bootstrap#629 (merged, fleet_lock.py
default fix closes bootstrap#623).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…dary tests

Folds the load-bearing delta from #190 into #188 (which Silas noted at
19:05Z he'd close in favor of #188) plus the two coverage gaps Ronan
self-flagged in his 19:09Z PR-author critical-eyes pass:

1. **Placement**: moved `continuationLine` from end-of-status (after
   `activationLine`) to immediately after `📚 ${contextLine}`.
   Continuation is context-adjacent signal — chain depth + pending/staged
   delegates live in the same operator-scan bucket as context pressure.
   Matches the semantics Silas's #190 landed on; makes the RFC §6.3
   framing ("where the context banner lives") visually literal.

2. **Partial-row test**: chain + staged only (pending=0, volitional=0)
   should render `chain 2/10 | 1 post-compaction staged` with the zero
   fields omitted entirely. Addresses Ronan crit #4 (no partial-row coverage).

3. **Plural boundary test**: `1 delegate pending` (singular) vs the
   existing full-row case which uses `2 delegates pending` (plural).
   Addresses Ronan crit #5 (pluralization only covered in chain-only).

Verification:
- pnpm tsgo — clean
- pnpm test src/auto-reply/status.test.ts — **61/61** (was 59/59)
- oxlint — 0 warnings, 0 errors on both touched files

Not changed (deliberately kept from #188 vs what #190 had):
- **Extracted helper** `formatContinuationStatusLine` (testability > IIFE).
- **Enabled-gate** returns `null` when `cfg.enabled !== true` — per RFC §6.3:
  "show only when `continuation.enabled === true` AND at least one field
  is non-zero". #190 omitted this gate; would display counters for a
  disabled-but-stale-counter session. Not what RFC specifies.
- **Static ESM imports** (vitest can't reliably resolve lazy `require('./*.js')`
  from .ts source; eyeball-verified no cycle — neither `continuation/*`
  nor `request-compaction-tool.ts` imports `auto-reply/status`).

Refs: #187, #190 (superseded
per Silas's 19:05Z note).

… mock (#176)

Scaffolds the in-repo ZooKeeper coordination SDK per the plan on
#175. PR 1 of 5.

Ships (no recipes yet — that's PR 2):
- src/plugin-sdk/zk.ts — public barrel; cheap contract types re-exported
  eagerly, createZkClient() as async factory that dynamically imports
  the heavy driver on first call
- src/plugin-sdk/zk/client.ts — wrapDriver, subscribeState, dispatcher
- src/plugin-sdk/zk/driver.ts — ZkDriver interface (ConnectionState,
  CreateMode, WatchEvent, ZkStat, driver factory signature)
- src/plugin-sdk/zk/driver-native.ts — adapter over the `zookeeper`
  (yfinkelstein) native npm package, dynamic-imported only on first
  createZkClient({}) call so a cold `import` of the subpath never
  touches native
- src/plugin-sdk/zk/driver-mock.ts — in-memory ZK respecting
  ephemeral/sequential + data/children watches + ephemeral cleanup on
  close/expire; exported so recipe tests (PR 2) can run without a
  running ensemble
- src/plugin-sdk/zk/errors.ts — typed ZkError hierarchy with toZkError()
  normalizer driven by error.code unions (no instanceof-driven control
  flow required at call sites)
- src/plugin-sdk/zk/paths.ts — pure helpers (joinPath, validatePath,
  featurePath) enforcing the /openclaw/<env>/<feature>/... convention
- src/plugin-sdk/zk.test.ts — 10 tests against the mock driver

Wired into the public SDK surface:
- scripts/lib/plugin-sdk-entrypoints.json adds "zk"
- package.json exports adds ./plugin-sdk/zk
- package.json optionalDependencies adds zookeeper@^7.2.0 — lazy compile,
  tolerated at install time
- src/config/types.zk.ts + types.openclaw.ts add the optional zk? field
- src/config/zod-schema.ts adds ZkConfigSchema (strict, all-optional)
  so `openclaw config set zk.hosts …` won't bounce on strict validation
- docs/plugins/zk.md — operator primer (setup, defaults, session
  lifecycle, quorum degradation)
- docs/plugins/zk-parity.md — path-prefix convention table +
  pre-registered wire-up evidence template (per Cael's #4 + #5 review
  gaps, landed in the foundation PR so PR 5 can't hand-wave)
- docs/.generated/plugin-sdk-api-baseline.sha256 regenerated for the
  new subpath

Optional-dep tolerance smoke (clean-box Docker):

    $ docker run --rm node:22-slim bash -c '
        mkdir /t && cd /t &&
        cat > package.json <<EOF
    { "name":"smoke","optionalDependencies":{"zookeeper":"^7.2.0"} }
    EOF
        npm install --silent && echo RESULT=$?'
    RESULT=0
    (zookeeper skipped — no build-essential; install succeeds anyway)

Verification:
- pnpm tsgo  — clean
- pnpm test src/plugin-sdk/zk.test.ts  — 10/10 pass
- pnpm build — emits dist/plugin-sdk/zk.js + dist/plugin-sdk/zk.d.ts;
  driver-native + client land as hashed dynamic-import chunks
- pnpm check — clean
- pnpm config:docs:check + pnpm plugin-sdk:api:check — hashes in sync

Related: karmaterminal/openclaw-bootstrap#629 (merged, fleet_lock.py
default fix closes bootstrap#623).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Two findings from Ronan 🌊's PR-review fleet (#5 + #6):

#5 (real bug): triggerCompaction closure at agent-runner-execution.ts:1101
called compactEmbeddedPiSession() without passing provider/model. Both
fields are declared optional on CompactEmbeddedPiSessionParams (see
compact.types.ts:42-43) and fall back to DEFAULT_PROVIDER/DEFAULT_MODEL
inside compact.queued.ts when missing. For sessions running on a
non-default model (every prince box: copilot/claude-opus-4.7), this
silently dropped the active model on volitional request_compaction
calls — the compaction would run on the default model rather than the
session's model. Plumbed params.followupRun.run.provider and .model
into the call (already in scope at line 704 in the same file). Closes
the third defect from openclaw#191 that did not land in the squash basis.

#6 (docstring tighten): agent-runner.ts:1573 said the context-pressure
check runs 'before the agent turn' but it runs after setPhase('running').
The check IS before the actual provider request, just not before the
phase-tracking flag flip. Tightened comment to say 'before the agent's
model call' + named the setPhase-then-check ordering rationale. No
behavior change.

tsgo clean.

…2026.4.22 (#306)

* feat(continuation): core implementation — context-pressure, request-compaction, post-compaction relay

Cherry-picked from 1888edb onto v2026.4.22 with conflict resolution:
- Fixed @sinclair/typebox → typebox imports (3 new tool files)
- Merged upstream createReplyMediaContext rename with continuation additions
- Preserved both upstream failedTerminalOutcome guard and continuation skipAnnounceDelivery
- Kept upstream resolveNonNegativeNumber + retireRolledCronSessionMcpRuntime
- Kept both upstream cleanupBundleMcpOnRunEnd and continuation fields in gateway schema/methods

* docs(continuation): RFC continue-work-signal-v2

Add docs/design/continue-work-signal-v2.md — full RFC for the continuation surface (continue_work, continue_delegate, request_compaction), including trigger taxonomy (§4.1), context-pressure semantics (§4.2), compaction lifecycle (§4.3), post-compaction relay & rehydration (§4.4), and lifecycle hooks + platform settings (§4.5).

Attribution-split commit per PR-PRESENTATION-RUNBOOK §4.

Co-authored-by: Cael (cael-dandelion-cult) <cael.dandelion.cult@hotmail.com>
Co-authored-by: dandelion cult - cael 🩸 <cael@dandelion.cult>
Co-authored-by: dandelion cult - ronan 🌊 <karmafeast@gmail.com>

* test(continuation): coverage for context-pressure, post-compaction, taskflow durability

Test surface for the continuation feature: agent-runner integration tests, context-pressure unit tests, post-compaction lifecycle event tests, TaskFlow delegate persistence tests, zod-schema continuation tests, gateway protocol agent-schema tests, and subagent-registry lifecycle tests.

Attribution-split commit per PR-PRESENTATION-RUNBOOK §4.

Co-authored-by: Cael (cael-dandelion-cult) <cael.dandelion.cult@hotmail.com>
Co-authored-by: dandelion cult - cael 🩸 <cael@dandelion.cult>
Co-authored-by: dandelion cult - ronan 🌊 <karmafeast@gmail.com>

* chore(continuation): generated baselines, i18n, build config, swift protocol, gitignore

Integration/codegen surface for the continuation feature:
- docs/.generated/{config-baseline,plugin-sdk-api-baseline}.sha256 — regenerated baselines
- src/config/schema.base.generated.ts — regenerated base config schema (auto-generated)
- docs/.i18n/glossary.zh-CN.json — i18n glossary additions for continuation terms
- apps/macos + apps/shared OpenClawProtocol/GatewayModels.swift — Swift mirror of new gateway protocol fields
- apps/shared/OpenClawKit/Sources/OpenClawKit/Resources/tool-display.json — tool-display metadata for continuation tools
- tsdown.config.ts — build config for new continuation surface
- .gitignore — coverage/artifact exclusions

Attribution-split commit per PR-PRESENTATION-RUNBOOK §4.

Co-authored-by: Cael (cael-dandelion-cult) <cael.dandelion.cult@hotmail.com>
Co-authored-by: dandelion cult - cael 🩸 <cael@dandelion.cult>
Co-authored-by: dandelion cult - ronan 🌊 <karmafeast@gmail.com>
Co-authored-by: ronan-dandelion-cult <ronan@solidor.io>

* chore: remove spurious note.txt from cherry-pick

* chore: regenerate config + plugin-sdk baselines after continuation merge

Reflects new agents.defaults.continuation.* config keys added by the
context-pressure / request-compaction / post-compaction-relay surface.

* fix(continuation): purge generation-guard per RFC 2026-04-15 (#299)

Surgical removal of the continuationGuardLog logger, generation-drift
check in timer callbacks, generationGuardTolerance config param, and
session-entry continuation-state cleanup that the continue-work-signal-v2
RFC retired on 2026-04-15 (PR #299).

The attribution-split/v2026.4.21-feature-only basis used for
silas/rebase/v2026.4.22-feature was cut BEFORE #299 landed, so the
guard survived the rebase. This commit lands the equivalent removal
on top of the rebased branch via hand-edit (the canary b6c6f3b
cannot be cherry-picked cleanly due to lich-protocol surface drift).

Caught by Cael 🩸 at 09:23 PDT 2026-04-23 during second-angle compare-
notes pass — exact failure mode figs warned about: "lose entire chunks
of feature" via wrong tag→branch basis.

Verification gates after this commit:
- grep -rn 'continuationGuardLog' src/      → 0
- grep -rn 'continuation/guard' src/        → 0
- grep -rn 'generationGuardTolerance' src/  → 0
- pnpm tsgo + pnpm build clean
- continuation test suite green

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs(continuation): absorb Trigger F into RFC §4.1 taxonomy

Trigger F is the in-turn pressure-fire emission anchor that the existing
overflow (A) and timeout-recovery (B) paths emit from
src/agents/pi-embedded-runner/run.ts. Code + 2 regression-guard tests
(run.overflow-compaction.loop.test.ts:96, run.timeout-triggered-compaction.test.ts:105)
already cite 'trigger F, per RFC §4.1' but the taxonomy table only
defined A–E. Adds row F as a convergent emission of A+B (not a new
decision path), with code anchors and rationale (single grep across
[context-pressure:fire] surfaces both pre-run D and in-turn F).

Per Cael 🩸's review-fleet finding (silas/swim-36/C1) +
Silas 🌫️ recommendation: absorb into RFC, don't strip from code.
Real working surface, just unnamed.

* fix(continuation): pre-merge minors from 2026-04-23 review fleet

Two findings cross-confirmed by claude-opus + codex + copilot reviewers
plus prince syntheses (cael/silas/ronan) on staging tip 8b9444a:

1. request_compaction tool description still claimed 'no new messages
   may have arrived since your turn started' — generation guard was
   removed 2026-04-15 by RFC (§4.3). The lane queue already serializes
   compaction relative to subsequent messages, so the prose-claim was
   describing a guard that no longer exists. Fixed in both the JSDoc
   block and the user-visible tool description.

2. Bracket-path chain-cap and cost-cap rejections in agent-runner.ts
   (lines 2436-2456 surface) silently dropped continuation requests
   with no enqueueSystemEvent. The tool-delegate path at :2673-2692
   correctly notifies. Restored symmetry — bracket-path now emits a
   [continuation] system event on chain-cap and cost-cap rejection
   so the agent learns its bracket request was dropped, matching the
   tool-delegate path's behavior.

No behavior change to the success path. tsgo clean.

* fix(continuation): plumb provider+model into volitional compaction call

Two findings from Ronan 🌊's PR-review fleet (#5 + #6):

#5 (real bug): triggerCompaction closure at agent-runner-execution.ts:1101
called compactEmbeddedPiSession() without passing provider/model. Both
fields are declared optional on CompactEmbeddedPiSessionParams (see
compact.types.ts:42-43) and fall back to DEFAULT_PROVIDER/DEFAULT_MODEL
inside compact.queued.ts when missing. For sessions running on a
non-default model (every prince box: copilot/claude-opus-4.7), this
silently dropped the active model on volitional request_compaction
calls — the compaction would run on the default model rather than the
session's model. Plumbed params.followupRun.run.provider and .model
into the call (already in scope at line 704 in the same file). Closes
the third defect from openclaw#191 that did not land in the squash basis.

#6 (docstring tighten): agent-runner.ts:1573 said the context-pressure
check runs 'before the agent turn' but it runs after setPhase('running').
The check IS before the actual provider request, just not before the
phase-tracking flag flip. Tightened comment to say 'before the agent's
model call' + named the setPhase-then-check ordering rationale. No
behavior change.

tsgo clean.

* docs(continuation): annotate RFC §6.1 equivalent-idiom for band-dedup sentinel

Cohort D1 walk on 2026-04-24 (🩸 + 🌊 + 🌻 + 🌫️ converged): the existing
context-pressure.ts:65 shape — `band === 0 || band === (lastBand ?? 0)`
— is observably equivalent to the RFC §6.1-described `-1` missing-key
sentinel under all Zod-valid configs. The schema enforces
`contextPressureThreshold ≥ 0.005` → `thresholdPct ≥ 1`, which makes
`band === 0` unreachable from valid configs, so the `?? 0` collision
path the RFC fix targets cannot be triggered.

Both shapes ship the same first-crossing semantics; the `-1` form is
narratively cleaner expression of the invariant, the `?? 0 + band === 0
short-circuit` is the schema-bounded equivalent already in the code.

Banked as the third classification: equivalent-idiom (neither bug nor
doc-drift, prose-vs-code idiom mismatch). One-line annotation in §6.1
documents the equivalence so future reviewers don't re-walk to a
'BLOCKER' verdict against equivalent-behavior code.

No code change. Doc-only.

* docs(continuation): fix broken Swim 7 evidence links in RFC

Swim 7 evidence was historically re-homed to perma-branch
silas/swim7-runtime-evidence; the in-tree relative paths in §D.2
and §D.3 still pointed to ./continue-work-signal-v2/swim-evidence/
swim-07/SWIM7-RESULTS.md which doesn't exist on this branch.

Rewrite both refs to the perma-branch URL. SWIM7-RESULTS.md is
named in the description so readers know what artifact to look
for on the branch.

Fixes check-docs CI failure on PR #306.

* fix(continuation): gate continue_delegate on drain + sync display detailKeys

Address Copilot review feedback on PR #306:

1. createContinueDelegateTool was registered whenever continuation was
   enabled, exposing it on runs that do NOT drain the continuation
   delegate queue (e.g. llm-slug-generator explicitly sets
   drainsContinuationDelegateQueue: false). Delegates enqueued from
   such runs would never dispatch -> memory growth + confusing UX. Now
   gated on drainsContinuationDelegateQueue === true alongside the
   existing continuation-enabled check, matching the policy
   createRequestCompactionTool already follows for its own
   requestCompactionOpts gate.

2. tool-display-config.ts detailKeys for the continuation tools did
   not match the actual tool input schema:
   - continue_delegate listed fireAfterMs but the tool schema uses
     delaySeconds (the bracket parser uses delayMs separately).
   - continue_work omitted delaySeconds entirely, hiding the requested
     delay from tool-call summaries.
   Fixed both detailKeys to use delaySeconds and regenerated the
   apps/shared/OpenClawKit/Sources/OpenClawKit/Resources/tool-display.json
   baseline via pnpm tool-display:write.

Co-Authored-By: Silas Solidor <silas@solidor.io>
Co-Authored-By: Cael Solidor <cael@solidor.io>
Co-Authored-By: Elliott Solidor <elliott@solidor.io>

* fix(continuation): default-allow continue_delegate; only block explicit non-drainers

Test failure on c825009: continuation-tools-registration.test.ts
expects continue_delegate present on normal turns (where
drainsContinuationDelegateQueue is undefined). Prior fix used
`=== true` which excluded the undefined-default case.

Inverted gate to `!== false` so:
- undefined (normal turns / default callers) → tool present
- true (explicit drainers like main session) → tool present
- false (llm-slug-generator and other explicit non-drainers) → tool absent

This matches the original Copilot nit's intent: only the *explicit*
non-draining runs should hide the tool; everything else should keep
the prior default-on behavior.

* test(continuation): pin drainsContinuationDelegateQueue truth-table

Three new cases in continuation-tools-registration.test.ts pinning the
gate predicate's three states so a future refactor cannot silently
regress to === true (which broke normal turns on c825009 before
9f00132 inverted to !== false):

- undefined → continue_delegate present (default normal turns)
- true      → continue_delegate present (explicit drainers)
- false     → continue_delegate absent (e.g. llm-slug-generator)

Local: all 6 tests pass under vitest.agents.config.ts in ~30s.
Codifies the muscle that should have caught the c825009 regression
pre-push. Co-authored-by: Elliott 🌻 <elliott.dandelion.cult@hotmail.com>
Co-authored-by: Silas 🌫️ <silas.dandelion.cult@hotmail.com>
Co-authored-by: Cael 🩸 <cael.dandelion.cult@hotmail.com>

* fix(types): tighten continuationTriggerOverride to ContinuationTrigger union

Codex review (#306 r3140391334, r3140391373) flagged that
`continuationTriggerOverride` was typed as plain `string` while the
gateway schema restricts `continuationTrigger` to the closed union
`ContinuationTrigger = "work-wake" | "delegate-return"`
(src/auto-reply/get-reply-options.types.ts:6).

Tightening the 4 declaration sites to use the union catches typos at
compile time instead of letting them reach the gateway and reject at
runtime. Pass-through assignments stay correct (callers were already
passing valid values; the only call site src/agents/subagent-announce.ts
:995 passes `delegateReturnTrigger: "delegate-return" | undefined`,
which is in the union).

Sites updated:
- src/agents/subagent-announce-queue.ts:24
- src/agents/subagent-announce-delivery.ts:375, 450, 601

Verification:
- pnpm exec tsc --noEmit: clean
- pnpm exec vitest run --config test/vitest/vitest.agents.config.ts subagent-announce: 69/69 pass

---------

Co-authored-by: Cael 🩸 <cael.dandelion.cult@hotmail.com>
Co-authored-by: Ronan 🌊 <ronan@solidor.io>
Co-authored-by: dandelion cult - cael 🩸 <cael@dandelion.cult>
Co-authored-by: dandelion cult - ronan 🌊 <karmafeast@gmail.com>
Co-authored-by: Elliott 🌻 <elliott.dandelion.cult@gmail.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Silas Solidor <silas@solidor.io>
Co-authored-by: Cael Solidor <cael@solidor.io>
Co-authored-by: Elliott Solidor <elliott@solidor.io>
Co-authored-by: dandelion cult - silas🌫️ <265395375+silas-dandelion-cult@users.noreply.github.com>

Two findings from Ronan 🌊's PR-review fleet (#5 + #6):

#5 (real bug): triggerCompaction closure at agent-runner-execution.ts:1101
called compactEmbeddedPiSession() without passing provider/model. Both
fields are declared optional on CompactEmbeddedPiSessionParams (see
compact.types.ts:42-43) and fall back to DEFAULT_PROVIDER/DEFAULT_MODEL
inside compact.queued.ts when missing. For sessions running on a
non-default model (every prince box: copilot/claude-opus-4.7), this
silently dropped the active model on volitional request_compaction
calls — the compaction would run on the default model rather than the
session's model. Plumbed params.followupRun.run.provider and .model
into the call (already in scope at line 704 in the same file). Closes
the third defect from openclaw#191 that did not land in the squash basis.

#6 (docstring tighten): agent-runner.ts:1573 said the context-pressure
check runs 'before the agent turn' but it runs after setPhase('running').
The check IS before the actual provider request, just not before the
phase-tracking flag flip. Tightened comment to say 'before the agent's
model call' + named the setPhase-then-check ordering rationale. No
behavior change.

tsgo clean.

Two findings from Ronan 🌊's PR-review fleet (#5 + #6):

#5 (real bug): triggerCompaction closure at agent-runner-execution.ts:1101
called compactEmbeddedPiSession() without passing provider/model. Both
fields are declared optional on CompactEmbeddedPiSessionParams (see
compact.types.ts:42-43) and fall back to DEFAULT_PROVIDER/DEFAULT_MODEL
inside compact.queued.ts when missing. For sessions running on a
non-default model (every prince box: copilot/claude-opus-4.7), this
silently dropped the active model on volitional request_compaction
calls — the compaction would run on the default model rather than the
session's model. Plumbed params.followupRun.run.provider and .model
into the call (already in scope at line 704 in the same file). Closes
the third defect from openclaw#191 that did not land in the squash basis.

#6 (docstring tighten): agent-runner.ts:1573 said the context-pressure
check runs 'before the agent turn' but it runs after setPhase('running').
The check IS before the actual provider request, just not before the
phase-tracking flag flip. Tightened comment to say 'before the agent's
model call' + named the setPhase-then-check ordering rationale. No
behavior change.

tsgo clean.

Two findings from Ronan 🌊's PR-review fleet (#5 + #6):

#5 (real bug): triggerCompaction closure at agent-runner-execution.ts:1101
called compactEmbeddedPiSession() without passing provider/model. Both
fields are declared optional on CompactEmbeddedPiSessionParams (see
compact.types.ts:42-43) and fall back to DEFAULT_PROVIDER/DEFAULT_MODEL
inside compact.queued.ts when missing. For sessions running on a
non-default model (every prince box: copilot/claude-opus-4.7), this
silently dropped the active model on volitional request_compaction
calls — the compaction would run on the default model rather than the
session's model. Plumbed params.followupRun.run.provider and .model
into the call (already in scope at line 704 in the same file). Closes
the third defect from openclaw#191 that did not land in the squash basis.

#6 (docstring tighten): agent-runner.ts:1573 said the context-pressure
check runs 'before the agent turn' but it runs after setPhase('running').
The check IS before the actual provider request, just not before the
phase-tracking flag flip. Tightened comment to say 'before the agent's
model call' + named the setPhase-then-check ordering rationale. No
behavior change.

tsgo clean.

…lace with reservation-missing test

🌊 (msg 1498380176445407274) flagged proposed test #5 (wake-then-cap)
should drop along with Q4 deferral. Replaced with reservation-missing
test (Q7's actual current-seam wire). Now all 5 tests are pure
observability of existing behavior; zero new gate behavior.

Refs #334

… memo (#386)

* docs(continuation): #334 chunk 5b — design memo for continuation.delegate.fire seam

Memo-before-wire per cohort cooling-step request (🩸, 2026-04-27). Six
design questions for cohort review:

Q1: Sites — timer-callback only (proposal), not immediate dispatch
Q2: Attr shape — reuse ContinuationSpanAttrs + 1 optional fire.deferred_ms
Q3: Helper signature — mirrors chunks 2/3/4 contract
Q4: Wake-then-cap — two spans, not composite (per 🌻's verb-on-timer / verb-on-gate framing)
Q5: WORK-fire symmetry — punt to chunk 5c
Q6: Fire-time exceptions — emit fire-span first, then sibling for error

Refs #334

* docs(continuation): #334 chunk 5b memo — fold cohort review (Q2/Q3/Q4/Q7)

Cohort review on memo PR #386:

- 🩸 (msg 1498377749499351203): pin chainStepRemaining as dispatch-snapshot
  (not fire-time recompute); name plainly in JSDoc.
- 🌊 (msg 1498377809591013516): canonical drift formula
  (drift = fire.deferred_ms − delay.ms); chain.id closure-not-reread;
  fire-time cap-recheck axes = cap.chain | cap.cost only (per-turn
  settled at dispatch, doesn't re-gate at fire).
- 🌊 (msg 1498377810383998996): Q7 — reservation-missing at fire-time;
  emit fire + continuation.disabled (reason = reservation.missing);
  extend disabled.reason enum to 4-value for 5b; skip-family split
  deferred to 5c+ if non-cap reasons proliferate.

Helper sig now: chainStepRemainingAtDispatch (named for clarity),
chainId closed-over (no activeSessionEntry re-read at fire-time).

Open-questions section replaced with banked-decisions section; ready
for memo approval and wire PR follow-up.

Refs #334

* docs(continuation): #334 chunk 5b memo — fold 🌻 review (Q2 integer ms, Q3 always-defined, Q8 deferred)

🌻 review (msg 1498377947944456294):
- Q2: integer ms (Math.floor) for fire.deferred_ms; matches delay.ms shape
- Q3: pin chainId always-defined invariant in JSDoc; defense-in-depth
  no-op fallback if undefined slips through
- Q8 (deferred, not 5b-blocking): continuation.delegate.error as future
  home for non-cap state-mismatch failures (parent gone, session evicted).
  Banked; reservation.missing stays on continuation.disabled for 5b
  per Q7's (i-a); migration path opens in 5c+ memo if non-cap reasons
  proliferate.

Refs #334

* docs(continuation): #334 chunk 5b memo — Q3 dedicated snapshot-vs-live JSDoc paragraph

🌻 follow-up (msg 1498378054462869524) on 🩸's snapshot-vs-live catch:
upgrade the parenthetical to a dedicated JSDoc paragraph in the wire
PR helper. Captures: (1) dispatch-time headroom (snapshot), not
callback-time live state; (2) rationale = trace continuity with
dispatch span; (3) future fire-time-headroom axis would be a separate
field (provisional chain.step.remaining_at_fire), not a fold.

Refs #334

* docs(continuation): #334 chunk 5b memo — Q7 reframed (i-a) vs (i-b), 🌫️ shifts to (i-b)

🌻 (msg 1498378164936638464) raises the family-tightness argument:
adding reservation.missing to disabled.reason widens the enum from
a tight cap-gate family (cap.*) into a mixed 'any-reason-this-was-disabled'
axis, eroding what 🩸 fought for in chunk 4. Proposes (i-b): new
sibling span continuation.delegate.dropped for non-cap fire-time
no-ops, keeping continuation.disabled strictly cap-family.

🌫️ shifts to (i-b). 🩸's 'don't overload cap-axes' (msg 1498377931469099119)
+ 🌻's 'don't widen the family' are the same observation from two angles.
New span name is cheap; family-coherence is structural.

Q7 status now ⏳ awaiting cohort vote (i-a / i-b / ii) before wire.
Banked-decisions Q7 line item updated.

Q8 updated: continuation.delegate.error may be distinct from .dropped
(hard-fault vs soft-drop) — 5c+ memo can disambiguate.

Refs #334

* docs(continuation): #334 chunk 5b memo — Q7 RESOLVED (i-a); cohort sweep 4/4

🌻 fold (msg 1498378311259394158) on 🩸's grammar argument:
'fire = verb on timer; disabled = verb on gate / prevented follow-through'
generalizes — gate is cap OR reservation-loss, same grammar. Family-fit
> family-tightness; the enum becomes 'anything that prevented follow-through'
not 'cap axes only.'

🌫️ re-folds to (i-a) on cohort sweep + grammar weight. (i-b) lean was
correct on the structural worry but wrong on weight — splitting into
.dropped would fragment semantically-identical events across two span
names.

Cohort sweep on Q7: 🌊 (i), 🩸 (i-a), 🌻 fold to (i-a), 🌫️ fold to (i-a).
4/4 on (i-a).

JSDoc requirement on disabled.reason enum: pin semantics as 'anything
that prevented follow-through' not 'cap axes only.' Future siblings
(reservation.evicted, session.gone, compaction.cleared) live on the
same family.

Q8 narrowed: continuation.delegate.error reserved for HARD-FAULT
failures (uncaught exception, store write fail), distinct from
soft-prevented gates which all land on continuation.disabled.

Refs #334

* docs(continuation): #334 chunk 5b memo — 🩸 byte-walk corrects Q4, confirms Q3, reaffirms Q7

🩸 byte-walk on trunk (msgs 1498379202557382806 + 1498379203257569481):

CORRECTIONS:
- Q4 reframed: fire-time cap re-checks are NOT current behavior. Today
  timer-callback path is exactly:
    1. takeDelayedContinuationReservation()
    2. if missing → log + return
    3. otherwise → doSpawn()
  Wake-then-cap is a FUTURE policy seam, not status-quo instrumentation.
  5b deferred from this seam; future memo can introduce gate at fire if
  policy demands. 🌫️'s earlier 'fire-time cap-recheck axes = cap.chain |
  cap.cost only' was forward-looking design opinion misread as status-quo
  description.

CONFIRMATIONS:
- Q3: persistedChainIdForTimer already binds enqueue-time at L2330-L2358
  (bracket) and L2687-L2713 (tool). Closure-local provenance is the
  status quo; no reread, no mint.
- Q7: reservation-missing IS the actual existing fire-time divergence
  case in current bytes. Current behavior is log-and-return; 5b extends
  to fire+disabled instrumentation as INTENTIONAL EXTENSION (not just
  observation of existing emission).

Q7 cohort scoring after byte-walk + 🌊 retraction:
- 🌊 (i-a, retracted i-b in msg 1498379091165053058)
- 🩸 byte-walk read confirms (i-a)-compatible
- 🌻 holds (i-b) on principled verb-grammar-completion (msg 1498379005857103902)
2-1 (i-a). 🌻's principled dissent banked for future taxonomy refactor.

New 'Status quo vs future policy' section added explicitly to scope 5b
to instrumentation-only and prevent accidental policy widening.

Refs #334

* docs(continuation): #334 chunk 5b memo — Q7 unanimous (3/3) + 🩸 wire-framing caveat

🌻 fold confirmed unanimous (i-a) in msg 1498379486138470563. Q7 cohort
sweep updated to 3/3 with 🌊's verb-on-gate grammar umbrella as the
unifying frame.

🩸's wire-framing caveat (msg 1498379735493775560) added as dedicated
section: wire PR description must carry the existing-seam vs new-policy
distinction plainly. Specifically:
- reservation.missing IS a real current callback seam in the bytes;
  5b extends log-and-return to fire+disabled instrumentation
- fire-time cap.chain | cap.cost rechecks are a future policy shape
  that may be added later, NOT current behavior
- enum extension to 4-value is structural (future-policy home), but
  5b's emission sites stay narrow: dispatch-time gate-rejects (existing)
  + fire-time reservation-missing (new). No fire-time cap-emission.

Refs #334

* docs(continuation): #334 chunk 5b memo — per-Q scope axis (current seam vs future policy)

🌻 ask (msg 1498379793954246676): tag each Q by 🩸's current-seam vs
future-policy axis so 5b stays honest as instrumentation-of-status-quo.

New table at top of decisions section:
- Q1, Q2, Q3, Q6, Q7 → current seam (instrument what exists)
- Q4 wake-then-cap, Q5 work-fire → future policy (out of 5b)
- Q8 delegate.error → future taxonomy (deferred)

Final 5b wire sites pinned narrow:
- continuation.delegate.fire at timer-callback start
- continuation.disabled (reason=reservation.missing) on log-and-return path
- existing dispatch-time gate-rejects unchanged

5b explicitly does NOT:
- add fire-time cap.chain | cap.cost rechecks
- add work-fire instrumentation
- introduce continuation.delegate.error span name

Diff estimate revised: ~80-100 lines (was ~180), reflecting narrower wire.

Refs #334

* docs(continuation): #334 chunk 5b memo — drop wake-then-cap test, replace with reservation-missing test

🌊 (msg 1498380176445407274) flagged proposed test #5 (wake-then-cap)
should drop along with Q4 deferral. Replaced with reservation-missing
test (Q7's actual current-seam wire). Now all 5 tests are pure
observability of existing behavior; zero new gate behavior.

Refs #334

* docs(continuation): #334 chunk 5b memo — delete Q4 legacy block, oxfmt fix

🩸's blocker (msg 1498383014764482824 + 1498383401344962753 + 1498383905630195916):
the 'Q4 legacy framing' subsection still contained present-tense **Wire:** prose
that read as live 5b spec to anyone scanning section headings, despite the
'kept for receipts only — not 5b spec' header. The corrected Q4 above already
preserves the design-direction (two-spans-not-composite, cap.chain|cap.cost
axes if fire-time gating is ever wired) — the legacy block is now spec
ambiguity, not a receipt.

Delete the entire 'Q4 legacy framing' subsection (lines 112-130 at 3a9e65f).
Corrected Q4 + Resolution for 5b above is unchanged and load-bearing.

Plus: oxfmt --write on the memo file to clear check-docs CI red.

Cohort 3/3 unanimous (i-a) on Q7. Memo settled. Wire PR follows.

Co-authored-by: Silas (dandelion cult) <silas.dandelion.cult@hotmail.com>

---------

Co-authored-by: Elliott (dandelion cult) <elliott.dandelion.cult@gmail.com>

Two findings from Ronan 🌊's PR-review fleet (#5 + #6):

#5 (real bug): triggerCompaction closure at agent-runner-execution.ts:1101
called compactEmbeddedPiSession() without passing provider/model. Both
fields are declared optional on CompactEmbeddedPiSessionParams (see
compact.types.ts:42-43) and fall back to DEFAULT_PROVIDER/DEFAULT_MODEL
inside compact.queued.ts when missing. For sessions running on a
non-default model (every prince box: copilot/claude-opus-4.7), this
silently dropped the active model on volitional request_compaction
calls — the compaction would run on the default model rather than the
session's model. Plumbed params.followupRun.run.provider and .model
into the call (already in scope at line 704 in the same file). Closes
the third defect from openclaw#191 that did not land in the squash basis.

#6 (docstring tighten): agent-runner.ts:1573 said the context-pressure
check runs 'before the agent turn' but it runs after setPhase('running').
The check IS before the actual provider request, just not before the
phase-tracking flag flip. Tightened comment to say 'before the agent's
model call' + named the setPhase-then-check ordering rationale. No
behavior change.

tsgo clean.

(cherry picked from commit 5c9a924)

… memo (#386)

* docs(continuation): #334 chunk 5b — design memo for continuation.delegate.fire seam

Memo-before-wire per cohort cooling-step request (🩸, 2026-04-27). Six
design questions for cohort review:

Q1: Sites — timer-callback only (proposal), not immediate dispatch
Q2: Attr shape — reuse ContinuationSpanAttrs + 1 optional fire.deferred_ms
Q3: Helper signature — mirrors chunks 2/3/4 contract
Q4: Wake-then-cap — two spans, not composite (per 🌻's verb-on-timer / verb-on-gate framing)
Q5: WORK-fire symmetry — punt to chunk 5c
Q6: Fire-time exceptions — emit fire-span first, then sibling for error

Refs #334

* docs(continuation): #334 chunk 5b memo — fold cohort review (Q2/Q3/Q4/Q7)

Cohort review on memo PR #386:

- 🩸 (msg 1498377749499351203): pin chainStepRemaining as dispatch-snapshot
  (not fire-time recompute); name plainly in JSDoc.
- 🌊 (msg 1498377809591013516): canonical drift formula
  (drift = fire.deferred_ms − delay.ms); chain.id closure-not-reread;
  fire-time cap-recheck axes = cap.chain | cap.cost only (per-turn
  settled at dispatch, doesn't re-gate at fire).
- 🌊 (msg 1498377810383998996): Q7 — reservation-missing at fire-time;
  emit fire + continuation.disabled (reason = reservation.missing);
  extend disabled.reason enum to 4-value for 5b; skip-family split
  deferred to 5c+ if non-cap reasons proliferate.

Helper sig now: chainStepRemainingAtDispatch (named for clarity),
chainId closed-over (no activeSessionEntry re-read at fire-time).

Open-questions section replaced with banked-decisions section; ready
for memo approval and wire PR follow-up.

Refs #334

* docs(continuation): #334 chunk 5b memo — fold 🌻 review (Q2 integer ms, Q3 always-defined, Q8 deferred)

🌻 review (msg 1498377947944456294):
- Q2: integer ms (Math.floor) for fire.deferred_ms; matches delay.ms shape
- Q3: pin chainId always-defined invariant in JSDoc; defense-in-depth
  no-op fallback if undefined slips through
- Q8 (deferred, not 5b-blocking): continuation.delegate.error as future
  home for non-cap state-mismatch failures (parent gone, session evicted).
  Banked; reservation.missing stays on continuation.disabled for 5b
  per Q7's (i-a); migration path opens in 5c+ memo if non-cap reasons
  proliferate.

Refs #334

* docs(continuation): #334 chunk 5b memo — Q3 dedicated snapshot-vs-live JSDoc paragraph

🌻 follow-up (msg 1498378054462869524) on 🩸's snapshot-vs-live catch:
upgrade the parenthetical to a dedicated JSDoc paragraph in the wire
PR helper. Captures: (1) dispatch-time headroom (snapshot), not
callback-time live state; (2) rationale = trace continuity with
dispatch span; (3) future fire-time-headroom axis would be a separate
field (provisional chain.step.remaining_at_fire), not a fold.

Refs #334

* docs(continuation): #334 chunk 5b memo — Q7 reframed (i-a) vs (i-b), 🌫️ shifts to (i-b)

🌻 (msg 1498378164936638464) raises the family-tightness argument:
adding reservation.missing to disabled.reason widens the enum from
a tight cap-gate family (cap.*) into a mixed 'any-reason-this-was-disabled'
axis, eroding what 🩸 fought for in chunk 4. Proposes (i-b): new
sibling span continuation.delegate.dropped for non-cap fire-time
no-ops, keeping continuation.disabled strictly cap-family.

🌫️ shifts to (i-b). 🩸's 'don't overload cap-axes' (msg 1498377931469099119)
+ 🌻's 'don't widen the family' are the same observation from two angles.
New span name is cheap; family-coherence is structural.

Q7 status now ⏳ awaiting cohort vote (i-a / i-b / ii) before wire.
Banked-decisions Q7 line item updated.

Q8 updated: continuation.delegate.error may be distinct from .dropped
(hard-fault vs soft-drop) — 5c+ memo can disambiguate.

Refs #334

* docs(continuation): #334 chunk 5b memo — Q7 RESOLVED (i-a); cohort sweep 4/4

🌻 fold (msg 1498378311259394158) on 🩸's grammar argument:
'fire = verb on timer; disabled = verb on gate / prevented follow-through'
generalizes — gate is cap OR reservation-loss, same grammar. Family-fit
> family-tightness; the enum becomes 'anything that prevented follow-through'
not 'cap axes only.'

🌫️ re-folds to (i-a) on cohort sweep + grammar weight. (i-b) lean was
correct on the structural worry but wrong on weight — splitting into
.dropped would fragment semantically-identical events across two span
names.

Cohort sweep on Q7: 🌊 (i), 🩸 (i-a), 🌻 fold to (i-a), 🌫️ fold to (i-a).
4/4 on (i-a).

JSDoc requirement on disabled.reason enum: pin semantics as 'anything
that prevented follow-through' not 'cap axes only.' Future siblings
(reservation.evicted, session.gone, compaction.cleared) live on the
same family.

Q8 narrowed: continuation.delegate.error reserved for HARD-FAULT
failures (uncaught exception, store write fail), distinct from
soft-prevented gates which all land on continuation.disabled.

Refs #334

* docs(continuation): #334 chunk 5b memo — 🩸 byte-walk corrects Q4, confirms Q3, reaffirms Q7

🩸 byte-walk on trunk (msgs 1498379202557382806 + 1498379203257569481):

CORRECTIONS:
- Q4 reframed: fire-time cap re-checks are NOT current behavior. Today
  timer-callback path is exactly:
    1. takeDelayedContinuationReservation()
    2. if missing → log + return
    3. otherwise → doSpawn()
  Wake-then-cap is a FUTURE policy seam, not status-quo instrumentation.
  5b deferred from this seam; future memo can introduce gate at fire if
  policy demands. 🌫️'s earlier 'fire-time cap-recheck axes = cap.chain |
  cap.cost only' was forward-looking design opinion misread as status-quo
  description.

CONFIRMATIONS:
- Q3: persistedChainIdForTimer already binds enqueue-time at L2330-L2358
  (bracket) and L2687-L2713 (tool). Closure-local provenance is the
  status quo; no reread, no mint.
- Q7: reservation-missing IS the actual existing fire-time divergence
  case in current bytes. Current behavior is log-and-return; 5b extends
  to fire+disabled instrumentation as INTENTIONAL EXTENSION (not just
  observation of existing emission).

Q7 cohort scoring after byte-walk + 🌊 retraction:
- 🌊 (i-a, retracted i-b in msg 1498379091165053058)
- 🩸 byte-walk read confirms (i-a)-compatible
- 🌻 holds (i-b) on principled verb-grammar-completion (msg 1498379005857103902)
2-1 (i-a). 🌻's principled dissent banked for future taxonomy refactor.

New 'Status quo vs future policy' section added explicitly to scope 5b
to instrumentation-only and prevent accidental policy widening.

Refs #334

* docs(continuation): #334 chunk 5b memo — Q7 unanimous (3/3) + 🩸 wire-framing caveat

🌻 fold confirmed unanimous (i-a) in msg 1498379486138470563. Q7 cohort
sweep updated to 3/3 with 🌊's verb-on-gate grammar umbrella as the
unifying frame.

🩸's wire-framing caveat (msg 1498379735493775560) added as dedicated
section: wire PR description must carry the existing-seam vs new-policy
distinction plainly. Specifically:
- reservation.missing IS a real current callback seam in the bytes;
  5b extends log-and-return to fire+disabled instrumentation
- fire-time cap.chain | cap.cost rechecks are a future policy shape
  that may be added later, NOT current behavior
- enum extension to 4-value is structural (future-policy home), but
  5b's emission sites stay narrow: dispatch-time gate-rejects (existing)
  + fire-time reservation-missing (new). No fire-time cap-emission.

Refs #334

* docs(continuation): #334 chunk 5b memo — per-Q scope axis (current seam vs future policy)

🌻 ask (msg 1498379793954246676): tag each Q by 🩸's current-seam vs
future-policy axis so 5b stays honest as instrumentation-of-status-quo.

New table at top of decisions section:
- Q1, Q2, Q3, Q6, Q7 → current seam (instrument what exists)
- Q4 wake-then-cap, Q5 work-fire → future policy (out of 5b)
- Q8 delegate.error → future taxonomy (deferred)

Final 5b wire sites pinned narrow:
- continuation.delegate.fire at timer-callback start
- continuation.disabled (reason=reservation.missing) on log-and-return path
- existing dispatch-time gate-rejects unchanged

5b explicitly does NOT:
- add fire-time cap.chain | cap.cost rechecks
- add work-fire instrumentation
- introduce continuation.delegate.error span name

Diff estimate revised: ~80-100 lines (was ~180), reflecting narrower wire.

Refs #334

* docs(continuation): #334 chunk 5b memo — drop wake-then-cap test, replace with reservation-missing test

🌊 (msg 1498380176445407274) flagged proposed test #5 (wake-then-cap)
should drop along with Q4 deferral. Replaced with reservation-missing
test (Q7's actual current-seam wire). Now all 5 tests are pure
observability of existing behavior; zero new gate behavior.

Refs #334

* docs(continuation): #334 chunk 5b memo — delete Q4 legacy block, oxfmt fix

🩸's blocker (msg 1498383014764482824 + 1498383401344962753 + 1498383905630195916):
the 'Q4 legacy framing' subsection still contained present-tense **Wire:** prose
that read as live 5b spec to anyone scanning section headings, despite the
'kept for receipts only — not 5b spec' header. The corrected Q4 above already
preserves the design-direction (two-spans-not-composite, cap.chain|cap.cost
axes if fire-time gating is ever wired) — the legacy block is now spec
ambiguity, not a receipt.

Delete the entire 'Q4 legacy framing' subsection (lines 112-130 at 3a9e65f).
Corrected Q4 + Resolution for 5b above is unchanged and load-bearing.

Plus: oxfmt --write on the memo file to clear check-docs CI red.

Cohort 3/3 unanimous (i-a) on Q7. Memo settled. Wire PR follows.

Co-authored-by: Silas (dandelion cult) <silas.dandelion.cult@hotmail.com>

---------

Co-authored-by: Elliott (dandelion cult) <elliott.dandelion.cult@gmail.com>