Skip to content

feat(webview): durable per-view viewStates pipeline (N2, split 2/3 of #1546) - #2227

Open
easonLiangWorldedtech wants to merge 1 commit into
Zoo-Code-Org:mainfrom
easonLiangWorldedtech:vps2/n2-viewstates-durability
Open

easonLiangWorldedtech wants to merge 1 commit into
Zoo-Code-Org:mainfrom
easonLiangWorldedtech:vps2/n2-viewstates-durability

Conversation

@easonLiangWorldedtech

Copy link
Copy Markdown
Contributor

Split unit N2 of #1546 (F1a — durable per-view viewStates pipeline)

Second unit of the split plan recorded in the tracking issue (fork issue 41). Depends on N1 (identity/claim); the buffer/mutation/write-path content is not included.

Scope (contract point)

  • Serialized persistedViewStateWriteQueue, fresh-read merge on save, 50-entry prune, corrupt-value guard.
  • Rekey on registration, clear on reset/delete, and export/import sanitization for viewStates (ContextProxy omit, importExport skip).
  • Typed ProviderSettingsNotFoundError handling used by the identity/adoption path.

Explicitly NOT in this unit

Budget (own delta vs the parent unit)

  • git diff vps2/n1-view-identity..<head>: 326 insertions, 428 deletions (~754 a+d) → under the 1,000 hard cap.
  • Cumulative diff vs 05d01f33d is intentionally larger; measure this unit against its parent, not main.

Evidence

  • ClineProvider.spec.ts + ContextProxy.spec.ts + importExport.spec.ts + ProviderSettingsManager.spec.ts: 362 passed.
  • tsc --noEmit: clean (0 errors).

Stack / merge order

F0 (#1528) → N1 → N2 (this PR) → N3 → F1b (#1550) → F1c (#1552) → F3 (#1560) → F4/F5/F6/F7. Base is main; merge strictly in order.

Refs: #1546, tracking issue 41 (fork).

Split unit N2 of Zoo-Code-Org#1546: viewStates read/write queue, claim rekey, prune, clear, load/save and export/import sanitization on top of N1 identity. Buffer/mutation/history content remains for N3.
@github-actions

Copy link
Copy Markdown
Contributor

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. community-approved is managed the same way — do not add or remove it manually. It signals a fresh community code approval for the current head as an advisory priority only; maintainer review is still required.

@coderabbitai

coderabbitai Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

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

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
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-author PR is waiting for the author to address requested changes has-conflicts PR has merge conflicts with the base branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant