@qwen-code/qwen-code 0.23.3-nightly.20260910.c46cb85cf2 → 0.23.3

package/bundled/goal-draft/SKILL.md

@@ -114,10 +114,10 @@ Then hand off, and nothing else:
 
 **If the `propose_goal` tool is available and no Goal is active**, call it with the objective on one line. The user approves or declines it in a dialog; only their approval sets the Goal. If they decline you will not be told why: stop, do not ask about it, and do not propose the same or a reworded objective again. After approval, acknowledge it in one sentence and end the turn — the Goal runtime starts the first Goal turn on its own.
 
-**Otherwise** (a client without Goal proposal support, headless, the tool is disabled, or a Goal is active), print:
+**Otherwise** (Web Shell or another ACP client, headless, the tool is disabled, or a Goal is active), print:
 
 1. The objective in a fenced code block.
 2. One line the user can run as-is: `/goal set <objective on one line>` (or `/goal edit …` when tightening the active goal). Print it as plain text with no code markers, so it can be copied verbatim.
-3. One sentence explaining that the draft has not been applied and the user must run the command to apply it; include any `[ASSUMPTION]` items. Do not promise a dialog when the tool is unavailable.
+3. One sentence explaining that the draft has not been applied and the user must run the command to apply it; include any `[ASSUMPTION]` items. Do not promise a dialog in Web Shell or other ACP sessions.
 
 Do not run /goal yourself. Do not begin the task. Stop and wait for the user.

package/bundled/qc-helper/docs/features/channels/dingtalk.md

@@ -111,6 +111,26 @@ Background Agent output is sent as soon as each response segment is available.
 Every message is labeled with the Agent name so concurrent work remains
 attributable.
 
+To buffer each Agent's notification turn and send it as one labeled message,
+enable aggregation for the DingTalk channel in `settings.json`:
+
+```json
+{
+  "channels": {
+    "my-dingtalk": {
+      "type": "dingtalk",
+      "clientId": "$DINGTALK_CLIENT_ID",
+      "clientSecret": "$DINGTALK_CLIENT_SECRET",
+      "aggregateBackgroundAgentResponses": true
+    }
+  }
+}
+```
+
+Aggregation is disabled by default. A partial labeled message is sent if the
+Agent turn is interrupted, fails before producing a final response, or does
+not finish within ten minutes.
+
 ## Running
 
 ```bash

package/bundled/qc-helper/docs/features/channels/overview.md

@@ -63,6 +63,7 @@ Channels are configured under the `channels` key in `settings.json`. Each channe
 | `allowedUsers`      | No               | List of user IDs allowed to use the bot (used by `allowlist` and `pairing` policies)                                                                                                                                    |
 | `sessionScope`      | No               | How sessions are scoped: `user` (default), `chat_thread`, or `single`. Legacy `thread` remains compatible when already configured but is not offered for new Web Shell configurations                                   |
 | `multiSession`      | No               | Retain up to eight owner-scoped named tasks in one chat. Requires daemon-managed mode, `sessionScope: "user"`, no webhooks or group-history backfill, and no enabled Channel loops                                      |
+| `messagePrefix`     | No               | Only dispatch user messages that begin with this exact, case-sensitive prefix after any leading `@mentions`; the prefix and following whitespace are removed before dispatch                                            |
 | `cwd`               | No               | Working directory for the agent. Defaults to the current directory                                                                                                                                                      |
 | `approvalMode`      | No               | Tool approval mode for channel sessions. Unattended webhook tasks require `yolo`; the setting applies to every session on the channel                                                                                   |
 | `instructions`      | No               | Custom instructions prepended to the first message of each session                                                                                                                                                      |
@@ -73,6 +74,10 @@ Channels are configured under the `channels` key in `settings.json`. Each channe
 | `groups`            | No               | Per-group settings. Keys are group chat IDs or `"*"` for defaults. See [Group Chats](#group-chats)                                                                                                                      |
 | `dispatchMode`      | No               | What happens when you send a message while the bot is busy: `steer` (default), `collect`, or `followup`. See [Dispatch Modes](#dispatch-modes)                                                                          |
 
+When `messagePrefix` is set, every user-authored message must begin with the prefix and a non-empty payload, for example `/review inspect #123`. Only the prefix and the mentions ahead of it are removed; a mention the user typed after the prefix reaches the agent unchanged. Shared and agent commands use the same rule (`/review /help`, `/review /clear`, and so on). Telegram's registered command-menu actions remain available without the prefix — unless the configured prefix is itself one of them, in which case the prefix wins and that command has to be sent prefixed too (`/new /new`). Attachments need a matching caption when the platform supports one; captionless Telegram, Feishu, WeChat, DingTalk and WeCom media messages continue to run, and their placeholder text is never quoted back as group history. Native todos, webhooks, and provider-generated assignment or review-request events also continue to run without a prefix because they are system events rather than chat messages.
+
+Two behaviours are deliberate and worth knowing before you turn the prefix on. A voice message whose transcript DingTalk or WeCom fills in counts as text the user spoke, so it must carry the prefix like any other message and is dropped otherwise — only an untranscribed voice note runs as captionless media. And the prefix is checked before pairing, so first contact from an unknown sender or an unapproved group has to carry the prefix as well; without that ordering every unprefixed message in a busy group would draw a pairing reply, which is exactly the noise the prefix exists to suppress. Tell new users the prefix out of band, or leave pairing channels unprefixed.
+
 ### Sender Policy
 
 Controls who can interact with the bot:
