fix(webview): isolate parallel mode and provider profile writes (vps2 F3) by easonLiangWorldedtech · Pull Request #1560 · Zoo-Code-Org/Zoo-Code

easonLiangWorldedtech · 2026-09-07T02:38:30Z

Draft PR — vps2 unit F3 (mode/profile writes).

Tracking: easonLiangWorldedtech#41 (vps2 series ledger). Upstream issue: #1559 (this series' gap record; the original upstream bug is #978). Port source: the F1c-head-to-CS residual, cross-checked against upstream PR #979 (fix(webview): isolate parallel mode and provider profile writes) — closed/superseded by the vps2 series; the #41 ledger names #979 as the F3 port source.

Scope

10 files, 919 insertions, 65 deletions (measured vs stack base aa0f3b1):

src/core/webview/ClineProvider.ts (112/6) — the webview delete-path (deleteProviderProfile + repointPersistedViewStates), loadViewState dead-mode-pin validation, the handleModeSwitch profile-write isolation (per-view upsert/activate instead of the shared write), the as-any cast drop in delegateParentAndOpenChild, and a 3-line Stryker exclusion comment (next-line CallExpression,ObjectLiteral directive) above the no-op listApiConfigMeta view-state write (two equivalent mutants; see the Mutation gate trust note).
src/core/task/Task.ts (16/2) + Task.spec.ts (40/2) — the task-side per-view mode/profile write: mode switches route through provider.handleModeSwitch and the submitted message is kept on failure.
src/core/tools/SwitchModeTool.ts (7/4) + switchModeTool.spec.ts (22/14) — the tool-side per-view write port.
src/core/webview/webviewMessageHandler.spec.ts (5/0) — ported mock surface only: fix(webview): isolate parallel mode and provider profile writes #979's 4 mock fields (captureCustomModeCreated, captureModeSettingChanged, updateCustomMode, handleModeSwitch) plus the defaultModeSlug import. webviewMessageHandler.ts itself is 0/0 — see Port fidelity.
src/core/webview/tests/ClineProvider.sticky-mode.spec.ts (72/31) — the sticky-mode spec rewrites (concurrent-switch assertions re-targeted from the shared mode key to the per-view viewStates key).
src/core/webview/tests/ClineProvider.spec.ts (20/4) — exactly the two handleModeSwitch assertion-rewrite hunks (L3328, L3362 vs base).
src/core/webview/tests/ClineProvider.parallelMode.spec.ts (623/0) — 3 import lines + a 620-line append to the file created by F2: the CS F3 describes (310 lines, byte-identical to CS L1364-1673), 116 lines of F3-authored mutation-killing tests (corrupt-entry repoint skip, legacy-pin repoint, unknown-mode-slug no-op, released-provider switch tool path, ModeChanged event emission, empty-profile no-op), and a 194-line append of 5 further mutation-killing tests (no-task switch race, non-focused profile-load skip, upsert-without-activation list refresh, and the two deleteProviderProfile pin-behavior tests).
src/eslint-suppressions.json (2/2) — no-explicit-any counts decrease for core/webview/ClineProvider.ts (12 to 11) and core/webview/tests/ClineProvider.sticky-mode.spec.ts (36 to 33); no count increases.

Budget

a+d 984 vs the 400-soft / 1000-hard budget: soft-over, hard-under. The unit carries the production isolation logic (CP 112/6, Task 16/2, SwitchModeTool 7/4), three spec rewrites (sticky 72/31, CP.spec 20/4, switchModeTool.spec 22/14), and the 623-line parallelMode append. The 310 authored test lines (116 + 194) are gate-mandated: the Stryker diff gate cannot be satisfied by the CS-residual tests alone (several CP conditional/object-literal/string-literal mutants and one NoCoverage have no CS-side killer), and the skill rule is to kill by spec, never suppress. The only non-test production addition is the 3-line Stryker exclusion comment (equivalent mutants, documented in the Mutation gate trust note).
Stryker-diff gate (vs aa0f3b1, final head 8da5c6e): 63 mutants generated on the 78 changed executable lines — 61 killed, 2 ignored (the excluded equivalent pair at the listApiConfigMeta view-state write), 0 survived, 0 uncovered; gate exit 0.
vitest: 475/475 passed (138 suites, 16 spec files) — per file: ClineProvider.spec 206, Task.spec 101, ClineProvider.parallelMode 24, Task.persistence 24, ClineProvider.sticky-mode 19, Task.throttle 19, ClineProvider.taskHistory 18, ClineProvider.apiHandlerRebuild 15, ClineProvider.sticky-profile 15, ClineProvider.flicker-free-cancel 10, Task.pending-action 9, Task.dispose 7, ClineProvider.pending-action 4, ClineProvider.lockApiConfig 2, Task.resume-eviction-race 1, Task.sticky-profile-race 1.
check-types, eslint (--prune-suppressions, max-warnings 0; suppression counts flat-or-down), prettier (--end-of-line=auto): all pass — check-types exit 0; eslint exit 0 on the touched files (suppression file unchanged from the stack base: no-explicit-any counts down on the two listed files, flat-or-down invariant holds); prettier --end-of-line=auto clean.

