Skip to content

feat(appkit): add dev-only design pages plugin and ui-only template - #680

Open
MarioCadenas wants to merge 75 commits into
work/2-appkit-plugin-add-with-auth-mofrom
work/1-design-plugin-dev-only-design-
Open

MarioCadenas wants to merge 75 commits into
work/2-appkit-plugin-add-with-auth-mofrom
work/1-design-plugin-dev-only-design-

Conversation

@MarioCadenas

@MarioCadenas MarioCadenas commented Oct 20, 2026 •

Copy link
Copy Markdown
Collaborator

Stacked on #679 (KIT-2). Merge #679 first; this PR's base will then move to main.

Adds a dev-only design() plugin (beta) for building an app's UI as design pages before it's wired to data, and an empty ui-only app template (server + design) for quick PoCs. This is the single design-plugin PR: it includes the TSX drafts work from #707 and #708 (KIT-38, KIT-40), which this replaces. HTML drafts are not part of it (the decision is TSX streaming only).

What it does

  • /design and /design/<name> render client/src/design/index.tsx and client/src/design/pages/<name>.tsx at full size, with the app's styles and hot reload. Other paths under /design return 404, and the plugin answers 404 in production.

    • With react-router 7 (the template ships it), pages share a router with basename /design. Each page is imported on its own, so an unfinished page breaks only its own URL.
  • TSX drafts, streamed while they're written.

    • A builder appends a draft's source to client/src/design/.staging/<name>.tsx (and the shared mock's to .staging/mock.ts), then writes the finished, type-checked file to pages/<name>.tsx.
    • /design/__stream/<name> shows the draft while it streams. The dev server keeps the latest renderable version of the staging file under the page's real module: closeOpen closes whatever is open at the cut (JSX, brackets, template literals), and components not written yet are stubbed.
    • Each version arrives as a hot update, so the page fills in in place.
    • Stubbed components show a DraftPlaceholder skeleton.
  • DesignPage (@databricks/appkit-ui/react/beta): every design page renders through it. It applies the app's theme before the first paint (dark included, ?theme= override). Its error boundary keeps the last good frame on screen instead of a broken one.

  • Readiness, for any kind of app, from a hidden preview. GET /design/__status reports:

    • ready, compiled (server-side import-graph build, no browser) and waitingFor;
    • for each design page, pages[]: compiled, rendered, errors and state;
    • for the app's own pages, app: entry, compiled, path, rendered, template and errors.

    Errors cover render errors, uncaught errors, unhandled rejections and Vite errors, with their messages. They are null until a browser has loaded the page, and a hot update clears what it fixed. Nothing waits for a visible or painted frame (two frames, or 100 ms without them).
    Pages post appkit:design-ready and the app's pages appkit:app-ready to the configured builderOrigin. That's a bare origin, never "*"; it defaults to the APPKIT_DESIGN_BUILDER_ORIGIN environment variable, so a scaffolded design() needs no options.

  • useDesignReady(false) holds readiness back for content the page can't detect on its own.

  • Charts (appkit-ui) fill their container's height by default (at least 160px), or take an exact height.

  • Template: the ui-only entry (feature design), a placeholder client/src/design/index.tsx, and the .appkit/ gitignore.

  • Plugin hook: plugins can add Vite plugins to the dev server through an optional vitePlugins() method.

  • Selection is out of scope here (the human's decision): no element picker or .appkit/design-selection.json. App Builder's own inspector selects elements through the dev server's data-source="file:line:col" attributes.

How I checked it

  • Tests: unit and real-Vite tests for page resolution and routing, the status endpoint (per page and app, hidden-frame reports, hot-update resets, CORS), compile errors anywhere in the import graph, the react-router check behind Vite's pre-bundle, closeOpen and renderablePartial, the staging watcher, DesignPage, and chart sizing.
  • Live in Chrome:
    • In display: none iframes, /design pages and the app reported rendered and their errors.
    • A fix in an imported component cleared its error through a hot update.
    • Lines written to .staging/<name>.tsx showed up in the page as they were written.
  • Commands: pnpm build, pnpm docs:build, pnpm -r typecheck, pnpm check, knip and pnpm test (324 files) pass.

Not done

  • ui-only wasn't generated with databricks apps init (needs the CLI and network); only the template files changed.

Task: KIT-1 (app-kit/1)

This pull request and its description were written by Isaac.

@github-actions

github-actions Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

📦 Bundle size report

Compared against bundle-size-baseline.json (main).

@databricks/appkit

npm tarball (packed): 1.3 MB (+38 KB) — gzipped download (dist + bin; excludes release-only docs/NOTICE).

dist raw gzip
JS (runtime) 1.3 MB (+44 KB) 478 KB (+16 KB)
Type declarations 467 KB (+1.8 KB) 169 KB (+910 B)
Source maps 2.6 MB (+75 KB) 888 KB (+24 KB)
Other 11 KB 3.7 KB
Total 4.4 MB (+121 KB) 1.5 MB (+41 KB)
Per-entry composition (own code — deps external (as shipped))
Entry Initial (gz) Lazy (gz) Total (gz) node_modules (min) Own code (min)
. 107 KB (+72 B) 2.5 KB 110 KB (+72 B) external 347 KB (+77 B)
./beta 113 KB (+9.9 KB) 484 B 114 KB (+9.9 KB) external 338 KB (+27 KB)
./testing 46 KB (+1 B) 33 KB (+74 B) 79 KB (+75 B) external 229 KB (+175 B)
./tsdown 520 B 0 B 520 B external 813 B
./type-generator 26 KB (+31 B) 0 B 26 KB (+31 B) external 74 KB (+42 B)

Chunks:

Entry Chunk Load Size (gz)
. index.js initial 103 KB
. utils.js initial 4.6 KB
. remote-tunnel-manager.js lazy 2.5 KB
./beta beta.js initial 93 KB
./beta modular.js initial 6.0 KB
./beta stream-manager.js initial 5.9 KB
./beta service-context.js initial 4.3 KB
./beta databricks.js initial 3.3 KB
./beta client.js initial 646 B
./beta index.js initial 20 B
./beta supervisor-api.js lazy 192 B
./beta databricks.js lazy 177 B
./beta index.js lazy 115 B
./testing manifest.js initial 33 KB
./testing index.js initial 10 KB
./testing wide-event-emitter.js initial 2.9 KB
./testing index.js lazy 29 KB
./testing remote-tunnel-manager.js lazy 2.5 KB
./testing utils.js lazy 1.8 KB
./tsdown index.js initial 520 B
./type-generator index.js initial 26 KB

@databricks/appkit-ui

npm tarball (packed): 404 KB (+7.5 KB) — gzipped download (dist + bin; excludes release-only docs/NOTICE).

dist raw gzip
JS (runtime) 436 KB (+6.9 KB) 149 KB (+2.7 KB)
Type declarations 270 KB (+2.6 KB) 100 KB (+1.3 KB)
Source maps 861 KB (+13 KB) 290 KB (+5.4 KB)
CSS 16 KB 3.2 KB
Total 1.5 MB (+23 KB) 542 KB (+9.4 KB)
Per-entry composition (consumer bundle — deps bundled, peerDeps external)
Entry Initial (gz) Lazy (gz) Total (gz) node_modules (min) Own code (min)
./js 5.3 KB 49 KB 55 KB 208 KB 14 KB
./js/beta 2.1 KB 0 B 2.1 KB 0 B 5.0 KB
./react 434 KB (+55 B) 49 KB 483 KB (+55 B) 1.3 MB (+3 B) 178 KB (+126 B)
./react/beta 14 KB (+9.2 KB) 0 B 14 KB (+9.2 KB) 25 KB (+25 KB) 16 KB (+3.4 KB)

Chunks:

Entry Chunk Load Size (gz)
./js index.js initial 5.2 KB
./js chunk initial 120 B
./js apache-arrow lazy 49 KB
./js/beta beta.js initial 2.1 KB
./react index.js initial 432 KB
./react tslib initial 2.1 KB
./react apache-arrow lazy 49 KB
./react/beta beta.js initial 14 KB

@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 1 · Fail · 3 critical, 2 major

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The canvas, multi-selection, notes, persistence across a real restart, and production 404 work, and the automated suite passes. The handoff is not reliable: normal selections can lack source locations, contain stale props, and include screenshots missing visible content. Valid wrapped components are also omitted, and concurrent reads can falsely report no pending selections.

Required

  • critical: Selecting AppKit UI components can omit the required source location or report an unrelated ancestor. (packages/appkit-ui/src/react/design/inspect.ts:86–87)
    Proof: Ran the design plugin in Chrome using the branch build and appkit-ui with published-package exports. Selected Primary action in the supplied ExampleCard template: the picker displayed no source location, and both GET /api/design/selection and .appkit/design-selection.json omitted source for Button. Selecting Library button on the running app instead saved the enclosing main element location. The picker only reads the closest native data-source attribute; dependency components are excluded from the existing JSX transform. See canvas-selection.png and checks.txt.
  • critical: The picker persists stale component props after ordinary React updates. (packages/appkit-ui/src/react/design/inspect.ts:69–80)
    Proof: In Chrome, incremented a parent useState counter three times, then selected the child LiveCard button and sent it. The visible text and persisted text were Count: 3, but persisted props.count was 2. A separate sequence reproduced rendered/saved pairs 0/0, 1/0, 2/2, 3/2, 4/4. Walking the DOM-attached fiber without resolving its current alternate reads the previous props on alternating updates. See app-selection.png and the saved endpoint output in checks.txt.
  • critical: Saved screenshots omit visible images and canvas content. (packages/appkit-ui/src/react/design/inspect.ts:119–125)
    Proof: Selected and sent a real component preview containing a same-origin image and an HTML canvas chart. Chrome displayed both, as shown in canvas-selection.png. Opened the actual JPEG referenced by the saved selection: the image became a broken-image icon and the chart disappeared. agent-screenshot.jpeg is that unedited file. Cloning and serializing the DOM does not preserve canvas pixels or embed image resources.
  • major: The canvas silently omits PascalCase memo and forwardRef component exports. (packages/appkit-ui/src/react/design/design-canvas.tsx:38–40)
    Proof: Added MemoDraft = memo(...) and RefDraft = forwardRef(...) alongside ordinary function previews in the isolated test app. Browser inspection found only BrokenDraft, RealPreview, and ExampleCard frames; MemoDraft and RefDraft were absent. An independent server-rendering probe likewise rendered only the ordinary function. Both wrappers are valid React component types but typeof returns object, which the filter rejects. checks.txt includes the actual fixture exports and browser frame list.
  • major: Reading selections during a write can falsely return an empty pending list. (packages/appkit/src/plugins/design/store.ts:63–67,107–109)
    Proof: Seeded one selection, appended 100 small selections, and concurrently polled read() from four readers without clearing. Of 1,019 reads, 104 returned an empty selections array; a new store after completion read all 101 entries. writeFile truncates the live file, reads bypass the write queue, and parse failures are converted to an empty list. This proves transient incorrect reads, not durable loss after completed writes. Runnable reproduction and output are included in checks.txt.

@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 2 · Pass

Does the change do what the task asked? Yes. Gate: major and worse must be fixed.

The five earlier findings are fixed, and I found no regressions from those fixes. Browser checks against the built UI package, the full test suite, typechecking, and read-only lint/format checks passed. There are no remaining findings in this round.

No findings.

@MarioCadenas
MarioCadenas force-pushed the work/1-design-plugin-dev-only-design- branch from af1f4a2 to aa65b0d Compare October 20, 2026 13:01
@MarioCadenas
MarioCadenas changed the base branch from main to work/2-appkit-plugin-add-with-auth-mo October 20, 2026 13:01
@MarioCadenas MarioCadenas changed the title Design plugin (dev-only /design) and ui-only template feat(appkit): add dev-only design plugin and ui-only template Oct 20, 2026
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 5 · Fail · 1 critical, 1 major

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The design canvas, selection handoff, persistence and production 404 behavior work in the exercised cases, and all 50 targeted tests pass. The screenshot requirement is incomplete: selecting an absolutely positioned element can silently save an entirely blank image. The added CLI also omits declared resource defaults from deployment variables in an unusual supported case.

Required

  • critical: Selecting an absolutely positioned element can silently send a blank screenshot to the agent. (packages/appkit-ui/src/react/design/inspect.ts:145-151 and 201-211)
    Proof: In Chrome at /design, selected a visible red button with position:absolute, left:180px, top:70px, width:220px and height:60px, then sent it through the actual picker. The UI reported success and persisted a JPEG, but that 220x60 image contained zero nonwhite pixels. The original button and saved image are compared in screenshot-failure.png. prepareClone retains the root positioning offsets inside a crop sized only to the element dimensions, placing the button outside its screenshot.
  • major: The new plugin add command omits manifest resource defaults from generated deployment variables. (packages/shared/src/cli/commands/plugin/add/plan.ts:396)
    Proof: Ran the source CLI plugin add analytics --yes against a temporary app whose analytics manifest declared fields.id.value="warehouse-default". The command wrote DATABRICKS_WAREHOUSE_ID=warehouse-default to .env, but databricks.yml referenced ${var.sql_warehouse_id} with neither a default nor target assignment. A direct planning probe also reported no missing values. checks-r5.txt includes the command output and generated configuration; no deployment was attempted.

@github-actions

github-actions Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

🤖 AppKit PR bot

🔬 Run evals

Start an eval for this PR from the evals-monitor app: Go to Evals Monitor →

📦 Try this PR's app template

Scaffolds a new app from this PR's SDK build. Run it in any folder (requires the GitHub CLI — gh auth login — and the Databricks CLI):

gh run download 42205587970 -R databricks/appkit -n appkit-template-0.90.0-pr.329b318-work-1-design-plugin-dev-only-design-680 -D appkit-pr-680 \
  && unzip -o "appkit-pr-680/appkit-template-0.90.0-pr.329b318-work-1-design-plugin-dev-only-design-680.zip" -d "appkit-pr-680" \
  && databricks apps init --template "appkit-pr-680"

The template pins @databricks/appkit and @databricks/appkit-ui to tarballs built from this branch, so the scaffolded app runs against this PR's code.

@MarioCadenas
MarioCadenas force-pushed the work/1-design-plugin-dev-only-design- branch from aa65b0d to 4d00fbf Compare October 20, 2026 14:22
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 6 · Pass

Does the change do what the task asked? Yes. Gate: major and worse must be fixed.

Both previous findings are fixed at the reviewed commit. Chrome reproduced the blank screenshot with the previous code and verified the saved JPEG with the fix; actual plugin-add runs preserved manifest defaults in deployment YAML. The focused regression checks passed, with no remaining findings in this round.

No findings.

@MarioCadenas
MarioCadenas force-pushed the work/1-design-plugin-dev-only-design- branch from 4d00fbf to acf5c0f Compare October 20, 2026 15:37
@MarioCadenas
MarioCadenas added this pull request to stack #681 October 20, 2026 16:09
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 7 · Fail · 3 critical

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The main canvas, source tracing, persisted handoff, production 404 behavior, and ui-only template work in the exercised paths. Three browser-proven faults remain: open dialogs disable the picker, completing a send discards selections added during that send, and screenshots omit typed values in uncontrolled inputs. The repository was left unchanged.

Required

  • critical: Opening an AppKit dialog makes the design picker unclickable, preventing selection of modal content. (packages/appkit-ui/src/react/design/design-picker.tsx:237)
    Proof: Ran node /tmp/appkit-design-round7/browser.mjs in Chromium against the current source. Opened the actual AppKit Dialog using its trigger, then attempted to click Select; Playwright timed out. Computed pointer-events was none on both body and the picker button, versus auto on dialog content. The picker host only sets position/z-index and inherits the disabled pointer events. See round7-dialog-blocked.png, round7-interactions.webm, and round7-checks.txt. Reproduce at http://127.0.0.1:5197/ by clicking Open sample dialog, then Select.
  • critical: A completed send silently discards selections added while that request was pending. (packages/appkit-ui/src/react/design/design-picker.tsx:143 (selection changes remain enabled at line 105))
    Proof: In the Chromium run, held the POST response using Playwright routing, selected Absolutely positioned action, and clicked Send 1 to agent. While the request was pending, selected Translated action; the UI offered an enabled Send 2 to agent button. Released the original request: both selections disappeared and the UI reported Sent, but the request and persisted endpoint contained only Absolutely positioned action. The successful send clears all current picks, including the unsent addition. See round7-interactions.webm and round7-checks.txt.
  • critical: Screenshots sent to the agent omit the current typed value of an uncontrolled text input. (packages/appkit-ui/src/react/design/inspect.ts:228 (prepareClone does not preserve live input state))
    Proof: Ran node /tmp/appkit-design-round7/form-check.mjs in Chromium. Filled a normal input with REVIEW TITLE, selected it, and sent it through the picker. The saved JPEG showed the Enter title placeholder instead of the visible text; it was byte-identical to a capture taken after clearing the input. The live value exists as a DOM property, but XML serialization retains the empty value attribute. round7-form-screenshot.png compares the visible control with the actual persisted screenshot; round7-checks.txt records the assertion.

@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 8 · Pass

Does the change do what the task asked? Yes. Gate: major and worse must be fixed.

F8, F9 and F10 are fixed: browser checks confirmed modal selection, preservation of later picks and edited notes during a pending send, and screenshots containing current form values. Focused tests and nearby runtime checks passed, with no remaining findings in this review round. The repository was left unchanged.

No findings.

@MarioCadenas
MarioCadenas force-pushed the work/1-design-plugin-dev-only-design- branch from 9bdf7b9 to ad6dc6e Compare October 26, 2026 14:19
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 10 · Fail · 3 critical

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The change does not meet the full task: the running app has no selection interface, open dialogs block selection, and clicking an SVG path saves a blank screenshot. The normal canvas handoff, source metadata, persistence across a server restart, and production 404 behavior worked locally. All 71 tests exercised passed, including the previously failing React type test.

Required

  • critical: The design plugin does not provide element selection in the running app. (packages/appkit/src/plugins/design/vite-plugin.ts:62; packages/appkit-ui/src/react/design/design-canvas.tsx:194)
    Proof: Ran a local app with server() and design(), successfully selected and sent two elements from /design, then navigated to /. The real app component rendered, but Playwright found zero #appkit-design-picker roots and zero Select buttons. Source inspection confirms the picker is mounted only by DesignCanvas, whose entry is served only for /design and /design/. See running-app-without-picker.png and review-checks.txt. This omits the explicit requirement to select elements in the running app.
  • critical: Opening a normal AppKit dialog prevents users from enabling selection for its contents. (packages/appkit-ui/src/react/design/design-canvas.tsx:100; packages/appkit-ui/src/react/design/design-picker.tsx:166)
    Proof: Rendered an AppKit Dialog in a design preview and opened it through DialogTrigger. Clicking header button[aria-pressed] timed out because the z-50 dialog overlay intercepted pointer events; the dialog remained open and aria-pressed stayed false. The Select control sits in the z-10 header outside the dialog, and there is no activation keyboard shortcut. Enabling selection first consumes the dialog trigger click through the picker listeners. See modal-picker-blocked.png and the browser trace in review-checks.txt; the live fixture includes Open preview dialog.
  • critical: Clicking an SVG icon path sends a blank screenshot to the agent. (packages/appkit-ui/src/react/design/inspect.ts:228)
    Proof: In Chrome, enabled Select, clicked a visible red SVG path inside an icon button, and sent the selection. The persisted element correctly had tag path and a screenshot filename, but fetching and decoding that JPEG produced a 32 by 32 image with zero non-white pixels. The capture clones the path into an HTML div without its owning SVG, so the stored screenshot loses the selected visual. The exact fixture, saved metadata, and pixel analysis are in review-checks.txt; IconPreview in the live canvas reproduces it.

@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 11 · Fail · 2 critical

Does the change do what the task asked? No. Gate: major and worse must be fixed.

F12 and F13 are fixed and worked in Chromium, but the change does not yet meet the supplied task. F11 remains against the original running-app selection requirement; the claimed later scope change was not confirmed. Pressing the advertised Escape shortcut after selecting dialog content also closes the dialog and silently loses its screenshot when sent.

Required

  • critical: The design plugin still does not provide element selection in the running app. (packages/appkit/src/plugins/design/vite-plugin.ts:62; packages/appkit-ui/src/react/design/design-canvas.tsx:216)
    Proof: Opened the same temporary AppKit application at /design and / in Chromium. Selection works at /design; the running app has zero #appkit-design-picker roots and zero Select buttons. Executing the Vite plugin hooks also showed / and /orders passing through unchanged, with no app-page picker injection. Git history corroborates intentional removal, but does not independently establish the cited human scope change.
  • critical: Pressing Escape to stop selecting dialog content closes the dialog and silently saves the selection without its screenshot. (packages/appkit-ui/src/react/design/design-picker.tsx:184; packages/appkit-ui/src/react/design/design-picker.tsx:218; packages/appkit-ui/src/react/design/inspect.ts:232)
    Proof: Reproduced twice in Chromium: open a normal AppKit Dialog, enable Select, pick its title, press the advertised Esc-to-stop shortcut, then Send 1 to agent. Escape closes the dialog while the picker retains one selection; sending reports success. GET /api/design/selection and the on-disk .appkit/design-selection.json both contain selection 48e4923a-0cba-4eb9-8cd3-2f4daed9766a without a screenshot field. A control stopping selection with the header button keeps the dialog open and saves its screenshot. Escape is allowed to reach the dialog, and the later capture skips the now-detached element bec

@MarioCadenas MarioCadenas changed the title feat(appkit): add dev-only design plugin and ui-only template feat(appkit): add dev-only design pages plugin and ui-only template Oct 27, 2026
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 12 · Fail · 2 critical, 1 major

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The design pages and ui-only starter work, including hot reload and production 404s. The change does not meet the supplied task because element selection and persistent agent handoff are absent. An unrelated unfinished draft can also break an otherwise valid design page.

Required

  • critical: Users cannot select multiple elements or attach a note in either the design canvas or the running app. (packages/appkit/src/plugins/design/vite-plugin.ts:39; packages/appkit/src/plugins/server/vite-dev-server.ts:89)
    Proof: In Chromium, /design rendered the template sample with only its Primary action button. Clicking the heading and button produced no selection interface, note field or send control; the running app likewise had no picker and its button performed its ordinary action. Native elements carried data-source attributes, but source inspection confirms the entry module only renders the page and installs no selection/inspector UI. See validation.txt and design-review.webm.
  • critical: The required persisted selection record and builder-agent pull interface are not implemented. (packages/appkit/src/plugins/design/index.ts:28; packages/appkit/src/plugins/design/)
    Proof: GET and POST /api/design/selection both returned 404 from the running development app, and .appkit/design-selection.json did not exist after the browser interaction. The complete plugin contains only page resolution/rendering and the production 404; searching packages and template found no selection store, screenshot capture, selection endpoint or design MCP implementation. Consequently no record containing component, source location, props, screenshot and note can be saved or retrieved. See validation.txt.
  • major: Eagerly importing every design page lets an unrelated unfinished draft break a valid route. (packages/appkit/src/plugins/design/vite-plugin.ts:45)
    Proof: After /design rendered successfully, I added client/src/design/pages/unfinished.tsx importing a component that did not exist yet, without changing the index or visiting /design/unfinished. Reloading /design displayed a Vite unresolved-import overlay for unfinished.tsx and the valid index heading disappeared. Removing only the unfinished page restored /design. The entry module imports all matching pages with eager:true before choosing the requested one. See broken-draft.png, design-review.webm and validation.txt.

@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 13 · Fail · 2 critical

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The broken-draft loading bug is fixed, including live browser rendering and hot reload beside an unfinished page. The current task still explicitly requires multi-selection with notes and a persisted agent handoff; both remain absent despite their intentional removal, so the change does not meet all stated requirements.

Required

  • critical: Users still cannot select multiple elements or attach a note in either the design canvas or the running app. (packages/appkit/src/plugins/design/vite-plugin.ts:40; packages/appkit/src/plugins/server/vite-dev-server.ts:87)
    Proof: Ran the actual source AppKit server with server() and design() in an isolated local fixture. In Chrome at /design and /, clicked one shared component and Shift-clicked another, then tried Cmd+K: only native text highlighting appeared, with zero textboxes, dialogs or toolbars and only the original application buttons. Clicking a button invoked its original handler. Source inspection confirms the generated entry only mounts Page and the server adds data-source metadata without a picker, note field or send handler. See design-selection.png, app-selection.png, browser-checks.webm and checks.txt.
  • critical: The required persisted selection record and builder-agent pull interface are still not implemented. (packages/appkit/src/plugins/design/index.ts:28; packages/appkit/src/plugins/design/)
    Proof: On the running development fixture, GET and POST /api/design/selection both returned 404, and .appkit/design-selection.json did not exist after the browser interaction checks. Read every design plugin file: setup() returns immediately in development and only vitePlugins() contributes page serving; there is no selection schema, component/props/screenshot capture, persistence or replacement selection endpoint/MCP tool. Repository searches also found no design-selection or /api/design/selection implementation. HTTP observations are saved in checks.txt.

@MarioCadenas
MarioCadenas force-pushed the work/1-design-plugin-dev-only-design- branch 3 times, most recently from adfa702 to b5f6314 Compare October 28, 2026 09:44
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 14 · Fail · 1 critical, 2 major

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The change does not meet the full task: the required element selection and persistent agent handoff are absent. Design page rendering, navigation and production 404s work; 83 targeted tests pass and both changed TypeScript packages typecheck. Browser testing also reproduced false readiness after a render error and a broken route for pages/index.tsx.

Required

  • critical: The required element-selection and persistent agent-handoff workflow is missing. (packages/appkit/src/plugins/design/index.ts:64 and packages/appkit/src/plugins/design/vite-plugin.ts:128)
    Proof: Ran the real server()+design() source in Chromium on /design and the running app at /. Clicking the shared component invokes its ordinary action; there are no picker, multi-select, note or send controls. GET and POST /api/design/selection both return 404, and .appkit/design-selection.json is absent. Source inspection confirms that only page rendering/readiness and existing data-source attributes remain: no component/props/screenshot selection capture, selection store, or agent pull endpoint/tool exists. Commit 1f915cc explicitly removed these implementations. See checks.txt and working-design
  • major: A hot edit that fails to render still marks the design ready and notifies the builder. (packages/appkit/src/plugins/design/vite-plugin.ts:175)
    Proof: After a successful initial paint in a cross-origin builder iframe, edited the temporary DesignPage to throw during render. Chromium displayed Unexpected Application Error! and Review: render failed after hot edit, while GET /design/__status returned ready:true and the builder received a fresh appkit:design-ready message for index. The vite:afterUpdate handler reports the stale current page without checking whether rendering succeeded. See broken-readiness.png, checks.txt and review-session.webm.
  • major: The advertised /design/index page fails when its file is pages/index.tsx. (packages/appkit/src/plugins/design/vite-plugin.ts:135 and packages/appkit/src/plugins/design/vite-plugin.ts:193)
    Proof: Added a valid client/src/design/pages/index.tsx beside the root design/index.tsx. GET /design/__status listed both /design and /design/index. Opening /design/index returned HTTP 200 but Chromium rendered React Router’s 404 Not Found error screen. The generated router maps both files to / instead of creating /index. See broken-index-route.png and checks.txt.

@MarioCadenas
MarioCadenas force-pushed the work/1-design-plugin-dev-only-design- branch from b5f6314 to 48d89da Compare October 28, 2026 10:22
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 15 · Fail · 1 critical, 1 major

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The required selection and persistent agent-handoff workflow is still missing. The render-error fix works for edits to the index page, but readiness remains incorrectly true when an imported component fails after a hot edit. F20 is fixed, and all 49 focused design and server tests pass.

Required

  • critical: The required element-selection and persistent agent-handoff workflow is still missing. (packages/appkit/src/plugins/design/index.ts:64; packages/appkit/src/plugins/design/vite-plugin.ts:148 and :296)
    Proof: Read the complete design implementation and traced the existing source-location plugin: it renders pages, adds native-element data-source attributes, and exposes readiness only. Repository search for design-selection/designSelection across packages, apps, template and tools returned no matches. In Chrome, clicking and shift-clicking elements on both /design and the running app only activated the ordinary component action; no selection/note UI appeared and no .appkit/design-selection.json was created. There is no component/props/screenshot/note collection, persistent selection store, or agent p
  • major: A failing hot edit to an imported component still leaves /design marked ready. (packages/appkit/src/plugins/design/vite-plugin.ts:95-116 and :181-199)
    Proof: In the cross-origin Chrome fixture, first rendered /design successfully, then changed only client/src/components/OrderCard.tsx to throw during render. The error boundary displayed "Design page failed to render: Review: shared card hot edit failed", while GET /design/__status continued returning ready:true. Ready-message count stayed at 5, so the message suppression works but the endpoint remains stale. Reproduced without react-router as well (ready:true, message count unchanged at 3). designStatus tracks only index.tsx mtime, and the error boundary never invalidates server readiness. Direct in

@MarioCadenas
MarioCadenas force-pushed the work/1-design-plugin-dev-only-design- branch from 0341ad5 to 2d7a963 Compare October 28, 2026 18:32
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 20 · Pass · 1 minor, 1 trivial

Does the change do what the task asked? Yes. Gate: major and worse must be fixed.

Taking the human's later scope decisions into account (selection handling moved to the builder's inspector, drafts served with a hydrator), the branch does what was asked: /design is dev-only and returns 404 otherwise, drafts render real appkit-ui blocks, errors are reported, the props schema is published, and the ui-only template is generated. All 67 design-plugin tests and the use-design-ready tests pass. One edge case is left: the dark-mode token sync follows the system color scheme and ignores a draft that forces its own theme.