@@ -519,11 +524,7 @@ qwen channel status --daemon-url http://127.0.0.1:4170 --token secret
 qwen channel stop --daemon-url http://127.0.0.1:4170 --token secret
 ```
 
-This mode starts workspace-grouped channel worker processes owned by `qwen serve`. Workers connect back to the daemon through the SDK and use the same channel adapters. They are separate from the daemon process, so a channel adapter crash does not crash the daemon. An explicit `--channel` selection takes precedence and fails daemon startup if it cannot become ready. On a flagless boot, the trusted primary workspace's `serve.channels` setting is restored. Secondary workspaces do not independently restore their own `serve.channels`. Without either source, the daemon does not load channel adapters or reserve the lease until the first `qwen channel set`.
-
-Automatic restore skips invalid startup settings and validation or lease failures that occur before workers start, while preserving unrelated settings. After a worker startup fails, the daemon continues only once cleanup succeeds. A global runtime startup timeout or an unconfirmed worker stop still follows the normal startup-failure path; the service lease remains held while worker termination is unconfirmed. Check the daemon log for messages identifying `serve.channels` when a channel does not restore.
-
-Stored startup names must be non-empty, have no leading or trailing whitespace, and contain no unsafe control or invisible characters. Invalid entries are skipped individually and logged by their array index. Startup does not rename instances or rewrite the configuration. The channel startup toggle reflects the saved setting; runtime state shows whether the channel is running.
+This mode starts workspace-grouped channel worker processes owned by `qwen serve`. Workers connect back to the daemon through the SDK and use the same channel adapters. They are separate from the daemon process, so a channel adapter crash does not crash the daemon. A daemon started without `--channel` does not load channel adapters or reserve the channel-service PID lease until the first `qwen channel set`.
 
 `qwen serve --channel` is not the same service as `qwen channel start`. Standalone `qwen channel start` still uses the ACP-backed channel service and can run channel configs with different `cwd` values. Daemon-managed channels require every selected channel's `cwd` to resolve to a workspace registered by the daemon. In multi-workspace mode, a selection replacement keeps workers for workspaces whose ordered channel list did not change; `all` remains primary-workspace-only.
 

package/bundled/qc-helper/docs/features/goals.md

@@ -73,13 +73,13 @@ For an audit, completion means covering the agreed scenarios and reporting evide
 
 If a success criterion, command, input path, or essential decision cannot be established, the skill returns a draft marked "Needs clarification" with `<TODO: …>` items. It does not offer that draft for approval or print a runnable `/goal set` or `/goal edit` command. Nonessential defaults are marked `[ASSUMPTION]`; they do not stand in for missing success criteria.
 
-Once the objective is ready, an interactive terminal or Web Shell session can show the `propose_goal` approval dialog described below. Clients without Goal proposal support, headless runs, sessions with the tool disabled, and sessions with an active Goal receive a command to run manually instead. The hand-off says that the draft has not been applied. The skill never starts the work itself, and nothing is set without your approval.
+Once the objective is ready, an interactive terminal session can show the `propose_goal` approval dialog described below. Web Shell and other ACP clients, headless runs, sessions with the tool disabled, and sessions with an active Goal receive a command to run manually instead. The hand-off says that the draft has not been applied. The skill never starts the work itself, and nothing is set without your approval.
 
 Pass an existing objective to tighten it: `/goal-draft all tests pass and the lint is clean`. For an active Goal, an explicit request to tighten it produces `/goal edit`; a replacement uses `/goal set`. If the intended operation is unclear, the skill includes that choice in its single round of questions.
 
 ### Approve a Goal the model proposes
 
-In an interactive terminal or a Web Shell turn with an attached client, the model has a `propose_goal` tool. When `/goal-draft` finishes, or when you ask for an outcome that spans several turns, it can propose the objective instead of printing a `/goal set …` line for you to copy. The proposal appears as an approval dialog showing the full objective. Approving it sets the Goal exactly as `/goal set` would, the moment the current turn ends (the model acknowledges and stops; the first Goal turn then starts on its own), and declining sets nothing — the model sees only that the tool call was not allowed, and its instructions tell it not to ask why and not to propose the same objective again. The approval is bound to the turn that asked for it: if that turn is cancelled or otherwise never reaches its end, the approval is dropped rather than applied under a later message or an automated turn. No permission rule or approval mode (including YOLO) skips this dialog, and the tool refuses while another Goal is active, in plan mode, and in untrusted folders; subagents are never offered it. Web Shell uses its existing Allow/Reject permission panel. A stopped Goal can be replaced only if it still matches the version shown for approval; changing it invalidates the proposal. Headless runs, Web Shell channel deliveries and automatic turns, and ACP clients without the required approval and turn-lifecycle support retain the printed `/goal set` hand-off.
+In an interactive terminal session the model has a `propose_goal` tool. When `/goal-draft` finishes, or when you ask for an outcome that spans several turns, it can propose the objective instead of printing a `/goal set …` line for you to copy. The proposal appears as an approval dialog showing the full objective. Approving it sets the Goal exactly as `/goal set` would, the moment the current turn ends (the model acknowledges and stops; the first Goal turn then starts on its own), and declining sets nothing — the model sees only that the tool call was not allowed, and its instructions tell it not to ask why and not to propose the same objective again. The approval is bound to the turn that asked for it: if that turn is cancelled or otherwise never reaches its end, the approval is dropped rather than applied under a later message or an automated turn. No permission rule or approval mode (including YOLO) skips this dialog, and the tool refuses while another Goal is active, in plan mode, and in untrusted folders; subagents are never offered it. It is not available in headless runs, nor yet in Web Shell or other ACP-driven sessions (they do not pass through the turn boundary that applies the approval); there the printed `/goal set` line remains the hand-off.
 
 Turn it off with `goals.modelProposed: "disabled"` in your user settings. Because the setting decides whether the model may ask you to start an autonomous loop, it is honored only from user and system scope; a workspace `.qwen/settings.json` value is ignored with a warning.
 

package/bundled/qc-helper/docs/features/hooks.md

@@ -610,28 +610,24 @@ For `"ask"`, the TUI displays `permissionDecisionReason` as literal text rather
 
 #### UserPromptSubmit
 
-**Purpose**: Executed before supported model invocations to validate, block, or enrich their input. On the core/headless path, the event currently covers `UserQuery`, `ToolResult`, and `Hook` sends, while `Retry`, `Steer`, `Cron`, `Notification`, and `Teammate` sends are skipped. It can therefore occur on continuation paths, and `prompt` must not be assumed to be raw user input. The ACP session path has its own invocation policy: retries and newly dispatched background tasks can still invoke legacy hooks; continue, restored-question, and runtime-goal turns do not.
+**Purpose**: Executed before supported model invocations to validate, block, or enrich the current model-bound prompt. The event currently covers `UserQuery`, `ToolResult`, and `Hook` sends, while `Retry`, `Steer`, `Cron`, `Notification`, and `Teammate` sends are skipped. It can therefore occur on continuation paths, and `prompt` must not be assumed to be raw user input.
 
 **Event-specific fields**:
 
 ```json
 {
-  "prompt": "legacy prompt for this invocation; semantics depend on the execution path",
-  "submitted_prompt": "optional user text captured at a supported submission boundary"
+  "prompt": "current model-bound prompt for this hook invocation",
+  "submitted_prompt": "optional user text captured at a supported interactive TUI submission boundary"
 }
 ```
 
-`submitted_prompt` is optional. It is present on supported interactive TUI submissions and first-turn headless `UserQuery` sends. On the ACP session path used by ACP clients, `serve`, and daemon hosts, a fresh turn must carry an explicit submission declaration. Missing, non-string, empty, or whitespace-only declarations omit the field; the value is never reconstructed from `prompt` or a display label. Retries, continuations, and channel-classified turns omit it. The channel exclusion includes both automated events and human messages relayed through channel adapters.
+`submitted_prompt` is optional. It is present only when Qwen can carry provenance from a supported interactive TUI submission to a fresh `UserQuery`. It is omitted for unsupported producers and machine-driven paths such as same-turn steering, tool-result continuations, retries, cron, notifications, and teammate traffic. ACP, headless, `serve`, SDK, and remote-input paths do not produce it in this version.
 
-Web Shell provides the original composer text at its submission boundary. Realtime voice handoffs do not declare provenance because their request text comes from model-generated tool arguments. Other ACP/daemon SDK clients can opt in per request with `_meta: { "qwen.submittedPrompt": "original submitted text" }`, captured before resource or model-only expansion. Existing clients without this declaration continue running legacy hooks but do not trigger provenance-gated Auto Recall. Do not add the declaration globally to an SDK transport: scheduled tasks, Live task runs, sub-session spawns, model-authored cross-session messages, and promoted mid-turn messages must not acquire it automatically. The private `qwen.daemon.submittedPrompt` key is reserved for the daemon-to-child hop and is stripped from external callers. These declarations are caller-supplied provenance, not proof of human authorship or authorization.
-
-On the ACP path, the initial legacy `prompt` is the request's text blocks joined with a space before resource, attachment, slash-command, or model-only expansion. It does not expose the complete expanded model input. `submitted_prompt` can equal that text, but comes only from the explicit declaration and preserves its original whitespace. On the core/headless path, legacy `prompt` represents the current model-bound text for the hook invocation. Neither field is a complete DLP inspection surface.
-
-The following composer rules apply to the interactive TUI, not to ACP clients. Deferred input can retain the field when its provenance remains complete. A combined batch retains provenance only when every constituent item has it; edited, partially known, or otherwise ambiguous input omits the field. Prompt, command, and shell-history navigation or selected search matches, cross-restart stash restores, and conversation rewind restores also omit it because those paths can surface model-bound text without its original provenance. Consumers that require user-submitted text should treat absence as unavailable rather than falling back to `prompt`.
+Deferred input can retain the field when its provenance remains complete. A combined batch retains provenance only when every constituent item has it; edited, partially known, or otherwise ambiguous input omits the field. Prompt, command, and shell-history navigation or selected search matches, cross-restart stash restores, and conversation rewind restores also omit it because those paths can surface model-bound text without its original provenance. Consumers that require user-submitted text should treat absence as unavailable rather than falling back to `prompt`.
 
 After restored or provenance-unavailable model-bound input is cleared or submitted, the composer also clears its undo and redo history. This prevents undo from restoring expanded text after its marker or sidecar has been consumed.
 
-Large-paste placeholders remain compact in `submitted_prompt`; the expanded pasted content appears only in `prompt`. On that TUI path, consumers should treat the field as a text projection rather than a byte-for-byte record of clipboard input. ACP clients have no equivalent built-in Vim, paste-placeholder, history, or rewind provenance tracking; they own whether restored or edited text retains a valid submission declaration.
+Large-paste placeholders remain compact in `submitted_prompt`; the expanded pasted content appears only in `prompt`. Consumers should treat the field as a TUI text projection rather than a byte-for-byte record of clipboard input.
 
 Any non-empty input present while Vim mode is enabled omits `submitted_prompt`, including after Vim is disabled, because Vim registers do not carry provenance in this version. This conservative rule also covers drafts entered before enabling Vim. Clearing the composer starts a new eligible input.
 
@@ -669,7 +665,10 @@ This two-field payload is written only for this kind of user-prompt record.
 `hookContext` intentionally duplicates the tagged part so offline and
 third-party consumers can identify its provenance without parsing model text.
 `displayText` is the pre-hook display projection and never includes the hook
-context. On the core/headless path it is the submitted projection when available, otherwise the expanded pre-hook prompt. ACP records the trusted display projection or raw request text before expansion when a projection or attachment references require a payload; otherwise it records the user message without `systemPayload` or `displayText`.
+context. For a supported interactive TUI submission it is the raw composer
+projection carried by `submitted_prompt`; ACP, headless, `serve`, SDK, remote
+input, and other paths without that provenance record the expanded pre-hook
+prompt instead.
 
 Transcript display consumers treat `displayText` as this user-prompt projection
 when `systemPayload.hookContext` is a string. For compatibility with released
@@ -1496,11 +1495,11 @@ A PostToolUse HTTP hook that sends all tool execution records to a remote audit
 }
 ```
 