Mutation gate trust note

Gate of record: the final sandbox-mode run at head 8da5c6e (vs stack base aa0f3b1; 78 changed executable lines; the 16-file direct test set): 63 mutants generated — 61 killed, 2 ignored, 0 survived, 0 uncovered; gate exit 0.
The 2 ignored mutants are the excluded pair at the createNewApiConfiguration else-branch call this._updateViewLocalStateFromMutation({ listApiConfigMeta }) at L2238: the CallExpression mutant (statement deleted) and the ObjectLiteral mutant (object emptied). Both are true equivalent mutants: the method (byte-identical to the CS method) applies only mode, currentApiConfigName, apiConfiguration and provider-settings keys, and a listApiConfigMeta-only payload matches none of them, so the deleted-statement and empty-object forms are behaviorally indistinguishable from the original. The exclusion is the narrowest mutator-specific directive the gate accepts (next-line, two named mutators, concrete reason committed at the call site); broad exclusions are rejected by the gate.
Four mutants that surfaced as Survived in earlier sandbox-mode runs on this machine — L2053 ConditionalExpression, L2072 ConditionalExpression, L2275 ConditionalExpression and L2283 ObjectLiteral — are all killed in the final run. The earlier survivors were an environment artifact (sandbox-mode per-mutant verification of ClineProvider.ts running against an un-mutated file copy in this worktree setup, while the Task.ts and SwitchModeTool.ts mutants verified and killed correctly in the same runs); the artifact was reproduced and isolated in a detached probe worktree. Killability of record is the plain-vitest true-form matrix over the committed 16-file suite (475 tests): warm baseline 475/475; L2053 true form 1 failure (the no-task switch-race test); L2072 true form 1 failure (the non-focused profile-load skip test); the L2234 string-literal form 1 failure (the upsert-without-activation list-refresh test); the L2238 excluded forms 0 failures (equivalent); L2275 true form 3 failures (the committed replacement-profile sync test plus both deleteProviderProfile pin-behavior tests); L2283 form 2 failures (both pin tests); no test fails under any mutant other than its designed killer(s).
In-place run (STRYKER_IN_PLACE=true, same selectors and test set): not run — the canonical sandbox-mode gate passed at the final head, so a separate in-place run adds no evidence.

Port fidelity (coordinator-verified against the vps2 CS `e9a44b2`)

