report-to-databricks-applisted

# Report contract → Databricks App The second consumer of the governed reporting core. A report skill renders the contract offline; this makes the same contract interactive on Databricks Apps — the same SQL files, the same parameters, the same execution identities. This skill is an **adapter, not an app builder**. It owns exactly one thing: getting the contract into the app correctly and keeping it there. Scaffolding, screen design and deployment belong to skills that already do them well, and this skill loads them rather than reimplementing them. ## When to use - A validated contract (or a report skill built from one) should become an interactive app. - The app and the report disagree on a number. - Someone edited the app's SQL by hand and it needs to go back under the contract. - CI should fail when the app's copy drifts. ## When NOT to use - **An app with no contract behind it** → `databricks-apps`. This skill has nothing to materialize. - **How the screens should look** → `databricks-app-design` (KPI composition, charts, states, Genie trust). Load it alongside; do not design here. - **Bundle structure, targets, permissions** → `databricks-dabs`. - **A managed dashboard** → `databricks-aibi-dashboards`. "Build me a dashboard" is not this skill. - **Generating the report skill** → `report-skill-builder`. ## Workflow 1. **Validate the contract first.** An app built on an invalid contract is a faster way to be wrong. ```bash python3 "${CLAUDE_SKILL_DIR}/../go