-### Example 3: Submitted Prompt Validation Hook
+### Example 3: Interactive TUI Submitted Prompt Validation Hook
 
-On the core/headless path, `prompt` can include generated or expanded content rather than original user input. On ACP it starts with the pre-expansion request text, so reading it does not inspect attachment bodies or the complete model input. `UserPromptSubmit` does not cover every model send. Do not silently fall back from `submitted_prompt` to `prompt` when source provenance is required.
+To inspect the current model-bound content instead, read `prompt`. That field can include generated or expanded content, is not the original user input, and does not imply that `UserPromptSubmit` covers every model send. Do not silently fall back from `submitted_prompt` to `prompt` when source provenance is required.
 
-A UserPromptSubmit hook that validates supported submitted text and provides context for long prompts. It also runs on headless submissions and explicitly declared ACP/daemon submissions; it is not TUI-only. It skips invocations where source provenance is unavailable. A blocking result stops the affected invocation, including on these non-TUI paths. The keyword check is illustrative and is not a complete DLP policy:
+A UserPromptSubmit hook that validates supported interactive TUI submissions for sensitive information and provides context for long prompts. It skips invocations where source provenance is unavailable. The keyword check is illustrative and is not a complete DLP policy:
 
 **prompt_validator.py**
 

package/bundled/qc-helper/docs/qwen-serve.md