The F3 residual (CS vs F1c head, per file) was ported hunk-by-hunk; no whole-file copies.
webviewMessageHandler.ts is 0/0 vs base. The residual's kimi-code OAuth try/catch hunk is CS-only divergence (it is absent from upstream fix(webview): isolate parallel mode and provider profile writes #979, whose WMH.ts carries only the two F1c-shipped hunks) — CS not-ported register item 1, deliberately not ported. webviewMessageHandler.spec.ts carries only fix(webview): isolate parallel mode and provider profile writes #979's mock-field additions (5/0); the stack-side legacy-repair test, the Key-aware getValue mock, and the em-dash comment are retained from the F2 base (register item 4). fix(webview): isolate parallel mode and provider profile writes #979's mode-routing WMH.spec describe ("routes mode messages through handleModeSwitch instead of writing ContextProxy directly") exists in neither the CS nor the stack and is ported by no unit of this series — logged as a parked open question, not a gap of this PR.
ClineProvider.ts setViewStateId proto guard: the residual removes the guard (CS lineage); this PR retains the guard exactly as shipped by F1a, so the guard region is byte-identical to the F2 head (no diff hunk there). Rationale: without the guard, states["proto"] invokes the Object.prototype setter and the durable write for that view is silently dropped; no F3 spec depends on the unguarded behavior. Cross-check: upstream fix(webview): isolate parallel mode and provider profile writes #979's setViewStateId body also has no guard, confirming the guard is stack-side (F1a) hardening, not fix(webview): isolate parallel mode and provider profile writes #979/CS content.
ClineProvider.spec.ts: exactly the two handleModeSwitch assertion-rewrite hunks ported (each re-targets the shared-key assertion to the per-view viewStates objectContaining form, with the view pinned via setViewStateId); the F2-head describe("setViewStateId") guard test block is retained byte-identical (invisible in the diff). The remaining CS residual on this file is the deliberate F1-series describe restructure — excluded, not F3 content.
ClineProvider.sticky-mode.spec.ts: all 4 CS hunks present at the F3 head (including the concurrent-switch filter rewrite from the shared mode key to the per-view viewStates key) — verified byte-identical to the CS residual by the coordinator.
ClineProvider.parallelMode.spec.ts: the 310-line CS F3 describe region (CS L1364-1673) is present byte-identical in order at the F3 head; the 116 authored lines are targeted mutation killers, added in 3 blocks inside the CS describes; CS L1674 (the blank separator before the F4 describes) is not ported — F4 appends its own block.
The defaultModeSlug import (CS register item 5) lands in this unit via the webviewMessageHandler.spec.ts mock surface (F1c had dropped it as unused).

Structural note on the parallelMode spec (coordinator-verified)

The CS parallelMode.spec.ts is 1790 lines: a shared preamble (L1-672), an F1-series test section (L673-1363: viewId uniqueness, local state isolation, saveViewState, stale temporary-id load), the F3 describes (L1364-1673), a blank separator (L1674), and the F4 multi-instance describes (L1675-1790). In this series the F1-series section lives in ClineProvider.spec.ts (shipped by F1a/F1b/F1c — the deliberate F1-series describe restructure), and the F2 unit shipped the persisted-pruning and #1065 retention tests inside the parallelMode file (they are absent from the CS parallelMode file). Both placements are behaviorally covered; the divergence is structural, not a coverage gap.

Series mechanics

Base of record: upstream/main @ 0d937c0; PR base is main; the branch is stacked on the F2 head aa0f3b1 (the F1-series and F2 heads are merged below it in the series merge order).
Draft PR per unit; merge order F1a to F1b to F1c to F2 to F3 to F4 to F5 to F6 to F7.
CS not-ported register (for consistency): (1) kimi-code OAuth try/catch + routerModels.spec.ts +29 — also the reason WMH.ts is 0/0 here; (2) ApiConfigManager.tsx min-w-0 shrink to grow; (3) ApiConfigManager.visual.tsx deletion + 2 PNG baselines; (4) mojibake comment; (5) unused defaultModeSlug import — resolved by this unit; (6) providers/, .coderabbit.yaml, .github/, CONTRIBUTING.md, .gitignore churn.
Merge check against upstream main 4c7474d (merge-base = base of record 0d937c0), via git merge-tree on the full F0-to-F3 stack: nine files auto-merge, including the four files changed on both sides (Task.ts, Task.spec.ts, ClineProvider.ts, ClineProvider.spec.ts). The single content conflict is src/eslint-suppressions.json: upstream main independently decreased six no-explicit-any counts (including core/webview/ClineProvider.ts 12 to 8 and core/task/Task.ts 19 to 17) while this PR decreases two (core/webview/ClineProvider.ts 12 to 11 and the sticky-mode spec 36 to 33, vs stack base). The one overlapping entry is core/webview/ClineProvider.ts; resolution is mechanical: regenerate that entry from the post-merge file with eslint --prune-suppressions (per the AGENTS.md invariant the count can never increase; the post-merge count is flat-or-down vs upstream 8). Every other file entry touched by either side is disjoint.

coderabbitai · 2026-09-07T02:38:38Z

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

coderabbit-review-active

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: b02cf3ca-eab0-4b48-9d1b-ad1331f37929

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

github-actions · 2026-09-07T05:22:28Z

Review status

