chore: update

Author: webfansplz

.github/workflows/ci.yml

@@ -16,8 +16,6 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
-        with:
-          submodules: recursive
 
       - name: Install pnpm
         uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093
@@ -55,8 +53,6 @@ jobs:
       fail-fast: false
     steps:
       - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
-        with:
-          submodules: recursive
 
       - name: Install pnpm
         uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093
@@ -82,8 +78,6 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
-        with:
-          submodules: recursive
 
       - name: Install pnpm
         uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093

.github/workflows/src/ci.yml

@@ -17,8 +17,6 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
-        with:
-          submodules: recursive
 
       - name: Install pnpm
         uses: pnpm/action-setup@v4
@@ -54,8 +52,6 @@ jobs:
 
     steps:
       - uses: actions/checkout@v5
-        with:
-          submodules: recursive
 
       - name: Install pnpm
         uses: pnpm/action-setup@v4
@@ -82,8 +78,6 @@ jobs:
 
     steps:
       - uses: actions/checkout@v5
-        with:
-          submodules: recursive
 
       - name: Install pnpm
         uses: pnpm/action-setup@v4

.gitignore

@@ -20,6 +20,7 @@ packages/kit/skills
 **/.vitepress/cache
 .turbo
 .context
+.ghfs
 
 # Agent skills from npm packages (managed by skills-npm)
 **/skills/npm-*

.gitmodules

@@ -4,7 +4,7 @@
 
 Two layers, one mental model:
 