@@ -166,19 +166,15 @@ qwen channel status --daemon-url http://127.0.0.1:4170 --token secret
 qwen channel stop --daemon-url http://127.0.0.1:4170 --token secret
 ```
 
-This mode is experimental and daemon-managed. It does not replace the standalone `qwen channel start` command: without `--daemon-url`, existing `qwen channel start`, `stop`, and `status` behavior remains standalone. With `qwen serve --channel`, the explicit selection wins, the daemon reserves the channel-service lease before listening, and startup fails if the initial worker cannot become ready. On a flagless boot, the daemon restores `serve.channels` from the trusted primary workspace. If neither source selects channels, the heavy channel runtime remains unloaded and no channel-service lease is reserved until the first runtime PUT. Secondary workspaces do not independently restore their own `serve.channels`; enable those channels through the runtime API after boot. If a ready worker later crashes, the daemon keeps running, relaunches it under a bounded restart policy, and reports its state (including `channel_worker_exited` warnings) in `GET /daemon/status`.
+This mode is experimental and daemon-managed. It does not replace the standalone `qwen channel start` command: without `--daemon-url`, existing `qwen channel start`, `stop`, and `status` behavior remains standalone. With `qwen serve --channel`, the daemon reserves the channel-service lease before listening and fails startup if the initial worker cannot become ready. Without `--channel`, it loads no channel runtime and reserves no channel-service lease until the first runtime PUT. If a ready worker later crashes, the daemon keeps running, relaunches it under a bounded restart policy, and reports its state (including `channel_worker_exited` warnings) in `GET /daemon/status`.
 
-Automatic restore skips an invalid startup field or a validation or lease error before workers start, logs its `serve.channels` source, and keeps unrelated settings in effect. After a worker startup fails, the daemon continues only once cleanup succeeds. Global runtime startup timeouts and unconfirmed worker stops retain the normal startup-failure behavior; the service lease remains held while worker termination is unconfirmed. Check the daemon log for skipped or failed restores.
-
-Stored startup names must be non-empty, have no leading or trailing whitespace, and contain no unsafe control or invisible characters. Invalid entries are skipped individually and logged by array index. Startup neither trims them into a different instance name nor rewrites settings. The channel startup toggle reflects persisted configuration, while runtime state reports whether the channel is running.
-
-Runtime control is exposed as `GET`, `PUT`, and `DELETE /workspace/channel`; SDK helpers are `getChannelWorkerControl()`, `setChannelWorkerSelection()`, and `stopChannelWorker()`. PUT/DELETE/reload use the strict mutation gate: trusted-loopback primary callers may use them without a token, while other deployments require operator credentials. Runtime selections are deliberately ephemeral: PUT does not edit settings or the boot options, and a restart returns to the explicit `qwen serve --channel` selection, otherwise to the trusted primary workspace's `serve.channels`, or to disabled when neither exists. Explicit CLI and runtime named selections are trimmed and deduplicated in first-occurrence order; order is preserved because the first channel can affect shared model selection.
+Runtime control is exposed as `GET`, `PUT`, and `DELETE /workspace/channel`; SDK helpers are `getChannelWorkerControl()`, `setChannelWorkerSelection()`, and `stopChannelWorker()`. PUT/DELETE/reload use the strict mutation gate: trusted-loopback primary callers may use them without a token, while other deployments require operator credentials. Runtime selections are deliberately ephemeral: PUT does not edit settings or the boot options, and a restart returns to the `qwen serve --channel` selection (or disabled when that flag is omitted). Named selections are trimmed and deduplicated in first-occurrence order; order is preserved because the first channel can affect shared model selection.
 
 Daemon-backed `qwen channel set` and `qwen channel reload`, plus `status` and `stop` with `--daemon-url`, cannot discover a token generated by `--open-with-auth`. Use `QWEN_SERVER_TOKEN` and pass the same value with `--token` to those clients, or omit authenticated-open mode.
 
 The daemon reads each channel's settings (tokens, `proxy`, per-channel `model`) when its worker starts. To re-read settings without changing the committed selection, call `POST /workspace/channel/reload` (SDK `client.reloadChannelWorker()`, or `qwen channel reload`). Reload re-resolves workspace ownership and restarts selected workers through the same rollback-safe reconcile path. The `channel_control` capability is present whenever runtime control is wired; `channel_reload` is present only while the manager is enabled. Persisted threads are restored from disk.
 
-Each selected channel's `cwd` must resolve to a registered workspace, and channels are grouped by that owning workspace: a single-workspace daemon runs one worker (unchanged from before); a multi-workspace daemon (`--workspace` repeated) runs one worker per workspace that owns a selected channel, each bound to that workspace's cwd, `QWEN_DAEMON_WORKSPACE`, and env overlay. To host a channel in a non-primary workspace, define it in that workspace's own `.qwen/settings.json` (no `cwd` needed) or set an explicit `cwd` equal to the workspace path. A channel defined only in user/system scope with no `cwd` is ambiguous across multiple workspaces: an explicit `--channel` selection fails startup, while automatic restore logs the ownership error and skips that selection before workers start. `--channel all` stays primary-only (it hosts the primary workspace's channels) and cannot be combined with named channels.
+Each selected channel's `cwd` must resolve to a registered workspace, and channels are grouped by that owning workspace: a single-workspace daemon runs one worker (unchanged from before); a multi-workspace daemon (`--workspace` repeated) runs one worker per workspace that owns a selected channel, each bound to that workspace's cwd, `QWEN_DAEMON_WORKSPACE`, and env overlay. To host a channel in a non-primary workspace, define it in that workspace's own `.qwen/settings.json` (no `cwd` needed) or set an explicit `cwd` equal to the workspace path; a channel defined only in user/system scope with no `cwd` is ambiguous across workspaces and causes a boot error. `--channel all` stays primary-only (it hosts the primary workspace's channels) and cannot be combined with named channels.
 
 Replacing a selection preflights configuration, ownership, and trust before stopping anything. It keeps workspace workers whose ordered selection is unchanged. If a changed worker cannot start, the daemon stops new workers and restores the old selection. If the daemon cannot confirm that an old child exited even after SIGKILL, it keeps the PID lease and refuses to create a duplicate worker. A worker is still considered ready when at least one requested adapter connects; PUT then returns `partial: true`, and `/daemon/status` reports `channel_worker_partial_connect` for the missing adapters.
 

package/chunks/{MaxSizedBox-UZW24XUX.js → MaxSizedBox-D4LW7RZZ.js}

@@ -14,25 +14,25 @@ import "./chunk-47ECGEJC.js";
 import "./chunk-2MIN6GRR.js";
 import "./chunk-QHTIBUWB.js";
 import "./chunk-RKUWKYED.js";
-import "./chunk-F2RKL5I2.js";
+import "./chunk-BZM5U74J.js";
 import "./chunk-GELRJXE2.js";
 import "./chunk-32CM56LO.js";
 import "./chunk-AEY27Z35.js";
 import "./chunk-Y2MYW47X.js";
 import "./chunk-LJZSMWOH.js";
-import "./chunk-TP2DUOB6.js";
+import "./chunk-F42YYSCK.js";
 import "./chunk-NUQVB25K.js";
 import "./chunk-ZKZHSB5W.js";
-import "./chunk-L2KF7HUE.js";
+import "./chunk-MSNHNAQZ.js";
 import "./chunk-DJXSOEFB.js";
 import "./chunk-ZKYR7QS4.js";
 import "./chunk-532WHF4F.js";
 import "./chunk-BUQN5LTI.js";
 import "./chunk-ZPJWUGCS.js";
 import "./chunk-LK2WUCDQ.js";
-import "./chunk-5FKZ7KFQ.js";
-import "./chunk-FRVV5SSD.js";
-import "./chunk-JV5YASQA.js";
+import "./chunk-UKZ45TJL.js";
+import "./chunk-RLLRJJDR.js";
+import "./chunk-N7VWZDWW.js";
 import "./chunk-GOFAQQZA.js";
 import "./chunk-TWPJO254.js";
 import "./chunk-CQ35AJ4Z.js";
@@ -53,7 +53,7 @@ import "./chunk-2SZH22YO.js";
 import "./chunk-DTNV6UZY.js";
 import "./chunk-QJNDUTOL.js";
 import "./chunk-JXNIF2O5.js";
-import "./chunk-CGKEUUYG.js";
+import "./chunk-NFYEQRLG.js";
 import "./chunk-ELRMZTPF.js";
 import "./chunk-CHEIIBT3.js";
 import "./chunk-PLLIWEM3.js";
@@ -65,7 +65,7 @@ import "./chunk-MLXTMF7H.js";
 import "./chunk-LILGKQ4B.js";
 import "./chunk-3CZ2BQV6.js";
 import "./chunk-SAH4BD2J.js";
-import "./chunk-CAAMI77K.js";
+import "./chunk-CXTPVBFA.js";
 import "./chunk-U7O65WKL.js";
 import "./chunk-S6LOFUVP.js";
 import "./chunk-FN3JNDRU.js";
@@ -74,20 +74,20 @@ import "./chunk-G6UUOCUT.js";
 import "./chunk-IZ2U57NY.js";
 import "./chunk-NUQ4GK5I.js";
 import "./chunk-K2OJUPOE.js";
-import "./chunk-B6BDT4RX.js";
+import "./chunk-AXTFYDXT.js";
 import "./chunk-NAVJD2PQ.js";
-import "./chunk-ZGQIIGNQ.js";
-import "./chunk-ZHECLGA6.js";
+import "./chunk-YBUMTY7B.js";
+import "./chunk-HNLMYDQE.js";
 import "./chunk-QHMLYMMS.js";
 import "./chunk-VNOVK4I7.js";
 import "./chunk-CFKIH3D3.js";
 import "./chunk-JL6APGBX.js";
 import "./chunk-DJ2GSRLV.js";
-import "./chunk-L3DTX6U4.js";
-import "./chunk-C75BXMPM.js";
+import "./chunk-4ALNJDHL.js";
+import "./chunk-NOO4QFXM.js";
 import "./chunk-KFFCDLKV.js";
 import "./chunk-ZW2EUO2A.js";
-import "./chunk-34ZYDM3F.js";
+import "./chunk-HBU7EKY4.js";
 import "./chunk-5ETULJLP.js";
 import "./chunk-ZHKTKHMO.js";
 import "./chunk-VGC4I5JJ.js";
@@ -98,7 +98,7 @@ import "./chunk-WZAD4ZNJ.js";
 import "./chunk-3FPYT6QC.js";
 import "./chunk-FPGTNKCP.js";
 import "./chunk-TIGXX4PA.js";
-import "./chunk-RJZTX2OF.js";
+import "./chunk-3UXUOFO6.js";
 import "./chunk-XFFRI3WM.js";
 import "./chunk-ERU3SDXT.js";
 import "./chunk-EWJTAP3Y.js";

package/chunks/{StandaloneSessionPicker-IDK7NAZL.js → StandaloneSessionPicker-ALTTRWUP.js}

@@ -4,18 +4,18 @@ import {
   ConfigContext,
   SessionPicker,
   SettingsContext
-} from "./chunk-ATH66AEU.js";
+} from "./chunk-DAWWT2ID.js";
 import {
   KeypressProvider
-} from "./chunk-KVBNJ4K2.js";
-import "./chunk-TWC3FHUI.js";
-import "./chunk-KZ2CU2LH.js";
-import "./chunk-3VPFA6L2.js";
-import "./chunk-CUK6F5UF.js";
+} from "./chunk-E7LB57MB.js";
+import "./chunk-NHJKAR6E.js";
+import "./chunk-7Q2AXRDJ.js";
+import "./chunk-BWAMMKIS.js";
+import "./chunk-S6Q6Q4P2.js";
 import "./chunk-4WGODMVR.js";
 import "./chunk-2UWQX4FP.js";
-import "./chunk-PMS4FVLY.js";
-import "./chunk-LAP7X6EC.js";
+import "./chunk-IL5M5NYD.js";
+import "./chunk-QMUYLYT5.js";
 import "./chunk-4LIPOIXS.js";
 import {
   require_jsx_runtime
@@ -33,47 +33,47 @@ import "./chunk-WBCPROWX.js";
 import "./chunk-EKTCKZV5.js";
 import "./chunk-2XRE4KE4.js";
 import "./chunk-KW7NOTN6.js";
-import "./chunk-UGS62IR2.js";
-import "./chunk-7XM6KEVW.js";
+import "./chunk-GCDXVPFK.js";
+import "./chunk-AC6KDLH3.js";
 import "./chunk-47ECGEJC.js";
-import "./chunk-ZT6EPPBY.js";
+import "./chunk-6JACAGYH.js";
 import "./chunk-2MIN6GRR.js";
 import "./chunk-QHTIBUWB.js";
-import "./chunk-BQOP3K76.js";
+import "./chunk-TWUKBNWM.js";
 import "./chunk-57OAHC2Y.js";
-import "./chunk-OOLSYRZ7.js";
+import "./chunk-7BXXIQG4.js";
 import "./chunk-RKUWKYED.js";
-import "./chunk-IOUBOANU.js";
-import "./chunk-YIU5PEAT.js";
+import "./chunk-ZU47FBOC.js";
+import "./chunk-NOAG7N22.js";
 import "./chunk-BW4333PP.js";
 import "./chunk-VX63RJXE.js";
 import "./chunk-IDS7MSUP.js";
-import "./chunk-74JEYK2C.js";
+import "./chunk-VZUCTJ2P.js";
 import "./chunk-5EJZE3FP.js";
-import "./chunk-KHIBLKNK.js";
+import "./chunk-53GWJOLP.js";
 import "./chunk-NPQ5ZKRP.js";
 import "./chunk-MR3PXB6E.js";
-import "./chunk-F2RKL5I2.js";
+import "./chunk-BZM5U74J.js";
 import "./chunk-GELRJXE2.js";
 import "./chunk-32CM56LO.js";
 import "./chunk-AEY27Z35.js";
 import "./chunk-Y2MYW47X.js";
 import "./chunk-LJZSMWOH.js";
-import "./chunk-TP2DUOB6.js";
+import "./chunk-F42YYSCK.js";
 import "./chunk-NUQVB25K.js";
 import "./chunk-ZKZHSB5W.js";
-import "./chunk-L2KF7HUE.js";
+import "./chunk-MSNHNAQZ.js";
 import "./chunk-DJXSOEFB.js";
 import "./chunk-ZKYR7QS4.js";
 import "./chunk-532WHF4F.js";
 import "./chunk-BUQN5LTI.js";
 import "./chunk-ZPJWUGCS.js";
 import "./chunk-LK2WUCDQ.js";
-import "./chunk-5FKZ7KFQ.js";
-import "./chunk-FRVV5SSD.js";
+import "./chunk-UKZ45TJL.js";
+import "./chunk-RLLRJJDR.js";
 import {
   SessionService
-} from "./chunk-JV5YASQA.js";
+} from "./chunk-N7VWZDWW.js";
 import "./chunk-GOFAQQZA.js";
 import "./chunk-TWPJO254.js";
 import "./chunk-CQ35AJ4Z.js";
@@ -94,7 +94,7 @@ import "./chunk-2SZH22YO.js";
 import "./chunk-DTNV6UZY.js";
 import "./chunk-QJNDUTOL.js";
 import "./chunk-JXNIF2O5.js";
-import "./chunk-CGKEUUYG.js";
+import "./chunk-NFYEQRLG.js";
 import "./chunk-ELRMZTPF.js";
 import "./chunk-CHEIIBT3.js";
 import "./chunk-PLLIWEM3.js";
@@ -108,7 +108,7 @@ import {
   getGitBranch
 } from "./chunk-3CZ2BQV6.js";
 import "./chunk-SAH4BD2J.js";
-import "./chunk-CAAMI77K.js";
+import "./chunk-CXTPVBFA.js";
 import "./chunk-U7O65WKL.js";
 import "./chunk-S6LOFUVP.js";
 import "./chunk-FN3JNDRU.js";
@@ -117,20 +117,20 @@ import "./chunk-G6UUOCUT.js";
 import "./chunk-IZ2U57NY.js";
 import "./chunk-NUQ4GK5I.js";
 import "./chunk-K2OJUPOE.js";
-import "./chunk-B6BDT4RX.js";
+import "./chunk-AXTFYDXT.js";
 import "./chunk-NAVJD2PQ.js";
-import "./chunk-ZGQIIGNQ.js";
-import "./chunk-ZHECLGA6.js";
+import "./chunk-YBUMTY7B.js";
+import "./chunk-HNLMYDQE.js";
 import "./chunk-QHMLYMMS.js";
 import "./chunk-VNOVK4I7.js";
 import "./chunk-CFKIH3D3.js";
 import "./chunk-JL6APGBX.js";
 import "./chunk-DJ2GSRLV.js";
-import "./chunk-L3DTX6U4.js";
-import "./chunk-C75BXMPM.js";
+import "./chunk-4ALNJDHL.js";
+import "./chunk-NOO4QFXM.js";
 import "./chunk-KFFCDLKV.js";
 import "./chunk-ZW2EUO2A.js";
-import "./chunk-34ZYDM3F.js";
+import "./chunk-HBU7EKY4.js";
 import "./chunk-5ETULJLP.js";
 import "./chunk-ZHKTKHMO.js";
 import "./chunk-VGC4I5JJ.js";
@@ -141,7 +141,7 @@ import "./chunk-WZAD4ZNJ.js";
 import "./chunk-3FPYT6QC.js";
 import "./chunk-FPGTNKCP.js";
 import "./chunk-TIGXX4PA.js";
-import "./chunk-RJZTX2OF.js";
+import "./chunk-3UXUOFO6.js";
 import "./chunk-XFFRI3WM.js";
 import "./chunk-ERU3SDXT.js";
 import "./chunk-EWJTAP3Y.js";
@@ -152,7 +152,7 @@ import "./chunk-HUXPEUFL.js";
 import "./chunk-TP6FYVQT.js";
 import "./chunk-ZAFYHRVY.js";
 import "./chunk-TBWQLLFO.js";
-import "./chunk-JDEW3V5B.js";
+import "./chunk-JYKWOREU.js";
 import {
   writeStdoutLine
 } from "./chunk-7FA2II6K.js";

package/chunks/{acp-startup-profiler-ARO4II44.js → acp-startup-profiler-KEU6VAYR.js}

@@ -9,8 +9,8 @@ import {
   markAcpStartup,
   recordAcpConfigStartupEvent,
   resetAcpStartupProfilerForTesting
-} from "./chunk-5FFAUU4T.js";
-import "./chunk-YKK2XXHF.js";
+} from "./chunk-J3TJH52D.js";
+import "./chunk-PSPAM24S.js";
 import "./chunk-5O2XNYP6.js";
 import "./chunk-J2S4EL5Y.js";
 export {

package/chunks/{acp-subagent-executor-7TLJGISS.js → acp-subagent-executor-LEUN3N7N.js}

@@ -15,28 +15,28 @@ import {
   RequestError,
   ndJsonStream
 } from "./chunk-IJOS26LH.js";
-import "./chunk-F2RKL5I2.js";
+import "./chunk-BZM5U74J.js";
 import "./chunk-GELRJXE2.js";
 import "./chunk-32CM56LO.js";
 import "./chunk-AEY27Z35.js";
 import "./chunk-Y2MYW47X.js";
 import "./chunk-LJZSMWOH.js";
-import "./chunk-TP2DUOB6.js";
+import "./chunk-F42YYSCK.js";
 import "./chunk-NUQVB25K.js";
 import "./chunk-ZKZHSB5W.js";
-import "./chunk-L2KF7HUE.js";
+import "./chunk-MSNHNAQZ.js";
 import "./chunk-DJXSOEFB.js";
 import "./chunk-ZKYR7QS4.js";
 import "./chunk-532WHF4F.js";
 import "./chunk-BUQN5LTI.js";
 import "./chunk-ZPJWUGCS.js";
 import "./chunk-LK2WUCDQ.js";
-import "./chunk-5FKZ7KFQ.js";
-import "./chunk-FRVV5SSD.js";
+import "./chunk-UKZ45TJL.js";
+import "./chunk-RLLRJJDR.js";
 import {
   AgentEventEmitter,
   renderSubagentSystemPrompt
-} from "./chunk-JV5YASQA.js";
+} from "./chunk-N7VWZDWW.js";
 import "./chunk-GOFAQQZA.js";
 import "./chunk-TWPJO254.js";
 import "./chunk-CQ35AJ4Z.js";
@@ -59,7 +59,7 @@ import "./chunk-2SZH22YO.js";
 import "./chunk-DTNV6UZY.js";
 import "./chunk-QJNDUTOL.js";
 import "./chunk-JXNIF2O5.js";
-import "./chunk-CGKEUUYG.js";
+import "./chunk-NFYEQRLG.js";
 import "./chunk-ELRMZTPF.js";
 import "./chunk-CHEIIBT3.js";
 import "./chunk-PLLIWEM3.js";
@@ -71,7 +71,7 @@ import "./chunk-MLXTMF7H.js";
 import "./chunk-LILGKQ4B.js";
 import "./chunk-3CZ2BQV6.js";
 import "./chunk-SAH4BD2J.js";
-import "./chunk-CAAMI77K.js";
+import "./chunk-CXTPVBFA.js";
 import "./chunk-U7O65WKL.js";
 import "./chunk-S6LOFUVP.js";
 import "./chunk-FN3JNDRU.js";
@@ -80,20 +80,20 @@ import "./chunk-G6UUOCUT.js";
 import "./chunk-IZ2U57NY.js";
 import "./chunk-NUQ4GK5I.js";
 import "./chunk-K2OJUPOE.js";
-import "./chunk-B6BDT4RX.js";
+import "./chunk-AXTFYDXT.js";
 import "./chunk-NAVJD2PQ.js";
-import "./chunk-ZGQIIGNQ.js";
-import "./chunk-ZHECLGA6.js";
+import "./chunk-YBUMTY7B.js";
+import "./chunk-HNLMYDQE.js";
 import "./chunk-QHMLYMMS.js";
 import "./chunk-VNOVK4I7.js";
 import "./chunk-CFKIH3D3.js";
 import "./chunk-JL6APGBX.js";
 import "./chunk-DJ2GSRLV.js";
-import "./chunk-L3DTX6U4.js";
-import "./chunk-C75BXMPM.js";
+import "./chunk-4ALNJDHL.js";
+import "./chunk-NOO4QFXM.js";
 import "./chunk-KFFCDLKV.js";
 import "./chunk-ZW2EUO2A.js";
-import "./chunk-34ZYDM3F.js";
+import "./chunk-HBU7EKY4.js";
 import "./chunk-5ETULJLP.js";
 import "./chunk-ZHKTKHMO.js";
 import "./chunk-VGC4I5JJ.js";
@@ -104,7 +104,7 @@ import "./chunk-WZAD4ZNJ.js";
 import "./chunk-3FPYT6QC.js";
 import "./chunk-FPGTNKCP.js";
 import "./chunk-TIGXX4PA.js";
-import "./chunk-RJZTX2OF.js";
+import "./chunk-3UXUOFO6.js";
 import "./chunk-XFFRI3WM.js";
 import "./chunk-ERU3SDXT.js";
 import "./chunk-EWJTAP3Y.js";