Thanks for contributing. This comment tracks the review sequence and the next action.

Current step: Resolve the merge conflicts. The review sequence resumes after the branch is mergeable.

Review-state labels are managed by this workflow; do not edit them manually.

codecov · 2026-09-07T06:49:35Z

Codecov Report

❌ Patch coverage is 92.54808% with 31 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/core/webview/ClineProvider.ts	91.00%	17 Missing and 10 partials ⚠️
webview-ui/src/utils/vscode.ts	93.10%	1 Missing and 1 partial ⚠️
src/activate/registerCommands.ts	98.21%	0 Missing and 1 partial ⚠️
src/core/webview/webviewMessageHandler.ts	93.33%	0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

…en view-identity tests Track the in-flight tab panel creation with a module-level promise so concurrent openClineInNewTab calls reuse one panel and provider (adds a Promise.all regression test). ClineProvider.spec sets the private view via the public resolveWebviewView() instead of a ts-ignore assignment. registerCommands.spec types evictCurrentTask/refreshWorkspace on the fixture and drops the as any attachment. eslint-suppressions: prune the registerCommands.spec.ts entry (two as any suppressions removed).

…n the concurrency assertion

…-bar posts - openClineInNewTab: extract the unserialized creation body into createTabPanelUnlocked and guard the in-flight slot clear so a settled creation cannot clobber a replacement already stored in the slot. - onDidDispose: clear the tracked tab ref only when the disposing panel is still the tracked one, so a late disposal of a replaced panel cannot clobber the replacement's ref. - MDM lookup failure: log the fallback to the output channel instead of swallowing it silently. - Route the six title-bar button handlers through a shared postActions helper that posts each action in order and logs failures with the handler-specific prefix. - package.json: add the four InTab commands to the command palette, scoped to the active tab panel. - Tests: handler-level regression for openInNewTab + popoutButtonClicked started before the first creation resolves; fresh-creation test for a settled in-flight promise; stale-panel disposal regression; retained panel assertion for disposed tab instances; rightmost-editor column placement assertion; MDM fallback output assertion; %s placeholders for primitive it.each titles. - Stryker directives for the two equivalent setPanel type-literal mutants (setPanel branches only on type === sidebar).

Replace the weak toBeDefined() assertion in the dispose spec with an identity check against the panel returned during creation, per the CodeRabbit actionable comment on this PR (review run 7c4cfeb3-6dd9-4615- 9a58-70cfc705eca2). The tracked tab is now pinned with toBe(panel) before the dispose assertions, so a wrong or duplicated tracked panel fails the suite instead of passing a defined-only check. Upstream: Zoo-Code-Org#1528 (vps2 F0)

Retain the tracked tab panel in the InTab handler cases and assert that getInstanceForView was called with that exact panel, per the CodeRabbit actionable comment on this PR (review run 4afe1273-8739-4235-90d3-311db5f6ccb9, inline comment 3952466254 on the tabHandlerCases spec). A handler resolving any other view now fails instead of passing on the stubbed provider result alone; the same identity pin is applied to plusButtonClickedInTab. Upstream: Zoo-Code-Org#1528 (vps2 F0)

…States Each ClineProvider instance now owns a unique viewId (renderContext plus a monotonic counter) and registers a stable viewStateId for durable persistence. - Per-view state buffer (viewLocalState) holds mode / currentApiConfigName / apiConfiguration overrides in memory; saveViewState persists the non-secret subset durably under the active view id, rekeyed to the stable id on registration. - viewStates is stored as a map pruned to the newest 50 entries; writes go through a serialized queue so concurrent provider instances merge without lost updates. - setViewStateId sanitizes ids and rejects "__proto__" so a per-view entry can never be keyed through the Object.prototype setter. - postMessageToWebview no longer awaits the webview ack: a remounted or disposed page never acknowledges, and awaiting would wedge task-critical callers. - History restore falls back to the default mode view-locally instead of writing the shared global mode. - GlobalState gains the "viewStates" key and GLOBAL_STATE_KEYS tracks it. Adds F1a coverage in ClineProvider.spec.ts (viewId uniqueness, saveViewState persistence semantics, loadViewState fallback and failure, pruning, the __proto__ guard) and adapts the two history-restore tests in ClineProvider.sticky-mode.spec.ts to the view-local restore. getState() merging of hydrated per-view values and the remaining view-state suites land in the follow-up (F1b).