Not required (below the gate)

  • minor: The chart theme tokens copied to the draft root always come from a probe element with no theme class, so a draft that forces a theme with or class="light" still gets the system's theme for its charts. (packages/appkit/src/plugins/design/drafts.ts:539-559)
    Proof: Read the code: the probe
    never takes the document's .dark/.light class, and appkit-ui's globals.css picks its theme with .dark and :root:not(.light), so the probe resolves the theme from prefers-color-scheme alone. Not exercised in a browser.
  • trivial: The original requirements for click-to-select, .appkit/design-selection.json and handing selections to the agent were removed on purpose in bbf5db8, following later decisions from the coordinator and the human; noted so the reviewer of the PR knows the task text and the branch differ. (commit bbf5db8d, said-by.jsonl coordinator messages)
    Proof: git log body of bbf5db8; coordinator 'New decisions from the human' messages

@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 21 · Fail · 1 major

Does the change do what the task asked? Yes. Gate: major and worse must be fixed.

This round's additions (browserless status fields, theme.css, shipped schema, chart data types, template vitest inline) are in place and the design and chart tests pass. One claim is overstated: compiled only transforms the index file, so a syntax error in a component the index imports still reports compiled: true and waitingFor: "paint", and an agent waiting without a browser would wait forever.

Required

  • major: compiled in /design/__status only transforms the index module, so a broken imported component reports compiled: true / waitingFor: "paint" instead of "compile" with an error, contrary to the claim that the page and its imports build. (packages/appkit/src/plugins/design/vite-plugin.ts:594-606)
    Proof: Real Vite server, same transformRequest call: index.tsx importing ./Bad (Bad.tsx = const x = {;) gives index OK, Bad.tsx ERR Unexpected token. See compiled-misses-broken-import.txt. The unit test mocks transformRequest, so it can't catch this.

- design() plugin (beta): in development serves a /design canvas that
  renders every PascalCase export under client/src/design/, and injects a
  click-to-select picker into the canvas and every app page. Picks are traced
  via the existing data-source transform plus the React fiber (component,
  owner stack, props), screenshotted, and persisted with an optional note to
  .appkit/design-selection.json (GET/POST/DELETE /api/design/selection).
  Outside development it mounts nothing and /design returns 404.
- Plugins can contribute dev-server Vite plugins via an optional
  vitePlugins() hook.
- appkit-ui/react/beta: DesignCanvas, DesignPicker, mountDesignPicker.
- Template: gated client/src/design example, .appkit/ gitignored, and a
  ui-only app template (server + design).

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: MarioCadenas <MarioCadenas@users.noreply.github.com>
MarioCadenas and others added 4 commits November 5, 2026 21:18
The top-level compiled/compileError come from the index entry of pages,
which already builds it, instead of a second compile of the same import
graph per request. indexVersion, a one-use wrapper, is inlined. Same JSON.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: MarioCadenas <MarioCadenas@users.noreply.github.com>
…ng facts

No code change. Multi-line comments are cut to one short line (JSDoc
contracts kept, tightened), rationale repeated in several places is kept
in one (chart default height, the builder-origin format), and stale
wording ("after first paint", "only with a builder origin") is fixed.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: MarioCadenas <MarioCadenas@users.noreply.github.com>
The /design/__stream host no longer posts appkit:stream-frame messages,
and the APPKIT_DESIGN_STREAM_MODE=boundary switch is gone, with its test.
Both only served the KIT-40 spike's measurements (its replay app is
already removed); nothing in App Builder reads or sets them. Streaming
itself is unchanged.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: MarioCadenas <MarioCadenas@users.noreply.github.com>
…th-mo' into work/1-design-plugin-dev-only-design-

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: MarioCadenas <MarioCadenas@users.noreply.github.com>
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 39 · Fail · 1 critical, 1 minor

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The dev-only /design pages, production 404, data-source file:line instrumentation, readiness status and the ui-only template entry are built and their tests pass. The selection handoff the task plainly asks for (multi-select with a note, sent to the agent, persisted to .appkit/design-selection.json, exposed via endpoint or MCP tool) was removed in 45b1261 and is not on this branch. The agent says the human narrowed scope to delegate selection to App Builder's inspector, but I found no such instruction in the board's inbox, and the agent's own closing note leaves that question open for the human.

