@qwen-code/qwen-code 0.22.0-nightly.20260825.22bb5e8b9f → 0.22.1

package/bundled/review/references/persistence.md

@@ -5,7 +5,7 @@ _Reference file of the `review` skill, loaded on demand — the core body
 before Step 8 except cross-repo lightweight runs, which skip Step 8
 entirely (Step 1 names the skip)._
 
-**Steps 8 and 9 are four responses, not ten.** Every command in this tail is cheap; the model turns between them are not — and this stretch runs after the verdict is already computed (and, on a posting run, already posted), so every extra turn is pure latency to the reader. Measured across six CI reviews, the one-command-per-turn shape cost 4–6 minutes after submission, before the artifact-root fumbling below stretched it further (measured; DESIGN.md — The one-command-per-turn tail). The dependency chain is short, so batch to it, issuing each group as separate tool calls in one response exactly as the Step 1 setup batch does: (1) `cost-ledger` plus the `read_file` of the findings artifact — everything the report's content still needs; (2) write the Markdown report; (3) `save-artifact` and the incremental-cache write, when this run owes one — both read only files that already exist, and neither reads the other; (4) `record_artifact` (its `workspacePath` comes from save-artifact's stdout, which is why it is not in group 3) together with Step 9's `cleanup`. **Group (4) fires only after group (3) succeeded**: `cleanup` deletes the `.qwen/tmp` side files `save-artifact` reads, so a failed group (3) is resolved first — the JSON helper is fail-closed (below), and destroying its only inputs would convert a recoverable failure into a permanent one. When it **cannot** be resolved (a malformed input, a disk error — synthesizing a replacement is forbidden by the same fail-closed rule), the run still ends properly: disclose the failure, skip `record_artifact` (there is nothing valid to register), copy the findings/composed inputs beside the Markdown report so the artifact stays rebuildable, and **still run `cleanup`** — Step 9's bypass audit and the completion line are never gated behind a success that will not come. A group's remaining reads may join its response; nothing here needs a turn of its own. Lower tiers drop the commands they never owed (low saves no artifact and writes no cache), not the batching.
+**Steps 8 and 9 are four responses, not ten.** Every command in this tail is cheap; the model turns between them are not — and this stretch runs after the verdict is already computed (and, on a posting run, already posted), so every extra turn is pure latency to the reader. Measured across six CI reviews, the one-command-per-turn shape cost 4–6 minutes after submission, before the artifact-root fumbling below stretched it further (measured; DESIGN.md — The one-command-per-turn tail). The dependency chain is short, so batch to it, issuing each group as separate tool calls in one response exactly as the Step 1 setup batch does: (1) `cost-ledger` plus the `read_file` of the findings artifact — everything the report's content still needs; (2) write the Markdown report; (3) `save-artifact` and the incremental-cache write, when this run owes one — both read only files that already exist, and neither reads the other; (4) `record_artifact` (its `workspacePath` comes from save-artifact's stdout, which is why it is not in group 3) together with Step 9's `cleanup`. **Group (4) fires only after group (3) succeeded**: `cleanup` deletes the `.qwen/tmp` side files `save-artifact` reads, so a failed group (3) is resolved first — the JSON helper is fail-closed (below), and destroying its only inputs would convert a recoverable failure into a permanent one. When it **cannot** be resolved (a malformed input, a disk error — synthesizing a replacement is forbidden by the same fail-closed rule), the run still ends properly: disclose the failure, skip `record_artifact` (there is nothing valid to register), copy the findings/composed inputs beside the Markdown report so the artifact stays rebuildable, and **still run `cleanup`** — Step 9's bypass audit and the completion line are never gated behind a success that will not come. A group's remaining reads may join its response; nothing here needs a turn of its own. Lower tiers drop the commands they never owed (low saves no artifact and writes no cache; a `--topology minimal` run owes neither at ANY effort — no verdict, no composed input, no artifact, no cache), not the batching.
 
 ### Report persistence
 
