feat: update README on usage, and disable dropdown of targets

cornzyblack · Copilot · cornzyblack · commit aaf3293b65e1 · 2026-05-04T21:24:21.000+01:00
Co-authored-by: Copilot &lt;copilot@github.com&gt;
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,6 +2,13 @@
 
 All notable changes to the **Databricks Bundle Inspector** extension are documented in this file.
 
+## [0.1.1] - 2026-05-04
+
+### Changed
+
+- Simplified README to focus on structural DAG visualization and removed development/testing documentation.
+- Disabled target selection dropdown in the panel. The extension now displays "structural preview" only, removing the ability to switch between targets. This aligns with the focus on structural inspection.
+
 ## [0.1.0] - 2026-05-04
 
 Initial public release. The extension is a read-only inspector for Declarative Automation Bundles (previously known as Databricks Asset Bundles). It runs `databricks bundle validate --output json`, renders the resolved bundle as an interactive graph, and surfaces bundle issues in VS Code's native Problems panel. Everything operates on the CLI-resolved bundle. The extension does not modify YAML and does not call Databricks workspace APIs.
@@ -91,5 +98,6 @@ Initial public release. The extension is a read-only inspector for Declarative A
 - Node 22 (development).
 - Databricks CLI `v0.270.1` or newer.
 
-[Unreleased]: https://github.com/uncoverthestack/databricks-bundle-inspector/compare/v0.1.0...HEAD
+[Unreleased]: https://github.com/uncoverthestack/databricks-bundle-inspector/compare/v0.1.1...HEAD
+[0.1.1]: https://github.com/uncoverthestack/databricks-bundle-inspector/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/uncoverthestack/databricks-bundle-inspector/releases/tag/v0.1.0
diff --git a/README.md b/README.md
@@ -1,41 +1,38 @@
 # Databricks Bundle Inspector
 
-A VS Code extension for inspecting Declarative Automation Bundles (previously known as Databricks Asset Bundles) before you deploy or review them. It runs `databricks bundle validate --output json`, turns the CLI-resolved bundle into an interactive job graph, and surfaces bundle issues in context.
+A VS Code extension that visualizes Databricks Bundles as interactive job dependency graphs. See the actual structure of your bundle jobs, task dependencies, and configurations at a glance.
 
 ## What it does
 
-Declarative Automation Bundles (previously known as Databricks Asset Bundles) (DABs) describe jobs, tasks, dependencies, and compute in YAML that can span many files and layers of variable substitution. Reading the raw YAML rarely tells you what will actually run. This extension closes that gap inside your editor.
+Open a `databricks.yml` file and run **Inspect Databricks Bundle** to see:
 
-Open a `databricks.yml` file, run **Inspect Databricks Bundle**, and you get:
+- **Visual DAG**: Interactive graph of jobs and `depends_on` relationships with pan, zoom, and search.
+- **Task details**: Type, source file, parameters, compute, and dependencies.
+- **Issue detection**: Missing files, unresolved variables, unknown task types, and Databricks CLI diagnostics.
+- **Layout controls**: Automatic graph layout to keep parallel branches visually separated.
 
-- A visual DAG for bundle jobs, with arrows for `depends_on` relationships.
-- Task details including type, source file, parameters, compute, dependencies, and direct dependents.
-- Bundle issue detection for missing local files/libraries, unresolved variables, unknown task types, and Databricks CLI diagnostics.
-- File-content enrichment for local task files, including detected secret scopes and widgets where supported.
-
-The graph is powered by React Flow and includes pan, zoom, a minimap, search, job switching, issue-focused views, and layout controls.
+<div>
+    <a href="https://www.loom.com/share/634c3b8081f545b198e947ff68f99f3d">
+      <p>Databricks Bundle Inspector Demo - Watch Video</p>
+    </a>
+    <a href="https://www.loom.com/share/634c3b8081f545b198e947ff68f99f3d">
+      <img style="max-width:300px;" src="https://cdn.loom.com/sessions/thumbnails/634c3b8081f545b198e947ff68f99f3d-8b76e3bf25272d13-full-play.gif#t=0.1">
+    </a>
+  </div>
 
 ## Requirements
 