…lude viewStates from settings transfer

…stence fails

… describe by subject Tie-case pruning and editor-teardown retention now assert the full survivor objects instead of mere presence, and the durable viewStates persistence tests move out of the getState merging block into a persisted view state describe so each block name matches its subject.

Port vps2 F3 (mode/profile writes) from upstream 978, hunk-by-hunk against the F1c..CS residual: - ClineProvider: add repointPersistedViewStates() to re-point currentApiConfigName across per-view entries when a profile is renamed or replaced, and prune orphaned entries; validate handleModeSwitch slugs against the custom-modes manager and no-op with a log on unknown modes; drop the as-any cast in delegateParentAndOpenChild. - Task: route mode switches through provider.handleModeSwitch(task) and keep the submitted message on failure instead of setMode(). - SwitchModeTool and specs: durable per-view mode writes. - webviewMessageHandler: no change vs base - the kimi-code OAuth hunk in the residual is CS-only divergence (not-ported register item 1), not part of Zoo-Code-Org#978/Zoo-Code-Org#979. - webviewMessageHandler.spec: ported only Zoo-Code-Org#979's 4 mock fields + defaultModeSlug import; the stack-side legacy-repair test, Key-aware getValue mock and em-dash comment are retained (register item 4). Zoo-Code-Org#979's mode-routing WMH.spec describe ("routes mode messages through handleModeSwitch instead of writing ContextProxy directly") exists in neither CS nor the stack and is ported by no unit (open question, logged). - Tests: H3/H4 durable handleModeSwitch writes in ClineProvider.spec.ts; profile-mutation, profile-activation and handleModeSwitch-integration describes (incl. A4 non-focused-target regression and new mutation-killing tests) in ClineProvider.parallelMode.spec.ts; sticky-mode and webviewMessageHandler spec updates; retain the setViewStateId __proto__ guard + spec test - shipped F1a hardening; the residual's guard removal is lineage divergence, not F3 content. - eslint-suppressions.json: no-explicit-any counts decrease for core/webview/ClineProvider.ts (12 -> 11) and core/webview/__tests__/ClineProvider.sticky-mode.spec.ts (36 -> 33). Upstream: Zoo-Code-Org#978 (vps2 F3) - issue Zoo-Code-Org#978; content ported hunk-by-hunk from the F1c..CS residual, cross-checked against upstream PR

Route the CS API setConfiguration write through ClineProvider.setValues instead of the raw context proxy so the view-local subset stays in sync with the sidebar view's state. A direct context-proxy write leaves the view-local apiConfiguration stale; the mode-switch / profile-activation paths re-apply the current provider settings to the focused task on every user message, so a task started after an API setConfiguration runs with the stale configuration (wrong model / reasoning flags / endpoint). That is the deterministic 13-test e2e provider-suite failure (72/13) on this head: the provider suites configure the provider via setConfiguration and the mock serves fixtures by the model the request actually carries. Ported from the F5 head (vps2 F5) where the e2e provider suites pass; includes the unit spec asserting the routing. Upstream: Zoo-Code-Org#982 (vps2 F3)