-- **`devframe`** — *the container for one devtool integration, portable across viewers.* External project; lives at [`github.com/devframes/devframe`](https://github.com/devframes/devframe), docs at [`devfra.me`](https://devfra.me). Consumed here as an npm dependency (`catalog:deps`). A checked-in submodule at `devframe/` mirrors the source at the pinned tag for browsing and upstream contributions.
+- **`devframe`** — *the container for one devtool integration, portable across viewers.* External project; lives at [`github.com/devframes/devframe`](https://github.com/devframes/devframe), docs at [`devfra.me`](https://devfra.me). Consumed here as an npm dependency (`catalog:deps`).
 - **`@vitejs/devtools-kit`** — *the hub that unites many devtools integrations.* Owns docking, the command palette, toasts, terminal sessions — anything that only makes sense when more than one tool shares a UI. Provides `createPluginFromDevframe(devframeApp)` so a portable devframe definition drops into Vite DevTools as a Vite plugin, with the dock entry auto-derived from the definition's metadata.
 
 When deciding where something belongs: if a single-app standalone CLI would still need it, it belongs upstream in devframe; if it only matters once you have multiple integrations or a host UI, it lives in the kit.
@@ -28,8 +28,6 @@ Monorepo (`pnpm` workspaces + `turbo`). ESM TypeScript; bundled with `tsdown`. P
 Other top-level directories:
 - `docs/` — VitePress docs; guides in `docs/guide/`
 - `skills/` — Agent skill files generated from docs via [Agent Skills](https://agentskills.io/home). Structured references (RPC patterns, dock types, shared state, project structure) for AI agent context.
-- `devframe/` — Git submodule pinned to the `devframe` version in `catalogs.deps`. Run `pnpm sync` to align with the catalog; `pnpm sync <version>` or `pnpm sync --latest` to bump.
-- `scripts/sync.ts` — Submodule pin manager (see `pnpm sync --help`).
 
 ```mermaid
 flowchart TD
@@ -125,11 +123,13 @@ Codes are sequential 4-digit numbers per prefix (e.g. `DTK0033`, `RDDT0003`). Ch
    import { diagnostics } from './diagnostics'
 
    // For thrown errors — always prefix with `throw` for TypeScript control flow:
-   throw diagnostics.DTK0033.throw({ name })
+   throw diagnostics.DTK0033({ name })
 
-   // For reported (non-thrown) diagnostics:
-   diagnostics.DTK0033.report({ name })
-   diagnostics.DTK0033.report({ name, cause: error }) // attach cause via params
+   // For reported (non-thrown) diagnostics. The default console method is `warn`;
+   // override with the 2nd-arg reporter options when needed:
+   diagnostics.DTK0033({ name }) // console.warn
+   diagnostics.DTK0033({ name }, { method: 'error' }) // console.error
+   diagnostics.DTK0033({ name, cause: error }) // attach cause via params
    ```
 
 3. **Create a docs page** at `docs/errors/DTK0033.md`:

AGENTS.md

@@ -50,3 +50,20 @@ These types are no longer re-exported from `@vitejs/devtools-kit`. Import them f
 ```
 
 The `@vitejs/devtools-kit/utils/when` subpath remains and re-exports these types alongside `evaluateWhen` and `resolveContextValue`.
+
+#### Diagnostic handles are callable
+
+`nostics` 0.2 (pulled in via devframe 0.4) drops the `.report()` / `.throw()` methods on diagnostic handles. Each handle is now a callable that builds and emits a diagnostic; prefix with `throw` to raise.
+
+```diff
+- throw ctx.diagnostics.logger.MYP0001.throw({ name })
++ throw ctx.diagnostics.logger.MYP0001({ name })
+
+- ctx.diagnostics.logger.MYP0002.report()
++ ctx.diagnostics.logger.MYP0002()
+
+- ctx.diagnostics.logger.MYP0002.report({ name }, { method: 'error' })
++ ctx.diagnostics.logger.MYP0002({ name }, { method: 'error' })
+```
+
+The payload shape (including `cause`) and the optional reporter-options second argument are unchanged. Apply the same rewrite to typed handles returned from `ctx.diagnostics.defineDiagnostics()`.

MIGRATION.md

@@ -61,7 +61,6 @@ export default extendConfig(withMermaid(defineConfig({
     'packages/**',
     'examples/**',
     'tests/**',
-    'devframe/**',
     'docs/.vitepress/**',
     '.github/**',
     '.context/**',

docs/.vitepress/config.ts

@@ -13,7 +13,8 @@
 interface DevToolsDiagnosticsHost {
   /**
    * Proxy-backed lookup of every registered code by name. Each entry is a
-   * `nostics` handle with `.report()` and `.throw()` methods.
+   * `nostics` `DiagnosticHandle` — a callable that builds a diagnostic and
+   * routes it through registered reporters; prefix with `throw` to raise.
    */
   readonly logger: Record<string, any>
 
@@ -56,7 +57,7 @@ export function MyPlugin(): PluginWithDevTools {
         ctx.diagnostics.register(diagnostics)
 
         // Emit codes through the shared lookup:
-        ctx.diagnostics.logger.MYP0002.report()
+        ctx.diagnostics.logger.MYP0002()
       },
     },
   }
@@ -80,23 +81,26 @@ Each definition supports `why` (string or function returning a string) and an op
 
 ## Emit a diagnostic
 
-Each registered code is reachable as a property on `ctx.diagnostics.logger`. Every handle exposes `.throw(params)` and `.report(params)`.
+Each registered code is reachable as a property on `ctx.diagnostics.logger`. Every handle is a callable — invoke it to report (returns the `Diagnostic`), or prefix with `throw` to raise.
 
 ```ts
 // Throw — control flow stops here
-throw ctx.diagnostics.logger.MYP0001.throw({ name: 'foo' })
+throw ctx.diagnostics.logger.MYP0001({ name: 'foo' })
 
-// Report without throwing (goes through the host's reporter)
-ctx.diagnostics.logger.MYP0002.report()
+// Report without throwing (default console method: `warn`)
+ctx.diagnostics.logger.MYP0002()
+
+// Override the console method per call
+ctx.diagnostics.logger.MYP0002({}, { method: 'error' })
 
 // Attach a `cause` via the params object
-ctx.diagnostics.logger.MYP0001.report({ name: 'foo', cause: error })
+ctx.diagnostics.logger.MYP0001({ name: 'foo', cause: error })
 ```
 
-`.throw()` is typed `never`. Prefix the call with `throw` so TypeScript narrows control flow correctly:
+The callable returns a `Diagnostic` (which extends `Error`). Prefix with `throw` so TypeScript narrows the lines after as unreachable:
 
 ```ts
-throw ctx.diagnostics.logger.MYP0001.throw({ name })
+throw ctx.diagnostics.logger.MYP0001({ name })
 ```
 
 ## Typed handle reference
@@ -115,7 +119,7 @@ const myDiagnostics = ctx.diagnostics.defineDiagnostics({
 ctx.diagnostics.register(myDiagnostics)
 
 // Use the typed handle directly at emit sites
-myDiagnostics.MYP0001.report({ name: 'foo' })
+myDiagnostics.MYP0001({ name: 'foo' })
 ```
 
 Both paths share the formatter and reporter defaults set by the host (ANSI console output).
@@ -135,7 +139,7 @@ Each page covers the message, cause, example, and fix; see any [DTK code page](/
 
 ## When to use what
 
-- **`ctx.diagnostics`** — coded conditions worth looking up: misconfiguration, deprecations, validation failures, internal invariants. Always docs-backed. Often `.throw()`.
+- **`ctx.diagnostics`** — coded conditions worth looking up: misconfiguration, deprecations, validation failures, internal invariants. Always docs-backed. Often `throw`-prefixed.
 - **[`ctx.messages`](./messages)** — user-facing activity surfaces in the DevTools UI: progress indicators, audit results, "URL copied" toasts. Just a message and a level.
 
 Diagnostics target tool authors and CI; messages target the human in front of the DevTools panel.

docs/kit/diagnostics.md

@@ -1,7 +1,7 @@
 {
   "name": "@vitejs/devtools-e2e",
   "type": "module",
-  "version": "0.1.24",
+  "version": "0.2.0",
   "private": true,
   "scripts": {
     "test": "vitest --run"

e2e/package.json

@@ -1,7 +1,7 @@
 {
   "name": "example-plugin-a11y-checker",
   "type": "module",
-  "version": "0.1.24",
+  "version": "0.2.0",
   "private": true,
   "exports": {
     ".": "./dist/index.mjs",