Required

  • critical: The selection handoff is not built: there is no multi-select with a note, no screenshot or props capture, no .appkit/design-selection.json, and no endpoint or MCP tool for the agent. (packages/appkit/src/plugins/design/ (removed in 45b126186))
    Proof: git diff 05c51e2...HEAD | rg -i 'design-selection|mcp' finds nothing. Commit 45b1261 says it removes the element picker, the selection store and the /api/design routes. The closing note asks the human whether to restore them and says no answer has come yet. If the human really did narrow the scope, this finding does not apply.

Not required (below the gate)

  • minor: Click-to-select is left to an external builder inspector reading data-source attributes; the existing appkit inspector is not wired to it in this change. (docs/docs/plugins/design.md:71)
    Proof: The docs only say that a builder's inspector can read data-source. No in-repo inspector consumes it.

@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 40 · Fail · 1 critical, 1 minor

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The dev-only /design pages and the ui-only template exist, but the selection handoff the task plainly requires is not built. Commit 45b1261 removed the multi-select picker, notes, screenshots, the .appkit/design-selection.json store and the /api/design endpoint, and nothing replaces them at HEAD. The agent's argument that an earlier tested build also lacked them does not change what the task asks for.

Required

  • critical: There is no way to select elements, add a note and send the selection to the agent: no picker, no persisted .appkit/design-selection.json, and no endpoint or MCP tool for the agent to pull from. (packages/appkit/src/plugins/design/ (removed in 45b126186))
    Proof: rg design-selection over the repo at b35ff17 returns no matches; 45b1261 'make the design plugin serve full-size /design pages only' is an ancestor of HEAD. See selection-absent.txt.

