Fallout-build · ChrisonSimtian · Sep 9, 2026 · Sep 9, 2026 · Sep 9, 2026 · Sep 9, 2026
diff --git a/.assets/screenshots/README.md b/.assets/screenshots/README.md
@@ -0,0 +1,24 @@
+# Screenshots
+
+README and marketplace imagery. Kept here rather than in `media/` because `media/`
+ships inside the `.vsix` (the extension icon lives there) and these do not —
+`.assets/**` is `.vscodeignore`d.
+
+README links these with **absolute** `raw.githubusercontent.com` URLs pinned to
+`develop`. Verified: `vsce` passes absolute URLs through unchanged, while it
+rewrites relative ones to a base that is not guaranteed to match this repo's
+default branch.
+
+| File | Used for |
+|---|---|
+| `overview.png` | Hero. Explorer file tree, the Fallout Build dock, and the graph in one frame. |
+| `targets-and-source.png` | Build view — the `DependsOn` chain in the tree beside the C# that declares it. |
+| `run-configuration.png` | Run Configuration — a parameter and a secret, with the keychain note visible. |
+| `run-a-target.png` | Run a target — ▶ from the tree, ending on Fallout's green summary table. |
+
+## Capturing
+
+Extension Development Host (<kbd>F5</kbd>) with this repository open — it builds with
+Fallout, so the graph is already populated. Dark theme, to match the banner. Crop to
+the panel plus a little context; roughly 1000–1400px wide reads best, and a 2× retina
+capture scaled down is sharpest.
diff --git a/.assets/screenshots/overview.png b/.assets/screenshots/overview.png
diff --git a/.assets/screenshots/run-a-target.png b/.assets/screenshots/run-a-target.png
diff --git a/.assets/screenshots/run-configuration.png b/.assets/screenshots/run-configuration.png
diff --git a/.assets/screenshots/targets-and-source.png b/.assets/screenshots/targets-and-source.png
diff --git a/README.md b/README.md
@@ -2,21 +2,66 @@
 
 Explore, run, and visualize your [Fallout](https://github.com/Fallout-build/Fallout) (the NUKE successor) build targets without leaving the editor.
 
+Your build is a C# console app. This makes it feel like part of the IDE: every target listed, one click to run, go-to-definition onto the `Target X => …` declaration, and the whole dependency graph as a diagram.
+
+![The Fallout Build view docked in the Explorer, beside the build graph](https://raw.githubusercontent.com/Fallout-build/Fallout.Extensions.VSCode/develop/.assets/screenshots/overview.png)
+
 ## Features
 
-- **Targets view** — a dedicated Fallout container in the activity bar lists every build target, with the default target and each target's relations (`depends on`, `runs after`, `triggered by`, `triggers`) as expandable children.
-- **Run a target** — inline ▶ on any target runs it in an integrated terminal (`./build.ps1` on Windows, `./build.sh` elsewhere).
-- **Go to definition** — jump straight to the `Target X => ...` C# declaration; disambiguated by declaring type when several components declare the same name.
-- **Build graph** — a Mermaid diagram of the whole dependency graph; click a node to run that target.
-- Auto-refreshes as the build graph changes.
+### Build view
+
+A dedicated Fallout container in the activity bar lists every target in the build. The default target is marked, unlisted targets are dimmed, and each target's relations — `depends on`, `runs after`, `triggered by`, `triggers` — expand as children, recursively, so you can walk the graph in either direction.
+
+The same tree is also docked in the **Explorer**, collapsed by default, for when you don't want to leave the file tree.
+
+![Targets expanded to show their dependencies, beside the C# that declares them](https://raw.githubusercontent.com/Fallout-build/Fallout.Extensions.VSCode/develop/.assets/screenshots/targets-and-source.png)
+
+The tree is a view of your C#: expanding `PackVsix` shows the `DependsOn` chain exactly as the build declares it.
+
+### Run a target
+
+Inline ▶ on any target runs it in an integrated terminal — `./build.ps1` on Windows, `./build.sh` elsewhere. **Run Target with Parameters…** runs the same target with your saved run configuration applied.
+
+![Running PackVsix from the tree, with Fallout's summary table in the terminal](https://raw.githubusercontent.com/Fallout-build/Fallout.Extensions.VSCode/develop/.assets/screenshots/run-a-target.png)
+
+### Run Configuration
+
+A form for the parameters and secrets your build takes:
+
+- **Parameters** are passed as `--name value` arguments and stored per workspace.
+- **Secrets** are stored in VS Code's [SecretStorage](https://code.visualstudio.com/api/references/vscode-api#SecretStorage) — OS keychain-backed — and passed as **environment variables**, so they never reach your shell history, the process list, or a log. Values are never rendered back into the view; only names are.
+
+![The Run Configuration view with a parameter and a secret](https://raw.githubusercontent.com/Fallout-build/Fallout.Extensions.VSCode/develop/.assets/screenshots/run-configuration.png)
+
+### Go to definition
+
+Jump straight to the `Target X => …` C# declaration. Uses the C# language service when it's warmed up and falls back to a workspace scan, and disambiguates by declaring type when several components declare a target of the same name.
+
+### Build graph
+
+A Mermaid diagram of the whole dependency graph, with the same edge semantics as the framework's own `--plan` output — solid for an execution dependency, dashed for an order dependency, thick for a trigger. Click any node to run that target.
+
+Everything auto-refreshes as the build graph changes, so a target you add shows up as soon as the build re-runs.
 
 ## Requirements
 
-**Fallout 10.4.0 or later.** The extension reads a `build-graph.json` that the Fallout build writes into `.fallout/temp/` (or the legacy `.nuke/temp/`) on every build initialization — the emission landed in 10.4.0, so older framework versions produce no graph at all. Run the build once (e.g. `./build.ps1 --plan`) to generate it.
+**Fallout 10.4.0 or later.** The extension reads a `build-graph.json` that the Fallout build writes into `.fallout/temp/` (or the legacy `.nuke/temp/`) on every build initialization. Emission landed in 10.4.0, so older versions produce no graph at all and the views stay empty.
+
+Run the build once to generate it:
+
+```bash
+./build.sh --plan      # ./build.ps1 --plan on Windows
+```
+
+## Settings
+
+| Setting | Default | What it does |
+|---|---|---|
+| `fallout.deployment.enabled` | `false` | Shows the **Deployment** view. Off by default — the continuous-delivery graph isn't emitted by any released Fallout version yet, so the view can only show a placeholder. Turn it on to follow the work. |
 
 ## Versioning
 
-The extension's `major.minor` track the Fallout framework release line it targets — 10.4.x builds against Fallout 10.4 — while the patch moves independently. A mismatch between the extension and the framework your workspace builds with surfaces as a non-blocking warning.
+The extension's `major.minor` track the Fallout release line it targets — 10.4.x builds against Fallout 10.4 — while the patch moves independently. A mismatch between the extension and the framework your workspace builds with surfaces as a non-blocking warning.
 
 Versions are computed by [Nerdbank.GitVersioning](https://github.com/dotnet/Nerdbank.GitVersioning) from `version.json`, the same as the framework itself; the build fails if the declared line drifts from the Fallout version it actually references. Release candidates are published as GitHub pre-releases only.
 

diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -6,6 +6,10 @@
     "publisher": "fallout",
     "license": "MIT",
     "icon": "media/icon.png",
+    "galleryBanner": {
+        "color": "#0d0d0f",
+        "theme": "dark"
+    },
     "engines": {
         "vscode": "^1.85.0"
     },
@@ -59,7 +63,8 @@
                     "id": "fallout.deployment",
                     "name": "Deployment",
                     "icon": "media/fallout.svg",
-                    "contextualTitle": "Fallout"
+                    "contextualTitle": "Fallout",
+                    "when": "config.fallout.deployment.enabled"
                 },
                 {
                     "id": "fallout.runConfig",
@@ -79,6 +84,16 @@
                 }
             ]
         },
+        "configuration": {
+            "title": "Fallout",
+            "properties": {
+                "fallout.deployment.enabled": {
+                    "type": "boolean",
+                    "default": false,
+                    "markdownDescription": "Show the **Deployment** view. Off by default: the continuous-delivery graph (channels \u2192 environments \u2192 targets) is not emitted by any released Fallout version yet, so the view can only show its placeholder. Turn it on to follow the work."
+                }
+            }
+        },
         "viewsWelcome": [
             {
                 "view": "fallout.build",
@@ -90,7 +105,7 @@
             },
             {
                 "view": "fallout.deployment",
-                "contents": "No deployment graph yet.\nThe continuous-delivery model (channels → environments → targets) is emitted by a later Fallout build (ADR-0009). This view lights up once the framework writes a `deployment-graph.json`."
+                "contents": "No deployment graph yet.\nThe continuous-delivery model (channels \u2192 environments \u2192 targets) is emitted by a later Fallout build (ADR-0009). This view lights up once the framework writes a `deployment-graph.json`."
             }
         ],
         "commands": [
@@ -108,7 +123,7 @@
             },
             {
                 "command": "fallout.runTargetWithParameters",
-                "title": "Run Target with Parameters…",
+                "title": "Run Target with Parameters\u2026",
                 "category": "Fallout",
                 "icon": "$(run-all)"
             },