… mocks API.setConfiguration now routes through ClineProvider.setValues (8576b18 "fix(api): route setConfiguration through ClineProvider.setValues"), but the pre-existing spec still shaped the provider mock around the old contextProxy.setValues call. Both tests in this file failed with "this.sidebarProvider.setValues is not a function" on the platform-unit-test runs (F3 Zoo-Code-Org#1560 windows unit, job 101863508169, run 34161293841). Add the provider-level setValues mock to both tests to match the new routing. Upstream: Zoo-Code-Org#1560 (vps2 F3)

The F1a buffer routing and the new delete-time activation branch interacted in two ways: the unrelated-pin branch re-wrote currentApiConfigName through setValue although the view-local buffer already holds the surviving pin (drop the write: it only triggered a viewStates prune pass and could clobber the pin with the shared slot value), and deleting the current profile now activates the fallback, which reads its settings via providerSettingsManager, so the spec test uses a test double like its siblings in the describe.

…tion mutations - E1: move the provider-release switch test into switchModeTool.spec where the switchModeTool layer is the narrowest proof - E2: assert the state postMessage shape in the mode-lock switch test - E3: prune invalid persisted view-state entries before applying the cap - wrap the upsert and activate buffer-refresh calls so the view-local apiConfiguration buffer tracks the activated profile again; flat provider-settings keys no longer merge into the buffer

This was referenced Sep 7, 2026

[BUG] Isolate parallel mode and provider profile writes (vps2 F3; upstream #978) #1559

Open

VPS2 durable per-view state - independent-fix series (supersedes #34 + the 21-item upstream draft series) easonLiangWorldedtech/Zoo-Code#41

Open

github-actions Bot added the has-conflicts PR has merge conflicts with the base branch label Sep 7, 2026

easonLiangWorldedtech force-pushed the vps2/f3-mode-profile-writes branch from 8da5c6e to 7d91ff4 Compare September 7, 2026 06:11

github-actions Bot removed the has-conflicts PR has merge conflicts with the base branch label Sep 7, 2026

easonLiangWorldedtech mentioned this pull request Sep 7, 2026

[Tracking] 未合併 Upstream PRs（未追蹤） easonLiangWorldedtech/Zoo-Code#62

Open

easonLiangWorldedtech force-pushed the vps2/f3-mode-profile-writes branch from 39423f2 to 510689f Compare September 7, 2026 13:10

easonLiangWorldedtech marked this pull request as ready for review September 7, 2026 13:53

easonLiangWorldedtech requested review from JamesRobert20, edelauna, hannesrudolph, navedmerchant and taltas as code owners September 7, 2026 13:53

easonLiangWorldedtech force-pushed the vps2/f3-mode-profile-writes branch from 510689f to 7f69ecf Compare September 7, 2026 18:12

easonliang28 added 5 commits September 8, 2026 02:34

fix(activate): target title-bar commands to their click-origin instance

3396c9e

ci: re-trigger PR review-state labeler reconciliation (no-op commit)

a143267

test(activate): pin openClineInNewTab creation branches and strengthe…

c3027c8

…n the concurrency assertion

easonLiangWorldedtech force-pushed the vps2/f3-mode-profile-writes branch from 7f69ecf to f9233a4 Compare September 7, 2026 19:22

easonLiangWorldedtech force-pushed the vps2/f3-mode-profile-writes branch from cac941f to 210899f Compare September 7, 2026 20:24

easonliang28 added 4 commits September 8, 2026 04:51

fix(provider): track in-flight view-state mutations per field and exc…

8c13975

…lude viewStates from settings transfer

fix(provider): restore previous view-state id when registration persi…

dc2e9cd

…stence fails

easonLiangWorldedtech force-pushed the vps2/f3-mode-profile-writes branch from 210899f to 8576b18 Compare September 7, 2026 20:56

easonliang28 added 6 commits September 8, 2026 11:53

easonLiangWorldedtech force-pushed the vps2/f3-mode-profile-writes branch from b80d59a to 065116c Compare September 8, 2026 06:04

Navigation Menu

Uh oh!

fix(webview): isolate parallel mode and provider profile writes (vps2 F3) - #1560

fix(webview): isolate parallel mode and provider profile writes (vps2 F3)#1560
easonLiangWorldedtech wants to merge 30 commits into
Zoo-Code-Org:mainfrom
easonLiangWorldedtech:vps2/f3-mode-profile-writes

easonLiangWorldedtech commented Sep 7, 2026

Uh oh!

coderabbitai Bot commented Sep 7, 2026 •

edited

Loading

Review skipped

Uh oh!

github-actions Bot commented Sep 7, 2026 •

edited

Loading

Uh oh!

codecov Bot commented Sep 7, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

easonLiangWorldedtech commented Sep 7, 2026

Scope

Budget

Mutation gate trust note

Port fidelity (coordinator-verified against the vps2 CS e9a44b2)

Structural note on the parallelMode spec (coordinator-verified)

Series mechanics

Uh oh!

coderabbitai Bot commented Sep 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

github-actions Bot commented Sep 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review status

Uh oh!

codecov Bot commented Sep 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Port fidelity (coordinator-verified against the vps2 CS `e9a44b2`)

coderabbitai Bot commented Sep 7, 2026 •

edited

Loading

github-actions Bot commented Sep 7, 2026 •

edited

Loading

codecov Bot commented Sep 7, 2026 •

edited

Loading