Not required (below the gate)

  • minor: Click-to-select in the running app is not traceable: nothing in the repo reads the emitted data-source attributes. (appkit-ui inspector / design plugin)
    Proof: Raised by the previous reviewer and confirmed by the agent's own note; not re-run here.

@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 41 · Fail · 2 critical

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The dev-only design plugin, /design canvas, production 404 and the ui-only template entry are built, and the plugin's 61 tests pass. The selection half of the task is not built: click-to-select, multi-select with a note, the agent handoff, .appkit/design-selection.json and the endpoint/MCP tool. The agent says a human ruled selection out of scope, but the board description still asks for it, so I judged against that and leave the waiver for the human to confirm.

Required

  • critical: Click-to-select, multi-selection with a note, and sending selections to the agent (component, file:line, props, screenshot, note) are not built; the agent says this was descoped by a human decision that the task description does not reflect. (packages/appkit/src/plugins/design/)
    Proof: rg -i 'selection|screenshot|mcp' over packages/appkit/src/plugins/design/*.ts finds nothing; no picker or send UI exists in the diff.
  • critical: Selections are not saved to .appkit/design-selection.json and no endpoint or MCP tool exposes them to the agent. (whole branch)
    Proof: rg 'design-selection' across the repo (excluding node_modules) returns no matches.

@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 42 · Pass · 1 minor

Does the change do what the task asked? Yes. Gate: major and worse must be fixed.

The PR at b35ff17 is a draft, its head matches local, and all CI checks are green. The design plugin, appkit-ui and chart test suites pass locally (16 files, 334 tests). The plugin answers 404 outside development and registers no Vite plugin there. The only nit: an invalid builder-origin env var still throws in production.

Not required (below the gate)

  • minor: An invalid APPKIT_DESIGN_BUILDER_ORIGIN makes design() throw at construction even in production, where the plugin is supposed to do nothing. (packages/appkit/src/plugins/design/index.ts:63)
    Proof: Read the code: parseOrigins runs in the constructor with no isDev() guard, and it throws on a non-bare origin.

ditadi and others added 2 commits November 6, 2026 10:48
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 43 · Fail · 1 critical

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The code at 453a05d is in good shape: all 24 CI check runs pass and the design plugin's 61 tests pass locally. But the task says plainly that PR #680 stays a draft, and it is not a draft any more. It was marked ready for review today, so that requirement is not met.

Required

  • critical: PR feat(appkit): add dev-only design pages plugin and ui-only template #680 is no longer a draft, but the task requires it to stay one. (https://github.com/databricks/appkit/pull/680)
    Proof: gh pr view 680 --json isDraft returns false. The issue events show ready_for_review by MarioCadenas at 2026-11-06T09:32:28Z. If a human did this on purpose, the task text is out of date; otherwise convert the PR back to a draft.

fjakobs and others added 14 commits November 9, 2026 09:06
…allbacks (#716)

Signed-off-by: Fabian Jakobs <fabian.jakobs@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
…parent (#717)

Signed-off-by: Fabian Jakobs <fabian.jakobs@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Fabian Jakobs <fabian.jakobs@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
…713)

Signed-off-by: Fabian Jakobs <fabian.jakobs@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
…e token (#711)

Signed-off-by: Fabian Jakobs <fabian.jakobs@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Fabian Jakobs <fabian.jakobs@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: databricks-appkit[bot] <databricks-appkit[bot]@users.noreply.github.com>
… routes (#712)

Signed-off-by: Fabian Jakobs <fabian.jakobs@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: databricks-appkit[bot] <databricks-appkit[bot]@users.noreply.github.com>
Signed-off-by: Mike Helmick <mike.helmick@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: databricks-appkit[bot] <databricks-appkit[bot]@users.noreply.github.com>
Signed-off-by: databricks-appkit[bot] <databricks-appkit[bot]@users.noreply.github.com>
@MarioCadenas

Copy link
Copy Markdown
Collaborator Author

Review 44 · Fail · 1 critical, 1 pre-existing

Does the change do what the task asked? No. Gate: major and worse must be fixed.

The design plugin code looks complete for the scope: dev-only /design routes, TSX staging stream, __status, DesignPage/useDesignReady, chart sizing and the template entry. Its tests, typecheck and lint pass, and the out-of-scope HTML-draft and selection code is gone. But the task plainly requires the PR to stay a draft, and #680 is open as ready for review.

Required

Not required (there before this change)

  • trivial: oxlint warns about an unused ChartBaseProps import in charts/base.tsx; the line is not part of this diff. (packages/appkit-ui/src/react/charts/base.tsx:44)
    Proof: pnpm check output

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants