docs: adapt Vite DevTools integration plans to landed foundation

[antfubot]

What & why

The compat/deprecation foundation for the Vite DevTools / devframe integration has already landed — #1021 (server-side devtools:ready hook + nostics-driven deprecations) and #1023 (client-side onDevtoolsReady + exposed client). The plans under plans/vite-devtools-integration/ still described a proposed foundation (connect-safe host accessors on nuxt.devtools, a pre-connect queue, a disableAuthorization hard-break) that was never built. This realigns the remaining plans with reality.

Changes

• Remove 00-compat-foundation.md (implemented) and fold the landed facts into the README: the devtools:ready / onDevtoolsReady((ctx) => …) mechanism that hands you the already-connected context, the shipped nostics catalog and NDT_DEP_* codes, and disableAuthorization now being a supported first-class option (not a hard-break).
• Re-anchor plans 01/02/03 onto onDevtoolsReady, dropping the never-shipped connect-safe hosts and the pre-connect queue/flush machinery.
• 01 (messages): re-point the client toast path onto the client-side onDevtoolsReady / client.devtools.devtoolsKit from feat(devtools): client-side onDevtoolsReady + expose Vite DevTools client; fix client RPC registration #1023.
• 02 (terminals): note that the startSubprocess/getProcess deprecation warnings already ship while the shim still routes through the old @xterm system this plan replaces.
• 03 (dock groups): keep the dock:true convenience flag but flag the tension that addCustomTab is now soft-deprecated toward ctx.docks.register.
• Remove 04-ecosystem-playgrounds.md — handled in feat(playgrounds): add ecosystem dogfooding playground for plan 04 #1022.

Docs-only; no code touched.

This PR was created with the help of an agent.

[coderabbitai]

📝 Walkthrough

Walkthrough

The integration roadmap now treats the compatibility and deprecation foundation as landed and limits the documented workstreams to Messages, Terminals, and dock groups. The Messages and Terminals plans adopt onDevtoolsReady with local buffering before connection. The dock plan adds group registration and connected dynamic entry promotion. Deleted foundation and ecosystem plan documents are not replaced.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the docs update to align Vite DevTools integration plans with the landed foundation.
Description check	✅ Passed	The description accurately describes the documentation-only plan updates and removals in this changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@plans/vite-devtools-integration/README.md`:
- Around line 73-76: Separate readiness-safe context access from domain-event
buffering across all referenced sections: in
plans/vite-devtools-integration/README.md lines 73-76 clarify that only context
access is safe after the ready hook; in
plans/vite-devtools-integration/01-messages-unification.md lines 19-26 remove
absolute “no queue” wording and lines 118-122 describe intentional buffering;
align terminal buffering guidance in
plans/vite-devtools-integration/02-terminals-reuse.md lines 32-35, 139-144, and
225-227; and align dock guidance in
plans/vite-devtools-integration/03-dock-groups-presentation.md lines 23-26 and
234-235, retaining explicit pre-ready buffering for notifications, terminal
events, and custom tabs.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f236de33-3210-4b4a-a727-c2b0de64d735

📥 Commits

Reviewing files that changed from the base of the PR and between 88c4f1c and fd674bd.

📒 Files selected for processing (6)

• plans/vite-devtools-integration/00-compat-foundation.md
• plans/vite-devtools-integration/01-messages-unification.md
• plans/vite-devtools-integration/02-terminals-reuse.md
• plans/vite-devtools-integration/03-dock-groups-presentation.md
• plans/vite-devtools-integration/04-ecosystem-playgrounds.md
• plans/vite-devtools-integration/README.md

💤 Files with no reviewable changes (2)

• plans/vite-devtools-integration/00-compat-foundation.md
• plans/vite-devtools-integration/04-ecosystem-playgrounds.md

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Separate readiness from domain-event buffering.

The ready hook removes the need to guard access to an undefined context, but it does not eliminate buffering when notifications, terminal events, or custom tabs can be emitted before readiness. Rewrite these statements to distinguish “no context-access queue” from the optional local buffering required to preserve early events.

• plans/vite-devtools-integration/README.md#L73-L76: clarify that only context access is readiness-safe.
• plans/vite-devtools-integration/01-messages-unification.md#L19-L26: remove the absolute “no queue” wording.
• plans/vite-devtools-integration/01-messages-unification.md#L118-L122: describe the buffer as intentional domain-event buffering.
• plans/vite-devtools-integration/02-terminals-reuse.md#L32-L35: align the foundation guidance with terminal buffering.
• plans/vite-devtools-integration/02-terminals-reuse.md#L139-L144: preserve the distinction in the implementation steps.
• plans/vite-devtools-integration/02-terminals-reuse.md#L225-L227: keep the risk guidance consistent.
• plans/vite-devtools-integration/03-dock-groups-presentation.md#L23-L26: align the dock guidance.
• plans/vite-devtools-integration/03-dock-groups-presentation.md#L234-L235: retain the explicit pre-ready buffering requirement.

📍 Affects 4 files

• plans/vite-devtools-integration/README.md#L73-L76 (this comment)
• plans/vite-devtools-integration/01-messages-unification.md#L19-L26
• plans/vite-devtools-integration/01-messages-unification.md#L118-L122
• plans/vite-devtools-integration/02-terminals-reuse.md#L32-L35
• plans/vite-devtools-integration/02-terminals-reuse.md#L139-L144
• plans/vite-devtools-integration/02-terminals-reuse.md#L225-L227
• plans/vite-devtools-integration/03-dock-groups-presentation.md#L23-L26
• plans/vite-devtools-integration/03-dock-groups-presentation.md#L234-L235

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@plans/vite-devtools-integration/README.md` around lines 73 - 76, Separate
readiness-safe context access from domain-event buffering across all referenced
sections: in plans/vite-devtools-integration/README.md lines 73-76 clarify that
only context access is safe after the ready hook; in
plans/vite-devtools-integration/01-messages-unification.md lines 19-26 remove
absolute “no queue” wording and lines 118-122 describe intentional buffering;
align terminal buffering guidance in
plans/vite-devtools-integration/02-terminals-reuse.md lines 32-35, 139-144, and
225-227; and align dock guidance in
plans/vite-devtools-integration/03-dock-groups-presentation.md lines 23-26 and
234-235, retaining explicit pre-ready buffering for notifications, terminal
events, and custom tabs.