-The [Databricks CLI](https://docs.databricks.com/dev-tools/cli/index.html) must be installed. The extension looks for it in this order:
-
-1. The VS Code setting `databricksBundleInspector.cliPath`, if configured.
-2. `databricks` on the system `PATH`.
-
-Databricks authentication is not strictly required for structural inspection. The extension uses a probe target by default so it can often read the CLI-resolved bundle even when workspace credentials are not configured. Validation runs with a 30 second timeout.
+The [Databricks CLI](https://docs.databricks.com/dev-tools/cli/index.html) must be installed and available on your `PATH`, or configured via the `databricksBundleInspector.cliPath` VS Code setting.
 
 ## Usage
 
-1. Open a folder that contains a `databricks.yml` or `databricks.yaml` file.
+1. Open a folder containing a `databricks.yml` or `databricks.yaml` file.
 2. Open the bundle file in the editor.
-3. Run a command from one of these entry points:
-   * The **Inspect Databricks Bundle** button in the editor title bar (only shown for bundle files).
-   * Right-click in the editor and choose **Inspect Databricks Bundle**.
-   * The Command Palette.
+3. Click **Inspect Databricks Bundle** (editor title bar button) or right-click and select the command.
 
-The webview opens in a new editor column. After a bundle has been inspected, saving the bundle file or a tracked related file refreshes diagnostics and updates the active inspector panel.
+The graph opens in a new editor panel. It refreshes automatically when you save the bundle file or related configurations.
 
-## Commands
+## Command
 
 | Command ID | Title | When available |
 | --- | --- | --- |
@@ -44,191 +41,11 @@ The webview opens in a new editor column. After a bundle has been inspected, sav
 
 ## How it works
 
-The extension is split into two halves that talk over VS Code's webview message channel:
-
-The **extension host** (`src/extension.ts`) resolves the Databricks CLI, invokes `databricks bundle validate --output json` in the bundle directory, builds diagnostics/issues, enriches the graph from local task files, and passes the parsed result to the webview. Validation warnings, auth failures, and timeouts are surfaced as VS Code notifications or Problems panel diagnostics.
-
-The **webview** (`src/webview/`) is a React 19 + Vite + Tailwind v4 app that receives the parsed bundle graph and renders it with `@xyflow/react`. Layout is computed with a topological level assignment and a row-packing heuristic so parallel branches stay visually separated.
-
-The bundle graph model lives in `src/bundle/graph/`. Issue building, semantic graph export, source location handling, target resolution, and task file detection live under `src/bundle/`.
-
-## Development
-
-```bash
-npm install
-npm run build          # builds the extension and the webview
-npm run watch:esbuild  # rebuild the extension on change
-npm run watch:tsc      # type-check the extension on change
-npm run verify         # unit tests, semantic baselines, typecheck, lint
-```
-
-Press `F5` in VS Code to launch an Extension Development Host with the extension loaded. Fixture bundles for tests and manual smoke checks live under `src/test/fixtures/`.
-
-## Testing
-
-The test suite is split by confidence layer:
-
-| Command | Purpose |
-| --- | --- |
-| `npm run test:unit` | Pure unit tests for parsers, graph extraction, issue building, documentation policy, and file-content detection. |
-| `npm run test:semantic` | Golden semantic graph baseline tests from committed Databricks CLI-shaped JSON fixtures. |
-| `npm run test:semantic:cli` | Live Databricks CLI compatibility check. Runs the configured CLI against a fixture and compares the resulting semantic graph to the committed baseline. |
-| `npm run test:semantic:cli:matrix` | Runs the live CLI compatibility check across the CLI/fixture pairs in `semantic-cli-matrix.config.json`. |
-| `npm run test` | Runs unit tests and semantic graph baselines. |
-| `npm run typecheck` | Runs TypeScript without emitting build output. |
-| `npm run lint` | Runs ESLint over `src`. |
-| `npm run verify` | Local pre-PR check: tests, semantic baselines, typecheck, and lint. |
-
-Semantic graph baselines intentionally use committed `validated-bundle.json`
-fixtures that represent `databricks bundle validate --output json` output. They
-do not parse raw YAML directly and normal tests do not overwrite fixture files.
-
-To check a real Databricks CLI version without overwriting committed fixtures:
-
-```bash
-npm run test:semantic:cli
-```
-
-By default this runs `databricks` against
-`src/test/fixtures/secret-scope-example` and compares the resulting semantic
-graph with `src/test/fixtures/baselines/secret-scope-example.semantic.json`.
-Use environment variables to point it at another CLI or fixture:
-
-```bash
-SEMANTIC_CLI_COMMAND=/usr/local/bin/databricks \
-SEMANTIC_CLI_FIXTURE=src/test/fixtures/secret-scope-example \
-SEMANTIC_CLI_BASELINE=src/test/fixtures/baselines/secret-scope-example.semantic.json \
-npm run test:semantic:cli
-```
-
-Live CLI artifacts are written under `.test-artifacts/semantic-cli/` for
-inspection and are ignored by git. This command is intentionally not part of
-`npm run verify` because it depends on an external CLI installation and local
-Databricks environment behavior.
-
-To run the compatibility check across multiple CLI commands and fixtures:
-
-```bash
-npm run test:semantic:cli:matrix
-```
-
-The default matrix lives in `semantic-cli-matrix.config.json`. It is deliberately
-small so it works in a normal local environment. For broader compatibility
-testing, provide a separate config whose `clis` entries point at pinned
-Databricks CLI binaries, for example:
-
-```json
-{
-  "clis": [
-    { "name": "0.270.1", "command": "/opt/databricks-cli/0.270.1/databricks" },
-    { "name": "0.295.0", "command": "/opt/databricks-cli/0.295.0/databricks" },
-    { "name": "latest", "command": "/usr/local/bin/databricks" }
-  ],
-  "fixtures": [
-    {
-      "name": "secret-scope-example",
-      "fixture": "src/test/fixtures/secret-scope-example",
-      "baseline": "src/test/fixtures/baselines/secret-scope-example.semantic.json"
-    }
-  ]
-}
-```
-
-Run it with:
-
-```bash
-npm run test:semantic:cli:matrix -- --config path/to/matrix.json
-```
-
-The intended compatibility floor for v0 is Databricks CLI `v0.270.1+`, but broad
-compatibility claims should be tied to the fixture suite covered by this matrix.
-
-To install a local matrix of pinned Databricks CLI binaries from GitHub releases:
-
-```bash
-npm run cli:install-matrix -- --min 0.270.1
-```
-
-This installs every Databricks CLI release at or above the minimum into
-`.tools/databricks-cli/` and writes `semantic-cli-matrix.local.json`. Then run:
-
-```bash
-npm run test:semantic:cli:matrix -- --config semantic-cli-matrix.local.json
-```
-
-For a faster smoke matrix, use:
-
-```bash
-npm run cli:install-matrix -- --min 0.270.1 --strategy latest-patch-per-minor
-```
-
-The smoke strategy is useful for quick local checks, but it should not be used
-as the compatibility claim for v0.
-
-To intentionally refresh a validated bundle fixture and its provenance metadata:
-
-```bash
-npm run fixtures:update:validated-bundle -- \
-  --fixture src/test/fixtures/secret-scope-example \
-  --cli databricks
-```
-
-This command writes both `validated-bundle.json` and
-`validated-bundle.meta.json`. The metadata includes the CLI version, generation
-timestamp, target, and a canonical SHA-256 of the JSON payload so formatting-only
-changes do not invalidate provenance.
-
-## Dev Container
-
-The repository includes a VS Code dev container for repeatable local checks. It
-uses Node 22, installs project dependencies with `npm ci`, and installs the
-Databricks CLI inside the container.
-
-Recommended workflow:
-
-1. Open the repository in VS Code.
-2. Run **Dev Containers: Reopen in Container**.
-3. Run deterministic checks:
-
-   ```bash
-   npm run verify
-   ```
-
-4. Run the live CLI semantic compatibility check inside the container:
-
-   ```bash
-   npm run test:semantic:cli
-   ```
-
-The dev container sets `databricksBundleInspector.cliPath` to
-`/usr/local/bin/databricks` for extension development hosts launched from the
-container.
-
-## Release process
-
-Releases are tag-driven. After merging a release PR with `package.json`,
-`package-lock.json`, `CHANGELOG.md`, and `README.md` ready for the target
-version, create and push a matching version tag:
-
-```bash
-git tag v0.1.0
-git push origin v0.1.0
-```
-
-The release workflow verifies, builds, packages a VSIX, writes a SHA-256
-checksum, verifies that checksum, and publishes both files to a GitHub Release.
-The Marketplace publish job then waits for approval on the `vscode-marketplace`
-GitHub Environment. After approval, it downloads the same VSIX artifact, verifies
-the checksum again, and publishes that exact package to the VS Code Marketplace.
-
-Maintainers need to configure the `vscode-marketplace` environment in GitHub
-with required reviewers and a `VSCE_PAT` environment secret. The token must be an
-Azure DevOps Personal Access Token with Marketplace Manage scope for the
-`UncoverTheStack` publisher.
+The extension runs `databricks bundle validate --output json` to resolve your bundle structure, builds a dependency graph from the jobs and their `depends_on` relationships, and renders it as an interactive visual DAG using React Flow.
 
 ## Project status
 
-Version 0.1.0. Active development. Feedback, bug reports, and feature requests are welcome on the [issue tracker](https://github.com/uncoverthestack/databricks-bundle-inspector/issues).
+Version 0.1.1. Active development. Feedback, bug reports, and feature requests are welcome on the [issue tracker](https://github.com/uncoverthestack/databricks-bundle-inspector/issues).
 
 ## License
 
diff --git a/package.json b/package.json
@@ -2,7 +2,7 @@
   "name": "databricks-bundle-inspector",
   "displayName": "Databricks Bundle Inspector",
   "description": "Inspect and visualize Databricks bundle structure",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "publisher": "UncoverTheStack",
   "icon": "resources/dark/logo.png",
   "license": "Apache-2.0",
diff --git a/src/webview/components/AppHeader.jsx b/src/webview/components/AppHeader.jsx
@@ -31,38 +31,12 @@ export default function AppHeader({
       <span className="truncate text-sm font-semibold text-stone-200">
         {bundleName ?? "Bundle Inspector"}
       </span>
-      {targetOptions.length > 0 ? (
-        <select
-          title={targetTitle}
-          value={selectedTarget ?? ""}
-          onChange={(e) => onTargetChange(e.target.value || undefined)}
-          className={[
-            "hidden cursor-pointer rounded-md border px-2 py-1 text-xs outline-none focus:border-blue-400 md:block",
-            targetMode === "probe"
-              ? "border-yellow-500/30 bg-yellow-500/10 text-yellow-300"
-              : "border-stone-700 bg-stone-900 text-stone-300",
-          ].join(" ")}
-        >
-          <option value="">structural preview</option>
-          {targetOptions.map((target) => (
-            <option key={target} value={target}>
-              target: {target}
-            </option>
-          ))}
-        </select>
-      ) : (
-        <span
-          title={targetTitle}
-          className={[
-            "hidden shrink-0 rounded-md border px-2 py-0.5 text-[11px] md:inline-flex",
-            targetMode === "probe"
-              ? "border-yellow-500/25 bg-yellow-500/10 text-yellow-300"
-              : "border-stone-800 bg-stone-900/70 text-stone-400",
-          ].join(" ")}
-        >
-          {targetLabel}
-        </span>
-      )}
+      <span
+        title={targetTitle}
+        className="hidden shrink-0 rounded-md border border-stone-800 bg-stone-900/70 px-2 py-0.5 text-[11px] text-stone-400 md:inline-flex"
+      >
+        structural preview
+      </span>
       {jobKeys.length > 0 && <span className="text-xs text-stone-700">·</span>}
       {jobKeys.length > 1 ? (
         <select