@@ -25,19 +25,19 @@ Report content should include:
 
 - Review timestamp and target description
 - **Provenance — the commits and the toolchain.** The head SHA reviewed (`fetchedSha` from the fetch report) and the base it was diffed against — **the range the round actually used**: `incremental.diffBase` on a delta-scoped round (`incremental.effective` and no `upToDate`), `mergeBaseSha` on every other, since recording the merge base for a round that reviewed `diffBase..head` hands the later reader a scope the run never had — plus the platform and the Node/npm versions the gates ran on, and one line per gate with its result (`build`, `test`, `script-lint`, `test-efficacy`, `test-plan` — ran / clean / failed / skipped, and why). A saved report is read by someone who cannot re-derive what it was about: without the SHA pair a "Verdict: Approve" names no commit, so it can be neither checked against the PR nor distinguished from an approval of a different head; and without the gate line a reader cannot tell a gate that passed from one that never ran. Both facts are already in reports this run has open — copy them, do not re-measure.
-- Effort level the review ran at (low / medium / high; **low** findings are marked unverified — medium and high verify them in Step 4)
+- Effort level the review ran at (low / medium / high; **low** findings are marked unverified — medium and high verify them in Step 4; under `--topology minimal` mark the topology too — its findings are unverified whatever effort the run resolved)
 - Diff statistics (files changed, lines added/removed) — omit if reviewing a file with no diff
-- Build & test results (Agent 7 output summary) — high and medium effort
+- Build & test results (Agent 7 output summary) — high and medium effort (absent under `--topology minimal` — no agents ran)
 - All findings with verification status. Read them out of the findings artifact `qwen review findings` wrote (`.qwen/tmp/qwen-review-{target}-findings.json`) rather than re-typing them from the terminal — a third transcription of the same list is a third chance for a severity to drift, which has happened inside a single review.
 - **Per-finding outcomes, when Step 6B ran** — `fixed` / `skipped` / `no_change_needed`, with the reason for every `skipped`. The artifact already carries them; a `--fix` run whose archive does not say which findings were applied is a report that reads as if all of them were.
-- Verdict (high and medium effort — a low quick pass claims none; a medium verdict never exceeds Comment, since it runs no reverse audit — see Step 5)
+- Verdict (high and medium effort — a low quick pass and a `--topology minimal` pass claim none; a medium verdict never exceeds Comment, since it runs no reverse audit — see Step 5)
 - **The cost ledger — run it, do not compute it.** `"${QWEN_CODE_CLI:-qwen}" review cost-ledger --plan <the plan report from Step 1> --out .qwen/reviews/<report>-cost-ledger.json` aggregates the model calls the harness recorded for this review — the main loop and each agent, with input / cached / output / thinking token counts and wall time — from the harness's own usage records, the same records the coverage gate trusts. The window is bounded: it starts at the plan's mtime, and the ledger runs at this step, so the pre-plan bootstrap turns and the composition after this snapshot are not captured, and side queries such as chat compression leave no usage records to capture at all. Paste its printed block into the report verbatim, and relay the first line in the terminal summary. The printed block lists only the eight biggest agents; the `--out` JSON keeps every one, so the diffable record survives in full (worktree mode: resolve `--out` against the main project directory, like the report itself). If it prints `cost-ledger unavailable`, note that instead — it is informational and never blocks a review. Why it is in the archive: a "this version got slower" report is unanswerable from memory, and the one time it was answered properly took hours of telemetry forensics to find a repair round that had silently doubled a run. The ledger makes the next such question a diff of two saved reports.
 
 **The report's verdict is not yours to type.** `compose-review` printed the exact `Verdict:` line in Step 6 and persisted the same line as `verdictLine` inside `.qwen/tmp/qwen-review-{target}-composed.json` — copy either, verbatim. Do not reconstruct it from `event` + `cappedBy`: a presubmit downgrade also depends on fields that pair does not carry, and a rebuilt line can differ from the computed one. (And not `$(jq …)`: a `jq` binary is not guaranteed on the host, and a substitution that fails leaves the archived verdict blank or literal — worse than absent, because it looks written.)
 
 A run has written an Approve into its saved report minutes after reading the capped verdict (measured; DESIGN.md — The narrated-away cap). The terminal is prose and the archive is forever; this line is the one place the archive can be made to tell the truth for free. If the composed event is not the one you expected, fix the run — not the report.
 
-After the Markdown report exists, create and register the structured review artifact for **medium and high** effort (low has no canonical composed verdict and must not invent one) — the creation is group (3) of the batching rule above; the registration rides group (4) alongside cleanup, which never touches `.qwen/reviews/`. Use the same filename stem as the Markdown report with a `.json` extension:
+After the Markdown report exists, create and register the structured review artifact for **medium and high** effort (low has no canonical composed verdict and must not invent one; a `--topology minimal` run owes none at ANY effort — it emits no verdict at all, so there is no composed JSON to persist — Step 3M) — the creation is group (3) of the batching rule above; the registration rides group (4) alongside cleanup, which never touches `.qwen/reviews/`. Use the same filename stem as the Markdown report with a `.json` extension:
 
 ```bash
 "${QWEN_CODE_CLI:-qwen}" review save-artifact \
@@ -72,7 +72,7 @@ The JSON helper is fail-closed because it carries the authoritative review resul
 
 ### Incremental review cache
 
-If reviewing a PR **at high effort**, update the review cache for incremental review support. Low and medium reviews must NOT write it — a cache hit would make a later high-effort review of the same SHA report "No new changes since last review", silently converting a cheaper pass into a full-review verdict.
+If reviewing a PR **at high effort**, update the review cache for incremental review support. Low and medium reviews must NOT write it, and neither must a `--topology minimal` run at any effort — a cache hit would make a later high-effort review of the same SHA report "No new changes since last review", silently converting a cheaper pass into a full-review verdict.
 
 **The cache advances exactly when the marker anchored — read the marker, do not re-derive the net.** `compose-review` already computed whether this round may certify a range: its posted body's ledger marker carries a `sha` on a clean round and withholds it otherwise (unproven coverage, an undecided blocker, any cap other than a depth-only `unreviewed-dimension` — where depth-only means every entry names the build-and-test dimension or is the machine's own relayed stop entry; a whiffed LENS in that field withholds). The cache and the marker must never disagree about what a clean round is, and a hand-copied condition list here is how they drifted once already — the list in this paragraph aged out of sync with the module and told a whiffed-lens round to cache the sha the marker had refused. So the rule is mechanical: **write `lastCommitSha` into the cache only if the composed body's marker carries a `sha`** (check the composed JSON's body for `"sha"` inside the `qwen-review-ledger` comment); when it does not, **skip the cache write entirely and say so in the terminal output**. Caching this SHA would scope the next high-effort run to `lastCommitSha..HEAD` — or, worse, let the same-SHA shortcut report "No new changes since last review" and skip the run outright, Step 6 re-check included: a whiffed Security lens at SHA A followed by an incremental review at SHA B means no run ever reviews A's diff for security, and an existing blocker this run could only mark `cannot tell` would never be re-checked at the same SHA, while the cached verdict reads as full coverage. Leave the previous cache entry in place (or none), so the next high-effort run re-covers the whole range — re-detecting any uncoverable chunk and re-ruling on any undecided blocker, keeping both disclosures alive:
 

package/bundled/review/references/posting.md

@@ -4,7 +4,7 @@ _Reference file of the `review` skill, loaded on demand — the core body
 (Steps 1–6 and 9) is already in your context. Load this file when, and only
 when, posting is live for the run: the Step 1 verdict reported
 `comment.effective: true`, or the user asked this session to post the
-comments — on a PR target at high effort. Never write to the PR/MR without
+comments — on a PR target at high effort, and never under `--topology minimal` (the arm posts nothing at any effort). Never write to the PR/MR without
 having read it._
 
 **The whole rule in one sentence, so it survives even when the rest is compressed away: never run a `gh` command that writes to the pull request — nor an `a1` command that writes to the MR — `qwen review submit` is the only write path in this skill, and it refuses when the run is not authorised.** Everything below only spells out what "writes" covers so a compressor cannot quietly narrow it to a single API route. It is **every write path to the PR/MR**, not one: no `gh api repos/.../pulls/<n>/reviews` (not to submit, not to "test" an anchor), no `gh pr comment`, no `gh pr review`, no `gh issue comment`, no `gh api` with POST/PATCH/PUT/DELETE against the PR's `issues/*` or `pulls/*` endpoints, and — on an Aone target — no `a1 repo mr comment create`, no `a1 repo mr approve`, no `a1 repo mr edit`: no posting a finding or a verdict "by hand" when `submit` refused, in whole or in part — "by hand" is never an agent action; a remedy that names the USER as its actor is for the user to perform, not for you to perform for them. And no editing or deleting existing comments on either platform. (One narrowly-scoped carve-out exists and it does not touch the PR: the Step 4 render-adjudication check may post a minimal payload to the repo the **user designated** in `QWEN_REVIEW_SCRATCH_REPO` — that repo, that check, nothing else; absent the setting there is no carve-out at all, and nothing about the PR, its code, or its authors is ever posted there.) **You do not author PR-facing prose at all** — `compose-review` computes the review body from structured state (the verdict, the downgrade reasons, the body-Criticals), and there is no free-text field to pass through it; a free-form note you want to add is a note for the **terminal summary**, which the user reads, not for the pull request. The only text that reaches the PR is that computed body plus the inline finding comments, and both ride the one sanctioned write below. This bypass has happened, invisibly to everything downstream (measured; DESIGN.md — The gh pr comment bypass). On GitHub targets, `cleanup` audits the review window and flags issue comments by the reviewing account (submit never posts one — see Step 9), so that bypass is at least named in the terminal — a tripwire, not permission. On Aone targets the same tripwire is keyed on comment ids: there the sanctioned submit POSTS COMMENTS (the inline findings and the summary — Aone has no review object), so `cleanup` lists the MR's comments through the `a1` CLI and flags any comment the authenticated account posted — or edited — inside the window that the receipt `submit` wrote does not vouch for. The one write in this skill lives behind a check:
@@ -32,7 +32,7 @@ It also refuses a payload that contradicts itself — a body promising inline co
 
 If **none** of the three holds, `submit` refuses and nothing is written. You MUST NOT reach around it — no `gh api .../pulls/.../reviews`, no other comment/review write, at all in this run — regardless of the verdict, the number of Criticals, or any "Tip: post comments" text you are about to print. A Request-changes verdict with unposted Criticals is the correct, complete outcome of a review without an effective comment authorisation: the findings live in the terminal (Step 6) and the saved report (Step 8), and the follow-up tip invites the user to post if they want. Do not rationalize a post because the findings "seem important" — the user decides when feedback becomes public. This gate has been violated in dogfooding (measured; DESIGN.md — The self-filed COMMENT review (PR #6771)); the check is arithmetic, not judgment: no flag, no standing setting, and no explicit request ⇒ no write.
 
-Also skip this step (independently of the gate above) if the review target is not a PR, or if the review ran at low or medium effort. **Low**'s findings are unverified and must never be posted. **Medium**'s findings ARE verified (Step 4 ran), but posting is a high-only action — `--comment` forces high, and medium's verdict is capped at Comment — so a medium review reports to the user and does not post to the PR. Decline a "post comments" follow-up after either, and point at `--effort high`.
+Also skip this step (independently of the gate above) if the review target is not a PR, or if the review ran at low or medium effort, or if it ran under `--topology minimal` at any effort. **Low**'s findings are unverified and must never be posted. **Medium**'s findings ARE verified (Step 4 ran), but posting is a high-only action — `--comment` forces high, and medium's verdict is capped at Comment — so a medium review reports to the user and does not post to the PR. **Minimal**'s findings are unverified and the arm posts nothing at any effort — it resolves effort high by default on a PR target while the `--user-authorized` fast path never consults the topology, so this rule is the layer that catches a run whose Step 6 decline was missed. Decline a "post comments" follow-up after any of the three, and point at `--effort high`.
 
 **Use the "Create Review" API to submit verdict + inline comments in a single call** (like Copilot Code Review). This eliminates separate summary comments — the inline comments ARE the review.
 

package/chunks/MaxSizedBox-UUTUE42J.js

@@ -0,0 +1,112 @@
+// Force strict mode and setup for ESM
+"use strict";
+import {
+  MINIMUM_MAX_HEIGHT,
+  MaxSizedBox,
+  setMaxSizedBoxDebugging
+} from "./chunk-IJVDHPKD.js";
+import "./chunk-FPH6TXD3.js";
+import "./chunk-SV5PQVQE.js";
+import "./chunk-5Q372OFJ.js";
+import "./chunk-WEGXPP5E.js";
+import "./chunk-5QWWOFGG.js";
+import "./chunk-E7REAOTN.js";
+import "./chunk-2MIN6GRR.js";
+import "./chunk-QHTIBUWB.js";
+import "./chunk-RKUWKYED.js";
+import "./chunk-VMDURMFY.js";
+import "./chunk-J7MLXFC5.js";
+import "./chunk-LRKMQPMD.js";
+import "./chunk-LJZSMWOH.js";
+import "./chunk-47SIHHPL.js";
+import "./chunk-JLGFGPZJ.js";
+import "./chunk-SKNVVYIJ.js";
+import "./chunk-UCSV2IZW.js";
+import "./chunk-T2HMXHYA.js";
+import "./chunk-3FSBMAYD.js";
+import "./chunk-XJS54K4A.js";
+import "./chunk-ZPJWUGCS.js";
+import "./chunk-ZWKGZB2K.js";
+import "./chunk-OX44MOAN.js";
+import "./chunk-XYX474JQ.js";
+import "./chunk-GOFAQQZA.js";
+import "./chunk-5M6IDOMF.js";
+import "./chunk-TWPJO254.js";
+import "./chunk-CQ35AJ4Z.js";
+import "./chunk-3UZCLCXR.js";
+import "./chunk-TOF4UZHH.js";
+import "./chunk-O3BUXIPM.js";
+import "./chunk-ZLTEQYNC.js";
+import "./chunk-6PVPNMXU.js";
+import "./chunk-AYVIGUUK.js";
+import "./chunk-IRH27ZC2.js";
+import "./chunk-QHWCP53L.js";
+import "./chunk-JECO75XD.js";
+import "./chunk-O6GEWCJA.js";
+import "./chunk-T26EAKDL.js";
+import "./chunk-LJP2BBMK.js";
+import "./chunk-CPBF7KYF.js";
+import "./chunk-5Y2JCJAH.js";
+import "./chunk-T2CRBIDJ.js";
+import "./chunk-77TOMRBG.js";
+import "./chunk-DEYPMJPD.js";
+import "./chunk-T6OODF2U.js";
+import "./chunk-27ONXAFY.js";
+import "./chunk-ZEADBZLO.js";
+import "./chunk-FN5C6C7G.js";
+import "./chunk-BVE5EMIG.js";
+import "./chunk-MLXTMF7H.js";
+import "./chunk-NAVJD2PQ.js";
+import "./chunk-FVDQ5E67.js";
+import "./chunk-V3GINY6K.js";
+import "./chunk-QHMLYMMS.js";
+import "./chunk-SDVF6A42.js";
+import "./chunk-P3QQPMQA.js";
+import "./chunk-ILPXSKGQ.js";
+import "./chunk-VNOVK4I7.js";
+import "./chunk-SAH4BD2J.js";
+import "./chunk-ZKAZP2ZG.js";
+import "./chunk-DP7LABIB.js";
+import "./chunk-S6LOFUVP.js";
+import "./chunk-2LD5U7Q3.js";
+import "./chunk-DJ2GSRLV.js";
+import "./chunk-I6VVOZDK.js";
+import "./chunk-K2OJUPOE.js";
+import "./chunk-CFKIH3D3.js";
+import "./chunk-EB4VDXNI.js";
+import "./chunk-FJWICLG7.js";
+import "./chunk-UX3IFLJM.js";
+import "./chunk-YRLW2MSX.js";
+import "./chunk-VGC4I5JJ.js";
+import "./chunk-WBT3STGU.js";
+import "./chunk-PVBT5QPD.js";
+import "./chunk-IPQA4SR5.js";
+import "./chunk-WZAD4ZNJ.js";
+import "./chunk-FPGTNKCP.js";
+import "./chunk-SLEWBQWM.js";
+import "./chunk-ICWGPK23.js";
+import "./chunk-XZA32HII.js";
+import "./chunk-7QGEJI7M.js";
+import "./chunk-GTUKW3I6.js";
+import "./chunk-HHJLM3WQ.js";
+import "./chunk-6US7BF3G.js";
+import "./chunk-74TONY4F.js";
+import "./chunk-VL4YX3FH.js";
+import "./chunk-JUIJ3FXC.js";
+import "./chunk-E6FGMDFQ.js";
+import "./chunk-AQ37AY7B.js";
+import "./chunk-RRKNX553.js";
+import "./chunk-KOJ6MHD5.js";
+import "./chunk-2NNTE2ED.js";
+import "./chunk-75DOP5OR.js";
+import "./chunk-DMTGGOSA.js";
+import "./chunk-YQ3U5MUC.js";
+import "./chunk-AMDSOFFV.js";
+import "./chunk-TBWQLLFO.js";
+import "./chunk-5O2XNYP6.js";
+import "./chunk-J2S4EL5Y.js";
+export {
+  MINIMUM_MAX_HEIGHT,
+  MaxSizedBox,
+  setMaxSizedBoxDebugging
+};

package/chunks/{StandaloneSessionPicker-NEWUAPCT.js → StandaloneSessionPicker-XF2TVJFK.js}

@@ -4,142 +4,143 @@ import {
   ConfigContext,
   SessionPicker,
   SettingsContext
-} from "./chunk-3ROKI6MD.js";
-import "./chunk-SKXXO64C.js";
-import "./chunk-KUDADN3R.js";
-import "./chunk-EFT2T2LA.js";
-import "./chunk-L6PFEZUM.js";
-import "./chunk-3SH53ANB.js";
-import "./chunk-5PVLDRGJ.js";
+} from "./chunk-5ZYZPDDF.js";
 import {
   KeypressProvider
-} from "./chunk-QOUFO7TV.js";
-import "./chunk-YX4II73B.js";
+} from "./chunk-O5YGAEQS.js";
+import "./chunk-6E4WHQJV.js";
+import "./chunk-OT26ITEY.js";
+import "./chunk-2FN2HNTI.js";
+import "./chunk-4WGODMVR.js";
+import "./chunk-IJVDHPKD.js";
+import "./chunk-2ZV3CZKI.js";
+import "./chunk-3SH53ANB.js";
+import "./chunk-FPH6TXD3.js";
 import {
   require_jsx_runtime
 } from "./chunk-SV5PQVQE.js";
-import "./chunk-4WGODMVR.js";
-import "./chunk-EKTCKZV5.js";
-import "./chunk-X3PRXXUH.js";
-import "./chunk-KW7NOTN6.js";
 import {
   Box_default,
   render_default,
   use_app_default
 } from "./chunk-5Q372OFJ.js";
+import "./chunk-BKDAF7ES.js";
+import "./chunk-EC5BONC3.js";
+import "./chunk-EKTCKZV5.js";
+import "./chunk-WEGXPP5E.js";
+import "./chunk-KW7NOTN6.js";
 import {
   require_react
 } from "./chunk-5QWWOFGG.js";
-import "./chunk-7UVAWPYG.js";
-import "./chunk-3G6MRLTM.js";
-import "./chunk-RDPKOVXL.js";
-import "./chunk-XYUJPDPB.js";
+import "./chunk-C4WBKZJT.js";
+import "./chunk-NVK4HJYQ.js";
 import "./chunk-E7REAOTN.js";
-import "./chunk-QKSMM4HF.js";
+import "./chunk-L436XFLJ.js";
 import "./chunk-2MIN6GRR.js";
 import "./chunk-QHTIBUWB.js";
 import "./chunk-57OAHC2Y.js";
-import "./chunk-JVTU5JYO.js";
-import "./chunk-YS4H3OFV.js";
+import "./chunk-7AS7QX72.js";
+import "./chunk-MDZO5V2O.js";
 import "./chunk-RKUWKYED.js";
-import "./chunk-AIT6BMBI.js";
+import "./chunk-BDHLBR46.js";
 import "./chunk-GOXKNSDZ.js";
 import "./chunk-IDS7MSUP.js";
-import "./chunk-E6BJFSLJ.js";
+import "./chunk-W2WRNJKX.js";
 import "./chunk-5EJZE3FP.js";
-import "./chunk-FXNLH7E6.js";
+import "./chunk-2CRNTW2B.js";
 import "./chunk-5PA6UEYA.js";
-import "./chunk-NDJ3436G.js";
+import "./chunk-XNXWEGKB.js";
 import "./chunk-NPQ5ZKRP.js";
 import "./chunk-MR3PXB6E.js";
-import "./chunk-DLYJ3RN7.js";
-import "./chunk-EJ5XRNOK.js";
-import "./chunk-HTIG2U5C.js";
+import "./chunk-VMDURMFY.js";
+import "./chunk-J7MLXFC5.js";
+import "./chunk-LRKMQPMD.js";
 import "./chunk-LJZSMWOH.js";
-import "./chunk-2ZH5XAOO.js";
-import "./chunk-DZPWZPGJ.js";
-import "./chunk-LD76HNCC.js";
-import "./chunk-F37T2S4O.js";
-import "./chunk-IKPQM6I5.js";
-import "./chunk-V6R3IEHF.js";
+import "./chunk-47SIHHPL.js";
+import "./chunk-JLGFGPZJ.js";
+import "./chunk-SKNVVYIJ.js";
+import "./chunk-UCSV2IZW.js";
+import "./chunk-T2HMXHYA.js";
+import "./chunk-3FSBMAYD.js";
+import "./chunk-XJS54K4A.js";
 import "./chunk-ZPJWUGCS.js";
-import "./chunk-RLR7K4JJ.js";
-import "./chunk-FZUVUBYH.js";
+import "./chunk-ZWKGZB2K.js";
+import "./chunk-OX44MOAN.js";
 import {
   SessionService
-} from "./chunk-UFWRXRQ5.js";
+} from "./chunk-XYX474JQ.js";
 import "./chunk-GOFAQQZA.js";
 import "./chunk-5M6IDOMF.js";
 import "./chunk-TWPJO254.js";
 import "./chunk-CQ35AJ4Z.js";
-import "./chunk-J54EA46E.js";
-import "./chunk-PQ4RTSTH.js";
-import "./chunk-3E53DKST.js";
-import "./chunk-DV3KOUUU.js";
+import "./chunk-3UZCLCXR.js";
+import "./chunk-TOF4UZHH.js";
+import "./chunk-O3BUXIPM.js";
+import "./chunk-ZLTEQYNC.js";
 import "./chunk-6PVPNMXU.js";
-import "./chunk-R7Q5V3A5.js";
+import "./chunk-AYVIGUUK.js";
 import "./chunk-IRH27ZC2.js";
 import "./chunk-QHWCP53L.js";
-import "./chunk-KDGY3ST4.js";
+import "./chunk-JECO75XD.js";
 import "./chunk-O6GEWCJA.js";
 import "./chunk-T26EAKDL.js";
-import "./chunk-FLTGTSLG.js";
+import "./chunk-LJP2BBMK.js";
 import "./chunk-CPBF7KYF.js";
-import "./chunk-NA6AZRDQ.js";
-import "./chunk-ZB7VDPZB.js";
-import "./chunk-CGWPQ6IM.js";
+import "./chunk-5Y2JCJAH.js";
+import "./chunk-T2CRBIDJ.js";
+import "./chunk-77TOMRBG.js";
 import {
   getGitBranch
-} from "./chunk-RSWDOHXS.js";
-import "./chunk-5X33EPHJ.js";
-import "./chunk-CPZQJP6J.js";
-import "./chunk-UY2JOZK7.js";
-import "./chunk-WANR3VVK.js";
-import "./chunk-3KV5KXKU.js";
+} from "./chunk-DEYPMJPD.js";
+import "./chunk-T6OODF2U.js";
+import "./chunk-27ONXAFY.js";
+import "./chunk-ZEADBZLO.js";
+import "./chunk-FN5C6C7G.js";
+import "./chunk-BVE5EMIG.js";
 import "./chunk-MLXTMF7H.js";
 import "./chunk-NAVJD2PQ.js";
-import "./chunk-OY3ZSNQC.js";
-import "./chunk-AHQBSQYT.js";
+import "./chunk-FVDQ5E67.js";
+import "./chunk-V3GINY6K.js";
 import "./chunk-QHMLYMMS.js";
-import "./chunk-JS55F2GJ.js";
+import "./chunk-SDVF6A42.js";
 import "./chunk-P3QQPMQA.js";
-import "./chunk-O5ONGZGZ.js";
+import "./chunk-ILPXSKGQ.js";
 import "./chunk-VNOVK4I7.js";
 import "./chunk-SAH4BD2J.js";
-import "./chunk-CZIF7I53.js";
-import "./chunk-OWE7TE3F.js";
+import "./chunk-ZKAZP2ZG.js";
+import "./chunk-DP7LABIB.js";
 import "./chunk-S6LOFUVP.js";
 import "./chunk-2LD5U7Q3.js";
 import "./chunk-DJ2GSRLV.js";
-import "./chunk-BOQRZ443.js";
+import "./chunk-I6VVOZDK.js";
 import "./chunk-K2OJUPOE.js";
 import "./chunk-CFKIH3D3.js";
-import "./chunk-27HAGBZG.js";
-import "./chunk-JGDTCEBH.js";
-import "./chunk-EUZE3GSL.js";
+import "./chunk-EB4VDXNI.js";
+import "./chunk-FJWICLG7.js";
+import "./chunk-UX3IFLJM.js";
 import "./chunk-YRLW2MSX.js";
 import "./chunk-VGC4I5JJ.js";
-import "./chunk-QKGJIP2H.js";
-import "./chunk-MTKBZIXU.js";
-import "./chunk-QQQSUCC4.js";
+import "./chunk-WBT3STGU.js";
+import "./chunk-PVBT5QPD.js";
+import "./chunk-IPQA4SR5.js";
 import "./chunk-WZAD4ZNJ.js";
 import "./chunk-FPGTNKCP.js";
-import "./chunk-SIC4S3RX.js";
-import "./chunk-O6CS7VRT.js";
+import "./chunk-SLEWBQWM.js";
+import "./chunk-ICWGPK23.js";
 import "./chunk-XZA32HII.js";
-import "./chunk-UEY5WCRB.js";
-import "./chunk-FNZ42WN7.js";
+import "./chunk-7QGEJI7M.js";
+import "./chunk-GTUKW3I6.js";
 import "./chunk-HHJLM3WQ.js";
-import "./chunk-ZJWFRMCY.js";
+import "./chunk-6US7BF3G.js";
 import "./chunk-74TONY4F.js";
-import "./chunk-DD5XZICM.js";
-import "./chunk-COT2IXPM.js";
-import "./chunk-K623ENWT.js";
+import "./chunk-VL4YX3FH.js";
+import "./chunk-JUIJ3FXC.js";
+import "./chunk-E6FGMDFQ.js";
 import "./chunk-AQ37AY7B.js";
-import "./chunk-SJLW5XGQ.js";
-import "./chunk-3LUGIYS3.js";
-import "./chunk-VLEGGCEA.js";
-import "./chunk-MFSV57XN.js";
+import "./chunk-RRKNX553.js";
+import "./chunk-KOJ6MHD5.js";
+import "./chunk-2NNTE2ED.js";
+import "./chunk-EKP3M4RF.js";
 import {
   writeStdoutLine
 } from "./chunk-KGJGEEVR.js";

package/chunks/{acp-startup-profiler-T4GEAPLX.js → acp-startup-profiler-GNYAL6LI.js}

@@ -9,8 +9,8 @@ import {
   markAcpStartup,
   recordAcpConfigStartupEvent,
   resetAcpStartupProfilerForTesting
-} from "./chunk-7KOFLDEP.js";
-import "./chunk-LURJYO2T.js";
+} from "./chunk-5JTIYALA.js";
+import "./chunk-OZ6KS6KW.js";
 import "./chunk-5O2XNYP6.js";
 import "./chunk-J2S4EL5Y.js";
 export {