[ditadi]

What did you change, and why?

Why: Generated database CRUD currently defaults to exposure without per-operation authorization.

Change: Adds design 002, Database route operations. Comments and edits happen in the Google Doc; approved changes are synced to this file. The design covers schema-derived contracts, required authorization, actor identity, source-less bundles, client hooks, and removal of legacy CRUD.

This is PR 00 only. Implementation slicing and code wait for operator validation. No runtime behavior, API, template, or generated output changes.

How do you know it works?

Testing: Docs only. Checked source references, required design sections, code fences, approval gates, and exclusion of internal research. Reviewed competing designs and addressed independent security and architecture findings. The normal commit hook passed knip. Runtime behavior, type inference, packaging, and telemetry proofs remain explicitly unverified.

[github-actions]

🤖 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 39676091904 -R databricks/appkit -n appkit-template-0.89.0-pr.5aa7f15-victor-ditadi-data-stack-database-route-blocks-00-design-683 -D appkit-pr-683 \
  && unzip -o "appkit-pr-683/appkit-template-0.89.0-pr.5aa7f15-victor-ditadi-data-stack-database-route-blocks-00-design-683.zip" -d "appkit-pr-683" \
  && databricks apps init --template "appkit-pr-683"

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.