@qwen-code/qwen-code 0.23.2 → 0.23.3

package/bundled/review/references/posting.md

@@ -103,28 +103,45 @@ Read `.qwen/tmp/qwen-review-{target}-presubmit.json`. Schema:
   existingComments: {
     total: number;
     byBucket: { stale, resolved, overlap, repost, noConflict: number };
-                                 // repost entries are a SUBSET of overlap and
-                                 // are counted in both: every re-post target
-                                 // is also an overlap
+                                 // a top-level re-post target is ALSO an
+                                 // overlap and is counted in both; the
+                                 // pipeline's own carry-REPLY inside a
+                                 // replied-to thread appears in repost ONLY
+                                 // (an exemption carrier, never an overlap)
                                  // Comment = { id, path, line, commit_id,
                                  //   body — an 80-char excerpt,
                                  //   user? — the author login when known }
     overlap: Comment[];          // BLOCK on submit — except a finding whose
-                                 // id matches a repost entry at the same
-                                 // location (see repost below)
+                                 // id appears in matchedIds of ANY repost
+                                 // entry, wherever that entry sits (see
+                                 // repost below)
     repost: (Comment & { matchedIds: string[] })[];
-                                 // overlap comments matched as re-post
-                                 // targets — by a carried-id prefix in the
-                                 // claim line, or (when unambiguous) a truly
-                                 // id-less own-account original — exempt
-                                 // those findings from the drop (see below)
+                                 // a ROOT leg's matchedIds are the ids of
+                                 // findings at that entry's own location; a
+                                 // carry-reply leg's are id-joined, and its
+                                 // path/line are the reply's own anchor
+                                 // (`original_line` when GitHub unmapped it,
+                                 // else 0) — never null
+                                 // re-post targets: overlap comments matched
+                                 // by a carried-id prefix in the claim line,
+                                 // or (when unambiguous) a truly id-less
+                                 // own-account original, at the finding's
+                                 // location; PLUS the pipeline's own carry-
+                                 // reply carrying a wanted id, at ANY
+                                 // location (in repost only) — exempt those
+                                 // findings from the drop (see below)
     stale: Comment[];            // log "Skipped N stale ..."
     resolved: Comment[];         // log "Skipped N replied-to ..."
     noConflict: Comment[];       // log "Found N prior with no overlap ..."
   };
   downgradeApprove: boolean;        // submit COMMENT instead of APPROVE
   downgradeRequestChanges: boolean; // submit COMMENT instead of REQUEST_CHANGES (self-PR only)
-  downgradeReasons: string[];       // human-readable; join with '; ' for body
+  downgradeReasons: string[];       // human-readable; copy them into the
+                                    // compose state — `compose-review` caps
+                                    // each at 400 code points (a longer one
+                                    // is cut and ends in `…`), drops the
+                                    // ones past a 2000-point total, and
+                                    // joins and escapes what is left
   blockOnExistingComments: boolean; // one or more overlaps — drop those findings
                                     // (except carried-id re-posts, see below)
   findingsFileInvalid: boolean;     // the --new-findings file was unreadable:
@@ -150,9 +167,9 @@ Read `.qwen/tmp/qwen-review-{target}-presubmit.json`. Schema:
 
 **Apply the report:**
 
-- `blockOnExistingComments=true` → **an overlap is a duplicate; the disposal is deterministic — do not ask the user.** Drop each finding whose `(path, line)` appears in `existingComments.overlap` from your `comments` array — **except a finding whose `id` appears in `matchedIds` of an `existingComments.repost` entry at the same location**: that is a Step 6 ledger re-post, and re-posting under the original id is exactly how the id survives into the next round's marker — GitHub stacks it in the original thread, which is where it belongs. The inline counts follow automatically, because `submit` counts the comments you actually attach, so a dropped Critical is simply no longer there to count (and a dropped Critical that was already on the PR does not belong in `state.bodyCriticals` either). List each dropped finding in the terminal summary as "already reported at <path>:<line> — comment <id> (by <user>): <excerpt>", taking `<id>`, `<user>` (omit the `(by <user>)` slot when the entry carries no `user`), and the 80-char `<excerpt>` from the overlapping comment (`existingComments.overlap` entries carry all three), and submit the remainder without pausing. Naming the author is what makes an authorship-refused re-post exemption self-explanatory: the drop line then shows a DIFFERENT author next to the matching id. Name the comment on EVERY drop — that is what makes a same-line false positive visible to the operator instead of a bare location. This decision point has been improvised as an interactive question, which stalls a headless run forever (measured; DESIGN.md — The interactive overlap question); the Exclusion Criteria already forbid re-reporting discussed issues, so there is nothing to ask. (If dropping overlaps leaves zero findings, that is still not a question: submit with an empty `comments` array like any other run — `submit` composes the body from `state`, and a run with nothing to add posts whatever that computes. A recap like "all already reported, N resolved by `<sha>`, two still standing" goes in the **terminal summary**, not the PR: `compose-review` has no free-text body field to carry it (see Step 7 — you do not author PR-facing prose), and it is never a `gh pr comment` — a hand-posted issue comment bypasses the authorisation gate, the downgrade semantics, and the `posted` contract all at once.)
+- `blockOnExistingComments=true` → **an overlap is a duplicate; the disposal is deterministic — do not ask the user.** Drop each finding whose `(path, line)` appears in `existingComments.overlap` from your `comments` array — **except a finding whose `id` appears in `matchedIds` of ANY `existingComments.repost` entry** — a root leg matches at the finding's `(path, line)`, while a carry-reply leg (the pipeline's own reply inside a replied-to thread) matches on the id alone and its own `path`/`line` are the REPLY's — `original_line` when GitHub unmapped the anchor, else `0`, never null — which is routinely not where the finding sits, so never re-check the location: that is a Step 6 ledger re-post, and re-posting under the original id is exactly how the id survives into the next round's marker. Keep it in the array — on GitHub, `submit` posts it as a **reply in that original thread** rather than a new inline comment (the Create Review API opens a new thread per comment; only the replies endpoint joins one), so the finding keeps one thread across rounds instead of accumulating one per round (GitHub only: an Aone target has no review-thread graph, and the re-post stays inline there). Whenever the posting pass cannot reach an unresolved thread this account opened under the id — a resolved or gone original, a foreign or id-less root, a `(fix-induced)` re-report, or a draft that finds every live thread under the id already answered this round — the re-post goes inline and opens a fresh thread; the exemption is what lets it through to do either. The inline counts follow automatically, because `submit` counts the comments you actually attach, so a dropped Critical is simply no longer there to count (and a dropped Critical that was already on the PR does not belong in `state.bodyCriticals` either). List each dropped finding in the terminal summary as "already reported at <path>:<line> — comment <id> (by <user>): <excerpt>", taking `<id>`, `<user>` (omit the `(by <user>)` slot when the entry carries no `user`), and the 80-char `<excerpt>` from the overlapping comment (`existingComments.overlap` entries carry all three), and submit the remainder without pausing. Naming the author is what makes an authorship-refused re-post exemption self-explanatory: the drop line then shows a DIFFERENT author next to the matching id. Name the comment on EVERY drop — that is what makes a same-line false positive visible to the operator instead of a bare location. This decision point has been improvised as an interactive question, which stalls a headless run forever (measured; DESIGN.md — The interactive overlap question); the Exclusion Criteria already forbid re-reporting discussed issues, so there is nothing to ask. (If dropping overlaps leaves zero findings, that is still not a question: submit with an empty `comments` array like any other run — `submit` composes the body from `state`, and a run with nothing to add posts whatever that computes. A recap like "all already reported, N resolved by `<sha>`, two still standing" goes in the **terminal summary**, not the PR: `compose-review` has no free-text body field to carry it (see Step 7 — you do not author PR-facing prose), and it is never a `gh pr comment` — a hand-posted issue comment bypasses the authorisation gate, the downgrade semantics, and the `posted` contract all at once.)
 - `downgradeApprove` / `downgradeRequestChanges` / `downgradeReasons` → **do not apply these by hand.** Copy them into the `presubmit` field of the `compose-review` input (listed with the state fields in Step 6's Verdict section); the subcommand owns the semantics its tests pin — a downgrade fires only when the verdict it names is the one on the table (a Suggestion-only review is already Comment, so nothing is downgraded and no "Downgraded" sentence is emitted), the downgrade sentence carries the reasons, and a downgraded Request changes keeps its body Criticals after the sentence so the self-PR downgrade never erases the only copy of a blocker.
-- `headDrift.drifted=true` → **commits nobody reviewed are on the PR; the verdict can no longer certify the pull request as it stands.** The Approve cap has already fired through the downgrade machinery (the reason names both SHAs — it rides into the body with the other reasons; never hand-apply). What happens to the _submission_ is decided by **`headDrift.anchorsAtRisk`, which presubmit computes — do not re-derive it by hand**: pass `--new-findings` so it has your anchors, and it rules fail-safe on every hole a hand intersection falls into (a truncated `filesTouched` list (measured; DESIGN.md — The 283-file drift cap), the compare API's own 300-file ceiling, a `diverged` force-push, an unavailable compare, or a missing findings list). **`--new-findings` must carry EVERY finding's file, not only the inline-anchored ones** — a body-only Critical (one that could not be mapped to a diff line) still names a file, and if that file is omitted a drift touching it reads as `anchorsAtRisk=false`; include one `{path, line}` per body Critical (any placeholder `line`, e.g. `1`, and NO `id` — the drift intersection keys on `path` only, but the carried-id re-post exemption intersects on `(path, line)` plus id, so a placeholder line carrying an id could alias an inline finding's location and corrupt its exemption; a body-only Critical is never posted inline and can never be a re-post target). **`anchorsAtRisk=true`**: the anchors themselves are at risk and the findings may already be fixed — apply the 422-recovery rule _proactively_: abandon this submission, say so, and restart at the new SHA from Step 1's `fetch-pr`. **One exception — the CI salvage contract:** when the environment carries `QWEN_REVIEW_SALVAGE_POST=1` **and** the file named by `QWEN_CI_REVIEW_SALVAGE_OK_FILE` exists with content equal to `headDrift.reviewedSha`, the workflow's supersede watcher has already ruled this run salvage-eligible and a queued replacement run owns the new head — do **not** restart: submit as planned exactly as in the `anchorsAtRisk=false` branch (the review is of `fetchedSha`, the downgrade sentence names the drift, and the workflow's gh guard admits the post against that pinned head), and this consumes no restart. Either half missing — an explicit run exports no signal, and a marker alone is forgeable — and the rule above stands. **`anchorsAtRisk=false`**: submit as planned — the review is of `fetchedSha` (`submit` posts that very SHA as `commit_id`), the body's downgrade sentence says so, and if GitHub still answers 422 the recovery path below takes over. Name the drift in the terminal summary either way.
+- `headDrift.drifted=true` → **commits nobody reviewed are on the PR; the verdict can no longer certify the pull request as it stands.** The Approve cap has already fired through the downgrade machinery (the reason names both SHAs — it rides into the body with the other reasons; never hand-apply). What happens to the _submission_ is decided by **`headDrift.anchorsAtRisk`, which presubmit computes — do not re-derive it by hand**: pass `--new-findings` so it has your anchors, and it rules fail-safe on every hole a hand intersection falls into (a truncated `filesTouched` list (measured; DESIGN.md — The 283-file drift cap), the compare API's own 300-file ceiling, a `diverged` force-push, an unavailable compare, or a missing findings list). **`--new-findings` must carry EVERY finding's file, not only the inline-anchored ones** — a body-only Critical (one that could not be mapped to a diff line) still names a file, and if that file is omitted a drift touching it reads as `anchorsAtRisk=false`; include one `{path, line}` per body Critical (any placeholder `line`, e.g. `1`, and NO `id` — the drift intersection keys on `path` only, but the carried-id re-post exemption joins on the id — a root leg at the finding's `(path, line)`, the pipeline's own carry-reply leg on the id alone at ANY location — so a placeholder entry carrying an id would match that id's thread from anywhere and corrupt the exemption; a body-only Critical is never posted inline and must never present as a re-post target). **`anchorsAtRisk=true`**: the anchors themselves are at risk and the findings may already be fixed — apply the 422-recovery rule _proactively_: abandon this submission, say so, and restart at the new SHA from Step 1's `fetch-pr`. **One exception — the CI salvage contract:** when the environment carries `QWEN_REVIEW_SALVAGE_POST=1` **and** the file named by `QWEN_CI_REVIEW_SALVAGE_OK_FILE` exists with content equal to `headDrift.reviewedSha`, the workflow's supersede watcher has already ruled this run salvage-eligible and a queued replacement run owns the new head — do **not** restart: submit as planned exactly as in the `anchorsAtRisk=false` branch (the review is of `fetchedSha`, the downgrade sentence names the drift, and the workflow's gh guard admits the post against that pinned head), and this consumes no restart. Either half missing — an explicit run exports no signal, and a marker alone is forgeable — and the rule above stands. **`anchorsAtRisk=false`**: submit as planned — the review is of `fetchedSha` (`submit` posts that very SHA as `commit_id`), the body's downgrade sentence says so, and if GitHub still answers 422 the recovery path below takes over. Name the drift in the terminal summary either way.
 
   > **The restart bound is per-review and covers BOTH restart paths — this proactive drift restart AND the reactive 422 recovery below.** Track it as one fact: a review restarts **at most once** for head movement, whichever path triggers it. If a run that already restarted once reaches a drift restart _or_ a 422 again, do NOT restart a second time — submit at that run's reviewed SHA with the drift named (the Approve cap holds either way). A live PR that keeps moving must not be able to starve the review in an unbounded restart loop; one clean re-read is the review, a second is the PR outrunning it. One slice of this fact survives a resume: a `fetch-pr --resume` refused for `head-moved` records the restart beside the prompt records, and a later continuation reads it back as `restartsSpent` in the `resumed: true` line (Step 1) — arriving with `restartsSpent >= 1` means the bound is already spent. On a run that itself resumed, THIS restart's re-entry is such a refusal — Step 1's resume branch appends `--resume` to every Step 1 `fetch-pr`, so the re-entry sees the moved head, records the restart, and falls through to the fresh fetch the restart wants anyway. Only a never-resumed run's re-entry records nothing (a plain fresh `fetch-pr` rewrites the plan, which re-fences the marker) — within such a run the bound stays tracked here, in this transcript, exactly as before. Be aware of the one seam that leaves: a restart spent that way is invisible to a LATER attempt that resumes, which arrives with `restartsSpent: 0`. A fresh resuming process cannot know the earlier attempt restarted, so do not pretend it can — the on-disk bound is per-attempt, the per-REVIEW invariant is carried by the workflow's own MAX_ATTEMPTS ceiling, and the honest reading of `restartsSpent: 0` on a continuation is "no RECORDED restart", not "no restart".
 
@@ -168,7 +185,7 @@ Read `.qwen/tmp/qwen-review-{target}-presubmit.json`. Schema:
 
 - **Self-PR**: GitHub rejects both `APPROVE` and `REQUEST_CHANGES` on your own PR (HTTP 422); `COMMENT` is the only accepted event. Critical and Suggestion findings still appear as inline `comments` regardless, so substantive feedback is preserved.
 - **CI failure / pending**: the LLM review reads code statically and cannot see runtime test failures. Approving on red CI is misleading; pending CI means the verdict is premature.
-- **Overlap with existing comments**: posting on the same `(path, line)` as an existing Qwen comment produces visual duplicates, so overlapping findings are dropped rather than re-posted — with one exception by construction: a carried-id re-post belongs in the original thread (GitHub stacks same-line comments there), so a finding whose ledger id matches the existing comment at its location is exempted via `existingComments.repost`, and every drop names the overlapping comment so a same-line false positive stays visible. The match reads the id as the claim-line PREFIX (mirroring how the ledger marker reads it back), and a truly id-less OWN-account original is still matched when the target is unambiguous — exactly one own-account comment at the location and exactly one carried finding there (round-1 originals carry no id token; without this fallback their re-post would read as a plain overlap and be dropped). **Known limitation — the residue is the AMBIGUOUS case only**: an id-less original at a location with several own-account comments, or several carried ids at the location, or an id-less original whose body still mentions ANY ledger-id-shaped token (even a cross-reference — any token marks the comment as belonging to a specific finding's thread, so the fallback stays off), cannot be matched as a re-post target; the re-post of such a finding reads as a plain location overlap and is dropped — visibly, the drop log names the comment. A same-SHA re-run after an already-posted re-post can match that earlier re-post as the target and post a second copy (the two are structurally indistinguishable); the lineage self-heals next round through the new comment's prefix. A replied-to original still counts toward the ambiguity decision but is itself bucketed `resolved`, never a target. Stale-commit and replied-to comments are skipped silently — they're false-positive overlap from line-based matching.
+- **Overlap with existing comments**: posting on the same `(path, line)` as an existing Qwen comment produces visual duplicates, so overlapping findings are dropped rather than re-posted — with one exception by construction: a carried-id re-post belongs in the original thread, and `submit` puts it there (replying into the thread its ledger id names rather than opening a new one — same-line re-posts do NOT stack on their own, which is how one finding used to accumulate a thread per round), so a finding whose ledger id matches an own existing comment — a root at the finding's location, or the pipeline's own carry-reply in that id's thread, wherever its anchor now sits — is exempted via `existingComments.repost`, and every drop names the overlapping comment so a same-line false positive stays visible. The match reads the id as the claim-line PREFIX (mirroring how the ledger marker reads it back), and a truly id-less OWN-account original is still matched when the target is unambiguous — exactly one own-account comment at the location and exactly one carried finding there (round-1 originals carry no id token; without this fallback their re-post would read as a plain overlap and be dropped). **Known limitation — the residue is the AMBIGUOUS case only**: an id-less original at a location with several own-account comments, or several carried ids at the location, or an id-less original whose body still mentions ANY ledger-id-shaped token (even a cross-reference — any token marks the comment as belonging to a specific finding's thread, so the fallback stays off), cannot be matched as a re-post target; the re-post of such a finding reads as a plain location overlap and is dropped — visibly, the drop log names the comment. A same-SHA re-run after an already-posted re-post posts a second copy — under the reply mechanism, as a second reply in the same thread (the replied-to original is bucketed `resolved` and skipped by the overlap check, and the pipeline's own carry-reply inside that thread still carries the id as a `repost` exemption — so the re-post is not dropped even when another own comment overlaps the location); the thread stays one thread either way. A replied-to original still counts toward the ambiguity decision but is itself bucketed `resolved`, never a target. Stale-commit and replied-to comments are skipped silently — they're false-positive overlap from line-based matching.
 
 ⚠️ **Severity routing — high-confidence Critical AND Suggestion findings both go inline, pinned to the exact code line.** They are distinguished by the `**[Critical]**` / `**[Suggestion]**` prefix in the comment body, not by where they are posted.
 

package/chunks/{MaxSizedBox-4C3BKKKY.js → MaxSizedBox-D4LW7RZZ.js}

@@ -7,106 +7,113 @@ import {
 } from "./chunk-2UWQX4FP.js";
 import "./chunk-4LIPOIXS.js";
 import "./chunk-SV5PQVQE.js";
-import "./chunk-2XRE4KE4.js";
 import "./chunk-O4KNCAX4.js";
 import "./chunk-5QWWOFGG.js";
+import "./chunk-2XRE4KE4.js";
 import "./chunk-47ECGEJC.js";
 import "./chunk-2MIN6GRR.js";
 import "./chunk-QHTIBUWB.js";
 import "./chunk-RKUWKYED.js";
-import "./chunk-GOEVQADN.js";
+import "./chunk-BZM5U74J.js";
 import "./chunk-GELRJXE2.js";
 import "./chunk-32CM56LO.js";
-import "./chunk-OXR34GCD.js";
-import "./chunk-2EKVPSIJ.js";
+import "./chunk-AEY27Z35.js";
+import "./chunk-Y2MYW47X.js";
 import "./chunk-LJZSMWOH.js";
-import "./chunk-YZTGGCEE.js";
-import "./chunk-2WC3Y7YY.js";
-import "./chunk-IWABUX6T.js";
+import "./chunk-F42YYSCK.js";
+import "./chunk-NUQVB25K.js";
+import "./chunk-ZKZHSB5W.js";
+import "./chunk-MSNHNAQZ.js";
 import "./chunk-DJXSOEFB.js";
-import "./chunk-YQGW3M6Z.js";
-import "./chunk-J3VZF2AL.js";
-import "./chunk-OWCFKIFQ.js";
-import "./chunk-ZPJWUGCS.js";
-import "./chunk-X7LFJF5D.js";
+import "./chunk-ZKYR7QS4.js";
+import "./chunk-532WHF4F.js";
 import "./chunk-BUQN5LTI.js";
-import "./chunk-XDNFODER.js";
-import "./chunk-GOKAOSCN.js";
-import "./chunk-VNOVK4I7.js";
-import "./chunk-HJ5UJQQL.js";
+import "./chunk-ZPJWUGCS.js";
+import "./chunk-LK2WUCDQ.js";
+import "./chunk-UKZ45TJL.js";
+import "./chunk-RLLRJJDR.js";
+import "./chunk-N7VWZDWW.js";
 import "./chunk-GOFAQQZA.js";
-import "./chunk-65I7S4Z3.js";
-import "./chunk-6HUXPLB5.js";
 import "./chunk-TWPJO254.js";
 import "./chunk-CQ35AJ4Z.js";
-import "./chunk-XKBFYTCD.js";
-import "./chunk-LYT2OU7D.js";
+import "./chunk-65I7S4Z3.js";
+import "./chunk-6HUXPLB5.js";
 import "./chunk-7CLLH5TI.js";
-import "./chunk-HIXUUCGY.js";
-import "./chunk-6PVPNMXU.js";
-import "./chunk-565U2ANU.js";
-import "./chunk-GSFV5RQW.js";
+import "./chunk-XKBFYTCD.js";
+import "./chunk-ZTTC7T4X.js";
+import "./chunk-E4UEO3XM.js";
+import "./chunk-IAEXTMED.js";
 import "./chunk-IRH27ZC2.js";
 import "./chunk-QHWCP53L.js";
 import "./chunk-F53KKZUD.js";
-import "./chunk-TRWQQBVH.js";
-import "./chunk-QJNDUTOL.js";
-import "./chunk-N6S3NUYJ.js";
 import "./chunk-O6GEWCJA.js";
+import "./chunk-36HCNKDS.js";
+import "./chunk-6PVPNMXU.js";
+import "./chunk-2SZH22YO.js";
+import "./chunk-DTNV6UZY.js";
+import "./chunk-QJNDUTOL.js";
+import "./chunk-JXNIF2O5.js";
+import "./chunk-NFYEQRLG.js";
+import "./chunk-ELRMZTPF.js";
 import "./chunk-CHEIIBT3.js";
-import "./chunk-QAZ2MGYT.js";
-import "./chunk-QQK4L3UU.js";
+import "./chunk-PLLIWEM3.js";
+import "./chunk-5GLDOLNQ.js";
 import "./chunk-CH2YDT6X.js";
 import "./chunk-JX6XHPTX.js";
-import "./chunk-CLKE4IY3.js";
 import "./chunk-ZSTCM3MX.js";
-import "./chunk-SOA4HKRJ.js";
 import "./chunk-MLXTMF7H.js";
-import "./chunk-3LPJ776W.js";
+import "./chunk-LILGKQ4B.js";
 import "./chunk-3CZ2BQV6.js";
-import "./chunk-PQEISIKS.js";
-import "./chunk-S5QR6CB5.js";
-import "./chunk-H3Q3RSKZ.js";
+import "./chunk-SAH4BD2J.js";
+import "./chunk-CXTPVBFA.js";
+import "./chunk-U7O65WKL.js";
 import "./chunk-S6LOFUVP.js";
+import "./chunk-FN3JNDRU.js";
+import "./chunk-EUURTIV6.js";
+import "./chunk-G6UUOCUT.js";
+import "./chunk-IZ2U57NY.js";
+import "./chunk-NUQ4GK5I.js";
+import "./chunk-K2OJUPOE.js";
+import "./chunk-AXTFYDXT.js";
 import "./chunk-NAVJD2PQ.js";
-import "./chunk-OFVAS4AR.js";
+import "./chunk-YBUMTY7B.js";
 import "./chunk-HNLMYDQE.js";
 import "./chunk-QHMLYMMS.js";
+import "./chunk-VNOVK4I7.js";
 import "./chunk-CFKIH3D3.js";
-import "./chunk-VBLAI2HA.js";
+import "./chunk-JL6APGBX.js";
 import "./chunk-DJ2GSRLV.js";
 import "./chunk-4ALNJDHL.js";
 import "./chunk-NOO4QFXM.js";
 import "./chunk-KFFCDLKV.js";
-import "./chunk-7OCIQNKX.js";
-import "./chunk-F2NYVASI.js";
+import "./chunk-ZW2EUO2A.js";
+import "./chunk-HBU7EKY4.js";
 import "./chunk-5ETULJLP.js";
-import "./chunk-XBVNNDPK.js";
+import "./chunk-ZHKTKHMO.js";
 import "./chunk-VGC4I5JJ.js";
-import "./chunk-J6MB5ZHZ.js";
 import "./chunk-EDIDYZBT.js";
 import "./chunk-HD7O6WLV.js";
+import "./chunk-J6MB5ZHZ.js";
 import "./chunk-WZAD4ZNJ.js";
+import "./chunk-3FPYT6QC.js";
 import "./chunk-FPGTNKCP.js";
 import "./chunk-TIGXX4PA.js";
-import "./chunk-JO77FGNZ.js";
+import "./chunk-3UXUOFO6.js";
 import "./chunk-XFFRI3WM.js";
-import "./chunk-4HOEU2OR.js";
+import "./chunk-ERU3SDXT.js";
+import "./chunk-EWJTAP3Y.js";
 import "./chunk-HHJLM3WQ.js";
-import "./chunk-7VEYUF3N.js";
+import "./chunk-W5ZQMAEM.js";
 import "./chunk-74TONY4F.js";
-import "./chunk-E6TI726I.js";
-import "./chunk-4VY3ITHR.js";
-import "./chunk-O2FEO2CB.js";
-import "./chunk-G6UUOCUT.js";
-import "./chunk-IZ2U57NY.js";
-import "./chunk-MWIO7MF6.js";
+import "./chunk-HUXPEUFL.js";
+import "./chunk-TP6FYVQT.js";
 import "./chunk-ZAFYHRVY.js";
+import "./chunk-TBWQLLFO.js";
+import "./chunk-UKMWZ5NS.js";
 import "./chunk-75DOP5OR.js";
 import "./chunk-DMTGGOSA.js";
 import "./chunk-YQ3U5MUC.js";
 import "./chunk-MATEIJZF.js";
-import "./chunk-TBWQLLFO.js";
 import "./chunk-5O2XNYP6.js";
 import "./chunk-J2S4EL5Y.js";
 export {

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

@@ -4,24 +4,22 @@ import {
   ConfigContext,
   SessionPicker,
   SettingsContext
-} from "./chunk-LEAOJ43M.js";
-import "./chunk-B25JYXZE.js";
-import "./chunk-WXD7INFV.js";
+} from "./chunk-DAWWT2ID.js";
 import {
   KeypressProvider
-} from "./chunk-A7EFXK7P.js";
-import "./chunk-CWVZBIZJ.js";
-import "./chunk-TOOOLHVS.js";
-import "./chunk-22GORRNY.js";
-import "./chunk-UYDQYDW2.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-KW7NOTN6.js";
 import "./chunk-2UWQX4FP.js";
+import "./chunk-IL5M5NYD.js";
+import "./chunk-QMUYLYT5.js";
 import "./chunk-4LIPOIXS.js";
 import {
   require_jsx_runtime
 } from "./chunk-SV5PQVQE.js";
-import "./chunk-2XRE4KE4.js";
 import {
   Box_default,
   render_default,
@@ -30,130 +28,139 @@ import {
 import {
   require_react
 } from "./chunk-5QWWOFGG.js";
-import "./chunk-R457KFV7.js";
-import "./chunk-RM244SCQ.js";
-import "./chunk-WXFCI3O5.js";
-import "./chunk-XQ4RDO5B.js";
+import "./chunk-LG5Y4OWO.js";
+import "./chunk-WBCPROWX.js";
 import "./chunk-EKTCKZV5.js";
-import "./chunk-ERXNTINK.js";
+import "./chunk-2XRE4KE4.js";
+import "./chunk-KW7NOTN6.js";
+import "./chunk-GCDXVPFK.js";
+import "./chunk-AC6KDLH3.js";
 import "./chunk-47ECGEJC.js";
+import "./chunk-6JACAGYH.js";
 import "./chunk-2MIN6GRR.js";
 import "./chunk-QHTIBUWB.js";
+import "./chunk-TWUKBNWM.js";
 import "./chunk-57OAHC2Y.js";
-import "./chunk-QHLHE2OT.js";
-import "./chunk-WBU2PIZ5.js";
-import "./chunk-XSOXPG2L.js";
+import "./chunk-7BXXIQG4.js";
 import "./chunk-RKUWKYED.js";
+import "./chunk-ZU47FBOC.js";
+import "./chunk-NOAG7N22.js";
 import "./chunk-BW4333PP.js";
+import "./chunk-VX63RJXE.js";
 import "./chunk-IDS7MSUP.js";
-import "./chunk-CRZBDVP2.js";
+import "./chunk-VZUCTJ2P.js";
 import "./chunk-5EJZE3FP.js";
-import "./chunk-5BH2AIEY.js";
-import "./chunk-QTNCGZHQ.js";
-import "./chunk-NX7ZTXFF.js";
+import "./chunk-53GWJOLP.js";
 import "./chunk-NPQ5ZKRP.js";
 import "./chunk-MR3PXB6E.js";
-import "./chunk-GOEVQADN.js";
+import "./chunk-BZM5U74J.js";
 import "./chunk-GELRJXE2.js";
 import "./chunk-32CM56LO.js";
-import "./chunk-OXR34GCD.js";
-import "./chunk-2EKVPSIJ.js";
+import "./chunk-AEY27Z35.js";
+import "./chunk-Y2MYW47X.js";
 import "./chunk-LJZSMWOH.js";
-import "./chunk-YZTGGCEE.js";
-import "./chunk-2WC3Y7YY.js";
-import "./chunk-IWABUX6T.js";
+import "./chunk-F42YYSCK.js";
+import "./chunk-NUQVB25K.js";
+import "./chunk-ZKZHSB5W.js";
+import "./chunk-MSNHNAQZ.js";
 import "./chunk-DJXSOEFB.js";
-import "./chunk-YQGW3M6Z.js";
-import "./chunk-J3VZF2AL.js";
-import "./chunk-OWCFKIFQ.js";
-import "./chunk-ZPJWUGCS.js";
-import "./chunk-X7LFJF5D.js";
+import "./chunk-ZKYR7QS4.js";
+import "./chunk-532WHF4F.js";
 import "./chunk-BUQN5LTI.js";
-import "./chunk-XDNFODER.js";
-import "./chunk-GOKAOSCN.js";
-import "./chunk-VNOVK4I7.js";
+import "./chunk-ZPJWUGCS.js";
+import "./chunk-LK2WUCDQ.js";
+import "./chunk-UKZ45TJL.js";
+import "./chunk-RLLRJJDR.js";
 import {
   SessionService
-} from "./chunk-HJ5UJQQL.js";
+} from "./chunk-N7VWZDWW.js";
 import "./chunk-GOFAQQZA.js";
-import "./chunk-65I7S4Z3.js";
-import "./chunk-6HUXPLB5.js";
 import "./chunk-TWPJO254.js";
 import "./chunk-CQ35AJ4Z.js";
-import "./chunk-XKBFYTCD.js";
-import "./chunk-LYT2OU7D.js";
+import "./chunk-65I7S4Z3.js";
+import "./chunk-6HUXPLB5.js";
 import "./chunk-7CLLH5TI.js";
-import "./chunk-HIXUUCGY.js";
-import "./chunk-6PVPNMXU.js";
-import "./chunk-565U2ANU.js";
-import "./chunk-GSFV5RQW.js";
+import "./chunk-XKBFYTCD.js";
+import "./chunk-ZTTC7T4X.js";
+import "./chunk-E4UEO3XM.js";
+import "./chunk-IAEXTMED.js";
 import "./chunk-IRH27ZC2.js";
 import "./chunk-QHWCP53L.js";
 import "./chunk-F53KKZUD.js";
-import "./chunk-TRWQQBVH.js";
-import "./chunk-QJNDUTOL.js";
-import "./chunk-N6S3NUYJ.js";
 import "./chunk-O6GEWCJA.js";
+import "./chunk-36HCNKDS.js";
+import "./chunk-6PVPNMXU.js";
+import "./chunk-2SZH22YO.js";
+import "./chunk-DTNV6UZY.js";
+import "./chunk-QJNDUTOL.js";
+import "./chunk-JXNIF2O5.js";
+import "./chunk-NFYEQRLG.js";
+import "./chunk-ELRMZTPF.js";
 import "./chunk-CHEIIBT3.js";
-import "./chunk-QAZ2MGYT.js";
-import "./chunk-QQK4L3UU.js";
+import "./chunk-PLLIWEM3.js";
+import "./chunk-5GLDOLNQ.js";
 import "./chunk-CH2YDT6X.js";
 import "./chunk-JX6XHPTX.js";
-import "./chunk-CLKE4IY3.js";
 import "./chunk-ZSTCM3MX.js";
-import "./chunk-SOA4HKRJ.js";
 import "./chunk-MLXTMF7H.js";
-import "./chunk-3LPJ776W.js";
+import "./chunk-LILGKQ4B.js";
 import {
   getGitBranch
 } from "./chunk-3CZ2BQV6.js";
-import "./chunk-PQEISIKS.js";
-import "./chunk-S5QR6CB5.js";
-import "./chunk-H3Q3RSKZ.js";
+import "./chunk-SAH4BD2J.js";
+import "./chunk-CXTPVBFA.js";
+import "./chunk-U7O65WKL.js";
 import "./chunk-S6LOFUVP.js";
+import "./chunk-FN3JNDRU.js";
+import "./chunk-EUURTIV6.js";
+import "./chunk-G6UUOCUT.js";
+import "./chunk-IZ2U57NY.js";
+import "./chunk-NUQ4GK5I.js";
+import "./chunk-K2OJUPOE.js";
+import "./chunk-AXTFYDXT.js";
 import "./chunk-NAVJD2PQ.js";
-import "./chunk-OFVAS4AR.js";
+import "./chunk-YBUMTY7B.js";
 import "./chunk-HNLMYDQE.js";
 import "./chunk-QHMLYMMS.js";
+import "./chunk-VNOVK4I7.js";
 import "./chunk-CFKIH3D3.js";
-import "./chunk-VBLAI2HA.js";
+import "./chunk-JL6APGBX.js";
 import "./chunk-DJ2GSRLV.js";
 import "./chunk-4ALNJDHL.js";
 import "./chunk-NOO4QFXM.js";
 import "./chunk-KFFCDLKV.js";
-import "./chunk-7OCIQNKX.js";
-import "./chunk-F2NYVASI.js";
+import "./chunk-ZW2EUO2A.js";
+import "./chunk-HBU7EKY4.js";
 import "./chunk-5ETULJLP.js";
-import "./chunk-XBVNNDPK.js";
+import "./chunk-ZHKTKHMO.js";
 import "./chunk-VGC4I5JJ.js";
-import "./chunk-J6MB5ZHZ.js";
 import "./chunk-EDIDYZBT.js";
 import "./chunk-HD7O6WLV.js";
+import "./chunk-J6MB5ZHZ.js";
 import "./chunk-WZAD4ZNJ.js";
+import "./chunk-3FPYT6QC.js";
 import "./chunk-FPGTNKCP.js";
 import "./chunk-TIGXX4PA.js";
-import "./chunk-JO77FGNZ.js";
+import "./chunk-3UXUOFO6.js";
 import "./chunk-XFFRI3WM.js";
-import "./chunk-4HOEU2OR.js";
+import "./chunk-ERU3SDXT.js";
+import "./chunk-EWJTAP3Y.js";
 import "./chunk-HHJLM3WQ.js";
-import "./chunk-7VEYUF3N.js";
+import "./chunk-W5ZQMAEM.js";
 import "./chunk-74TONY4F.js";
-import "./chunk-E6TI726I.js";
-import "./chunk-4VY3ITHR.js";
-import "./chunk-O2FEO2CB.js";
-import "./chunk-G6UUOCUT.js";
-import "./chunk-IZ2U57NY.js";
-import "./chunk-MWIO7MF6.js";
+import "./chunk-HUXPEUFL.js";
+import "./chunk-TP6FYVQT.js";
 import "./chunk-ZAFYHRVY.js";
-import "./chunk-DAI65CMX.js";
+import "./chunk-TBWQLLFO.js";
+import "./chunk-JYKWOREU.js";
 import {
   writeStdoutLine
 } from "./chunk-7FA2II6K.js";
+import "./chunk-UKMWZ5NS.js";
 import "./chunk-75DOP5OR.js";
 import "./chunk-DMTGGOSA.js";
 import "./chunk-YQ3U5MUC.js";
 import "./chunk-MATEIJZF.js";
-import "./chunk-TBWQLLFO.js";
 import {
   init_esbuild_shims
 } from "./chunk-5O2XNYP6.js";