diff --git a/.assets/fallout-social-preview.png b/.assets/fallout-social-preview.png
new file mode 100644
index 0000000..7894354
Binary files /dev/null and b/.assets/fallout-social-preview.png differ
diff --git a/.assets/fallout-social-preview.svg b/.assets/fallout-social-preview.svg
new file mode 100644
index 0000000..694c8b6
--- /dev/null
+++ b/.assets/fallout-social-preview.svg
@@ -0,0 +1,45 @@
+
diff --git a/.assets/screenshots/README.md b/.assets/screenshots/README.md
new file mode 100644
index 0000000..90d4a48
--- /dev/null
+++ 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 (F5) 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
new file mode 100644
index 0000000..b4586fb
Binary files /dev/null and b/.assets/screenshots/overview.png differ
diff --git a/.assets/screenshots/run-a-target.png b/.assets/screenshots/run-a-target.png
new file mode 100644
index 0000000..c6b7409
Binary files /dev/null and b/.assets/screenshots/run-a-target.png differ
diff --git a/.assets/screenshots/run-configuration.png b/.assets/screenshots/run-configuration.png
new file mode 100644
index 0000000..ac912ce
Binary files /dev/null and b/.assets/screenshots/run-configuration.png differ
diff --git a/.assets/screenshots/targets-and-source.png b/.assets/screenshots/targets-and-source.png
new file mode 100644
index 0000000..94563df
Binary files /dev/null and b/.assets/screenshots/targets-and-source.png differ
diff --git a/.claude/agents/story-writer.md b/.claude/agents/story-writer.md
new file mode 100644
index 0000000..0641140
--- /dev/null
+++ b/.claude/agents/story-writer.md
@@ -0,0 +1,42 @@
+---
+name: story-writer
+description: Drafts GitHub issues and user stories for this repo — terse, outcome-focused, and to the canonical shape. Use when asked to create, write, or file an issue/story.
+tools: Read, Grep, Glob, Bash
+model: sonnet
+---
+
+You write GitHub issues and user stories for the Fallout VS Code extension repo.
+Your output is the issue body itself, not a conversation about it.
+
+**Before writing**, read `docs/issue-and-pr-style.md` — it is the binding style
+contract. Follow it exactly.
+
+Defaults:
+
+- Use the **Problem → Outcome → Acceptance criteria** shape. Drop any section
+ that doesn't apply rather than padding it.
+- Be terse. Lead with the point. No preamble, no restating the title, no
+ hedging, no marketing tone, no emoji headers. Match length to substance.
+- Prefer linking (`#123`, `src/model.ts:64`) over pasting.
+- Outcomes describe observable behaviour, not implementation.
+
+Scope check before you write: this repo is the **extension**, not the framework.
+Anything about target execution, the build engine, or how `build-graph.json` is
+*produced* belongs in [Fallout-build/Fallout](https://github.com/Fallout-build/Fallout).
+This repo owns how that graph is *displayed and driven* from VS Code. Say so
+rather than filing it in the wrong place.
+
+For bugs, the report is not actionable without three versions — VS Code,
+extension, and Fallout. The extension needs **Fallout 10.4.0+**; below that no
+`build-graph.json` is emitted at all, which accounts for most "empty view"
+reports. Rule that out before writing it up as an extension bug.
+
+When the request is underspecified, ask at most 1–2 sharp questions, then write.
+Do not invent acceptance criteria the user didn't imply — leave a `- [ ]` stub
+if unknown.
+
+If asked to file it, run `gh issue create` with `--title` and a `--body` that
+matches the shape. Apply exactly one category label — `enhancement` for stories
+unless told otherwise; the taxonomy is in `.github/release.yml`. This repo has
+no `target/YYYY` labels; that is a framework-repo convention. Report the created
+issue URL and nothing else.
diff --git a/.claude/commands/new-issue.md b/.claude/commands/new-issue.md
new file mode 100644
index 0000000..3d95db6
--- /dev/null
+++ b/.claude/commands/new-issue.md
@@ -0,0 +1,40 @@
+---
+description: Draft (and optionally file) a terse, outcome-focused GitHub issue to the repo's canonical shape.
+argument-hint:
+allowed-tools: Read, Bash(gh issue create:*), Bash(gh label list:*)
+---
+
+Read `docs/issue-and-pr-style.md` and follow it as the binding style contract.
+Then draft a GitHub issue for: **$ARGUMENTS**
+
+Assemble the body to the canonical shape:
+
+```markdown
+### Problem
+<1–2 sentences>
+
+### Outcome
+
+
+### Acceptance criteria
+- [ ]
+- [ ]
+```
+
+Rules:
+
+- Terse. Lead with the point. No preamble, no restating the title, no filler.
+- Drop `Acceptance criteria` (and add a short `### Notes`) only if it doesn't
+ fit the ask. Don't invent criteria — leave `- [ ]` stubs if unknown.
+- Prefer links (`#123`, `src/model.ts:64`) over pasted blocks.
+- For a bug, include the three versions that make a report actionable here:
+ VS Code, extension, and Fallout. Most "the view is empty" reports are a
+ pre-10.4.0 framework emitting no `build-graph.json` at all — rule that out
+ before writing it up as an extension bug.
+
+Show me the drafted title and body first. **Do not file it until I confirm.**
+On confirmation, run `gh issue create --title "…" --body "…"` with exactly one
+category label (`enhancement`, `bug`, `breaking-change`, `security`,
+`documentation`, `dependencies`) — the taxonomy in `.github/release.yml`. This
+repo has no `target/YYYY` labels; that is a framework-repo convention. Report
+only the resulting issue URL.
diff --git a/.claude/settings.json b/.claude/settings.json
new file mode 100644
index 0000000..e990227
--- /dev/null
+++ b/.claude/settings.json
@@ -0,0 +1,16 @@
+{
+ "$schema": "https://json.schemastore.org/claude-code-settings.json",
+ "permissions": {
+ "allow": [
+ "Bash(dotnet:*)",
+ "Bash(./build.ps1:*)",
+ "Bash(./build.sh:*)",
+ "Bash(pwsh:*)",
+ "Bash(npm:*)",
+ "Bash(npx:*)",
+ "Bash(node:*)",
+ "Bash(git:*)",
+ "Bash(gh:*)"
+ ]
+ }
+}
diff --git a/.claude/skills/restructure-pr-commits/SKILL.md b/.claude/skills/restructure-pr-commits/SKILL.md
new file mode 100644
index 0000000..ce942f9
--- /dev/null
+++ b/.claude/skills/restructure-pr-commits/SKILL.md
@@ -0,0 +1,112 @@
+---
+name: restructure-pr-commits
+description: "Restructure the commits on an existing PR into focused, reviewable commits"
+---
+
+Restructure the commits on PR `` into focused, reviewable commits.
+Follow these steps in order exactly.
+
+## 0 — Check this is worth doing at all
+
+```
+gh pr view --json baseRefName,title,url
+```
+
+**The base branch decides whether commit curation matters.** This repo enforces
+linear history with merge commits disabled, and the merge method differs by
+direction (`docs/branching-and-release.md#merging`):
+
+- **Base `main`** — merged with **rebase**. Every commit lands on the production
+ branch verbatim and becomes a permanent `git bisect` target. Curation matters;
+ proceed.
+- **Base `develop`** — merged with **squash**. The whole PR collapses to one
+ commit no matter how you arrange it. Restructuring is wasted effort — the
+ thing that actually needs care is the **PR title**, since that is what lands
+ on the trunk and what the release notes quote. Say so and stop, unless the
+ user explicitly wants the branch history tidied anyway.
+
+Use the real base ref from that command as `` below — do not assume.
+
+## 1 — Find what the PR actually changes
+
+```
+git diff origin/ HEAD --stat
+```
+
+This is the authoritative list of files the PR modifies. `git log` is misleading
+on branches kept up to date via merge: merge commits drag base-branch history
+into the log as if it were authored on this branch — it isn't.
+
+## 2 — Find the branch's own commits
+
+```
+git log --first-parent --no-merges origin/..HEAD --oneline
+```
+
+This shows only commits made directly on this branch.
+
+## 3 — Create a backup branch
+
+```
+git branch backup-pr- HEAD
+```
+
+Do this before changing anything. Never skip this step.
+
+## 4 — Build the restructured history
+
+Check out a fresh branch from the base:
+```
+git checkout origin/ -b restructured-pr-
+```
+
+Then restore the changed files from the backup:
+```
+git checkout backup-pr- --
+```
+
+Handle renames explicitly: `git rm ` then `git checkout backup-pr- -- `.
+
+Commit in logical groups — one concern per commit. Commit message rules (from
+`docs/issue-and-pr-style.md`):
+- Functional imperative phrases; no conventional-commit prefixes (`fix:`, `feat:`, etc.)
+- Subject completes "This commit will…" without saying so
+- Body (when needed) explains *why*, not *what*; no file/class/type names
+
+Do not restructure across the generated/hand-written CI boundary: a change to
+`build/Build.CI.GitHubActions.cs` and the regenerated `.github/workflows/build.yml`
+belong in the **same** commit. Splitting them leaves a commit where the attribute
+and the workflow disagree, which is exactly the state the generated-file rule
+exists to prevent.
+
+## 5 — Verify file content is unchanged
+
+Run both and report the output:
+```
+git diff HEAD backup-pr-
+git diff HEAD origin/ --stat
+```
+
+The first command must produce **no output**; if it does, stop and investigate before continuing.
+The second must list **exactly the same files** as step 1.
+
+## 6 — Stop and wait for explicit confirmation
+
+Show the new `git log --oneline` and ask the user to confirm the history looks
+correct. Do not proceed until the user explicitly says yes.
+
+## 7 — Push with --force-with-lease only after confirmation
+
+```
+git push origin HEAD: --force-with-lease
+```
+
+Never use `--force` alone.
+
+## 8 — Update the PR title and description after confirmation
+
+Rewrite the PR title and description to match the restructured commits.
+Structure: Summary → one Changes section per commit → optional Combined effect.
+Each Changes section maps 1-to-1 to a commit. Keep the one category label
+correct — it is the changelog (`.github/release.yml`), and the title is the
+release-note line.
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 0000000..d41712c
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,111 @@
+name: 🐞 Bug Report
+description: "Report something that doesn't look alright."
+labels: ["bug", "needs-triage"]
+body:
+ - type: markdown
+ attributes:
+ value: |
+ _Hi there :wave: and thanks for taking the time to report a bug!_
+
+ _Before you continue, please check the [contribution guidelines](https://github.com/Fallout-build/Fallout.Extensions.VSCode/blob/develop/CONTRIBUTING.md)._
+
+ - type: markdown
+ attributes:
+ value: |
+ **Empty Targets view?** Check two things first — they account for most reports:
+ 1. Your workspace builds with **Fallout 10.4.0 or later**. Earlier versions emit no build graph at all.
+ 2. `.fallout/temp/build-graph.json` exists. Run `./build.ps1 --plan` once to generate it.
+
+ - type: input
+ id: usage-information
+ attributes:
+ label: Usage Information
+ description: Extension version / Fallout version / VS Code version / Operating System
+ placeholder: 10.4.30 / Fallout 10.4.0 / VS Code 1.96.2 / macOS 15.2
+ validations:
+ required: true
+
+ - type: textarea
+ id: description
+ attributes:
+ label: Description
+ description: Please share a clear and concise description of the problem.
+ placeholder: Description
+ validations:
+ required: true
+
+ - type: textarea
+ id: reproduction-steps
+ attributes:
+ label: Reproduction Steps
+ description: |
+ Minimal steps to reproduce. Include logs and exceptions as text rather than screenshots — except for genuinely visual problems (graph layout, tree icons, theme contrast), where a screenshot is the clearest evidence.
+ placeholder: Minimal Reproduction
+ validations:
+ required: true
+
+ - type: textarea
+ id: expected-behavior
+ attributes:
+ label: Expected Behavior
+ placeholder: Expected Behavior
+ validations:
+ required: true
+
+ - type: textarea
+ id: actual-behavior
+ attributes:
+ label: Actual Behavior
+ description: If applicable, include error messages or stack traces.
+ placeholder: Actual Behavior
+ validations:
+ required: true
+
+ - type: textarea
+ id: build-graph
+ attributes:
+ label: Build graph
+ description: |
+ For anything about which targets appear, how they relate, or how the graph renders: paste the relevant slice of `.fallout/temp/build-graph.json`. Trim it to the targets involved — the whole file is rarely needed.
+ render: json
+ validations:
+ required: false
+
+ - type: textarea
+ id: extension-log
+ attributes:
+ label: Extension log
+ description: |
+ Optional. **Output** panel → select **Fallout** or **Log (Extension Host)** from the dropdown. Errors thrown during activation land there.
+ render: shell
+ validations:
+ required: false
+
+ - type: textarea
+ id: regression
+ attributes:
+ label: Regression?
+ description: |
+ Did this work in a previous version of the extension? If you can try an earlier one, that helps narrow it down. If you don't know, that's OK.
+ placeholder: Regression?
+ validations:
+ required: false
+
+ - type: textarea
+ id: known-workarounds
+ attributes:
+ label: Known Workarounds
+ placeholder: Known Workarounds
+ validations:
+ required: false
+
+ - type: dropdown
+ id: pull-request
+ attributes:
+ label: Could you help with a pull-request?
+ description: See the [contribution guidelines](https://github.com/Fallout-build/Fallout.Extensions.VSCode/blob/develop/CONTRIBUTING.md).
+ options:
+ - "No"
+ - "Yes"
+ validations:
+ required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 0000000..768ee60
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,14 @@
+blank_issues_enabled: false
+contact_links:
+ - name: 🔒 Security vulnerability
+ url: https://github.com/Fallout-build/.github/blob/main/SECURITY.md
+ about: Don't file these as issues. Report privately via this repo's Security tab.
+ - name: 🧩 Fallout framework issues
+ url: https://github.com/Fallout-build/Fallout/issues
+ about: Build engine, targets, or how build-graph.json is produced — that's the framework, not this extension.
+ - name: 📚 Contributing & release docs
+ url: https://github.com/Fallout-build/Fallout.Extensions.VSCode/blob/develop/CONTRIBUTING.md
+ about: Branching, PR labels, and how this extension is built and released.
+ - name: 🧪 Nightly build
+ url: https://github.com/Fallout-build/Fallout.Extensions.VSCode/releases/tag/nightly
+ about: Every push to develop publishes a rolling pre-release .vsix. Worth checking your issue isn't already fixed there.
diff --git a/.github/ISSUE_TEMPLATE/feature_idea.yml b/.github/ISSUE_TEMPLATE/feature_idea.yml
new file mode 100644
index 0000000..c41c38a
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_idea.yml
@@ -0,0 +1,53 @@
+name: 💡 Feature Idea
+description: "Suggest new features for the extension."
+labels: ["enhancement", "needs-triage"]
+body:
+ - type: markdown
+ attributes:
+ value: |
+ _Hi there :wave: and thanks for taking the time to send a feature idea!_
+
+ _Before you continue, please check the [contribution guidelines](https://github.com/Fallout-build/Fallout.Extensions.VSCode/blob/develop/CONTRIBUTING.md)._
+
+ _This repo is the **VS Code extension**. Ideas about targets, the build engine, or how the build graph is produced belong in the [framework repo](https://github.com/Fallout-build/Fallout/issues)._
+
+ - type: textarea
+ attributes:
+ label: Description
+ description: What should the new feature do?
+ validations:
+ required: true
+
+ - type: textarea
+ attributes:
+ label: Usage Example
+ description: How would you use it — which view, command, or gesture?
+
+ - type: textarea
+ attributes:
+ label: Alternative
+ description: What do you do today instead?
+
+ - type: dropdown
+ id: needs-framework-change
+ attributes:
+ label: Does this need new data in build-graph.json?
+ description: |
+ If the extension would need information Fallout doesn't currently emit, this needs a framework change first and will be routed there. Pick "Not sure" if you don't know — that's fine.
+ options:
+ - "Not sure"
+ - "No — it works with what's already in the graph"
+ - "Yes — Fallout would need to emit something new"
+ validations:
+ required: true
+
+ - type: dropdown
+ id: pull-request
+ attributes:
+ label: Could you help with a pull-request?
+ description: See the [contribution guidelines](https://github.com/Fallout-build/Fallout.Extensions.VSCode/blob/develop/CONTRIBUTING.md).
+ options:
+ - "No"
+ - "Yes"
+ validations:
+ required: true
diff --git a/.github/ISSUE_TEMPLATE/user_story.yml b/.github/ISSUE_TEMPLATE/user_story.yml
new file mode 100644
index 0000000..1bf3e01
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/user_story.yml
@@ -0,0 +1,61 @@
+name: 📝 User Story
+description: "Describe a desired capability as a small, outcome-focused story."
+labels: ["enhancement", "needs-triage"]
+body:
+ - type: markdown
+ attributes:
+ value: |
+ _Keep it terse and scannable — Problem, Outcome, and how we'll know it's done. See [issue & PR style](https://github.com/Fallout-build/Fallout.Extensions.VSCode/blob/develop/docs/issue-and-pr-style.md)._
+
+ _Before you continue, please check the [contribution guidelines](https://github.com/Fallout-build/Fallout.Extensions.VSCode/blob/develop/CONTRIBUTING.md)._
+
+ - type: textarea
+ id: problem
+ attributes:
+ label: Problem
+ description: What's wrong or missing, and for whom? 1–2 sentences.
+ placeholder: Finding which target a failing build actually ran means reading the terminal scrollback — the Targets view doesn't show run state.
+ validations:
+ required: true
+
+ - type: textarea
+ id: outcome
+ attributes:
+ label: Outcome
+ description: What does "done" look like? Describe observable behaviour, not the implementation.
+ placeholder: A target that has run shows its last result in the tree, and clicking it reveals that run's output.
+ validations:
+ required: true
+
+ - type: textarea
+ id: acceptance-criteria
+ attributes:
+ label: Acceptance criteria
+ description: Testable checkboxes. Drop this section if the Outcome is self-evident.
+ placeholder: |
+ - [ ] A succeeded target is visually distinct from one that has never run
+ - [ ] State clears when the graph is regenerated
+ value: |
+ - [ ]
+ - [ ]
+ validations:
+ required: false
+
+ - type: textarea
+ id: notes
+ attributes:
+ label: Notes
+ description: Optional. Links, constraints, related issues (≤3 lines). Leave blank if none.
+ validations:
+ required: false
+
+ - type: dropdown
+ id: pull-request
+ attributes:
+ label: Could you help with a pull-request?
+ description: See the [contribution guidelines](https://github.com/Fallout-build/Fallout.Extensions.VSCode/blob/develop/CONTRIBUTING.md).
+ options:
+ - "No"
+ - "Yes"
+ validations:
+ required: true
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index d43304e..0fc9b4a 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -8,3 +8,8 @@
+
+
+
+
+
diff --git a/.github/workflows/preview.yml b/.github/workflows/nightly.yml
similarity index 78%
rename from .github/workflows/preview.yml
rename to .github/workflows/nightly.yml
index d6b8a3a..4966117 100644
--- a/.github/workflows/preview.yml
+++ b/.github/workflows/nightly.yml
@@ -1,38 +1,44 @@
-# Hand-written (not auto-generated). The "preview" channel — per-commit builds of develop.
+# Hand-written (not auto-generated). The "nightly" channel — per-commit builds of develop.
#
# Counterpart to the framework repo's publish-packages-preview.yml, which pushes a
# -preview prerelease to GitHub Packages on every commit to main. The extension can't
# do the same thing: GitHub Packages does not speak the VS Code gallery protocol, and
-# neither marketplace accepts a semver prerelease version. So the preview channel here
+# neither marketplace accepts a semver prerelease version. So the nightly channel here
# is a ROLLING GitHub pre-release whose asset is replaced on every push.
#
# Why a rolling release rather than workflow artifacts:
# - the download URL is stable, so installing is one command with no run-hunting:
#
-# gh release download preview -R Fallout-build/Fallout.Extensions.VSCode -p '*.vsix' --clobber
+# gh release download nightly -R Fallout-build/Fallout.Extensions.VSCode -p '*.vsix' --clobber
# code --install-extension fallout.vsix
#
-# or, from a clone: dotnet fallout InstallVsix
# - workflow artifacts expire and need the run ID to fetch.
#
-# The tag is `preview`, deliberately NOT matching `v*`. Two consequences, both wanted:
+# The tag is `nightly`, deliberately NOT matching `v*`. Two consequences, both wanted:
# publish.yml (which triggers on v* only) does not fire, and the v* tag-protection
# ruleset does not apply to a tag this workflow force-moves on every push.
#
+# It was `preview` until GitHub's immutable releases were briefly enabled on this repo.
+# An immutable release reserves its tag permanently: deleting the release and the tag
+# does not free the name, and recreating it fails with "creations being restricted".
+# `preview` is therefore unusable here forever. Immutability and a force-moved tag are
+# fundamentally incompatible — if it is ever re-enabled, this channel needs per-commit
+# tags instead of a rolling one, not another rename.
+#
# The .vsix is marked as a marketplace pre-release, so if it is ever sideloaded next to
# a stable build VS Code shows it as pre-release rather than silently as a release.
#
# See docs/ci.md for how this fits with the other workflows.
#
# NOTE: this publishes NOTHING to any marketplace. It is the GitHub pre-stage only.
-name: preview
+name: nightly
on:
push:
branches:
# develop is the integration trunk under GitFlow, so it is what "latest" means.
# main only ever receives release and hotfix merges, and those are tagged, so a
- # preview build of main would duplicate a release build of the same commit.
+ # nightly build of main would duplicate a release build of the same commit.
- develop
paths-ignore:
- '**/*.md'
@@ -44,18 +50,18 @@ permissions:
concurrency:
# Never cancel in progress: a cancelled run could leave the rolling release holding a
# half-uploaded asset. Queue instead, so the newest push wins by finishing last.
- group: preview
+ group: nightly
cancel-in-progress: false
jobs:
- preview:
- name: preview
+ nightly:
+ name: nightly
runs-on: ubuntu-latest
permissions:
contents: write
environment:
name: github-releases
- url: https://github.com/Fallout-build/Fallout.Extensions.VSCode/releases/tag/preview
+ url: https://github.com/Fallout-build/Fallout.Extensions.VSCode/releases/tag/nightly
steps:
- uses: actions/checkout@v7
with:
@@ -105,7 +111,7 @@ jobs:
echo "version=$VERSION" >> "$GITHUB_OUTPUT"
echo "Packaged version: $VERSION"
- - name: 'Update the rolling preview release'
+ - name: 'Update the rolling nightly release'
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
VERSION: ${{ steps.version.outputs.version }}
@@ -113,7 +119,7 @@ jobs:
set -euo pipefail
NOTES=$(cat < /dev/null 2>&1; then
- gh release edit preview --target "$GITHUB_SHA" --notes "$NOTES" --prerelease
- gh release upload preview fallout.vsix --clobber
+ if gh release view nightly > /dev/null 2>&1; then
+ gh release edit nightly --target "$GITHUB_SHA" --notes "$NOTES" --prerelease
+ gh release upload nightly fallout.vsix --clobber
else
- gh release create preview \
- --title 'Preview (rolling)' \
+ gh release create nightly \
+ --title 'Nightly (rolling)' \
--target "$GITHUB_SHA" \
--notes "$NOTES" \
--prerelease \
diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
index 861586f..9d35e93 100644
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -70,7 +70,7 @@ jobs:
set -euo pipefail
# Releases come from main (current line) or a support/vX.Y line (older Fallout
# line still being served). NOT develop: under GitFlow the trunk is never
- # tagged for release — it ships through the preview channel instead.
+ # tagged for release — it ships through the nightly channel instead.
REACHABLE=$(git branch -r --contains "${{ github.sha }}" \
| grep -E 'origin/(main|support/v[0-9]+\.[0-9]+)$' || true)
if [ -z "$REACHABLE" ]; then
diff --git a/.gitignore b/.gitignore
index a0343ba..2ba810b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -7,3 +7,19 @@ out/
.fallout/temp/
bin/
obj/
+
+# Local-only, by convention: anything named *.local.* is this-machine state and never
+# committed. Covers CLAUDE.local.md (personal agent directives), settings.local.json,
+# and any *.local.json/.xml a tool drops beside its shared counterpart. The shared
+# sibling — settings.json, AGENTS.md, CLAUDE.md — IS committed.
+*.local.*
+
+# Claude Code — local state the pattern above doesn't catch. Credentials especially:
+# these must never reach a public repo.
+.claude/.credentials*
+.claude/scheduled_tasks.lock
+.claude/worktrees/
+memory/
+
+# macOS
+.DS_Store
diff --git a/.vscode/launch.json b/.vscode/launch.json
new file mode 100644
index 0000000..9f3ea55
--- /dev/null
+++ b/.vscode/launch.json
@@ -0,0 +1,39 @@
+{
+ // F5 opens a second VS Code window (the Extension Development Host) with this
+ // extension loaded from source. See docs/developing.md.
+ "version": "0.2.0",
+ "configurations": [
+ {
+ "name": "Run Extension",
+ "type": "extensionHost",
+ "request": "launch",
+ "args": [
+ "--extensionDevelopmentPath=${workspaceFolder}",
+ // Open this repo as the test workspace: it builds with Fallout, so it
+ // already has a .fallout/temp/build-graph.json and the views populate
+ // immediately. Point this elsewhere to test against another build.
+ "${workspaceFolder}"
+ ],
+ "outFiles": [
+ "${workspaceFolder}/out/**/*.js"
+ ],
+ "preLaunchTask": "npm: compile"
+ },
+ {
+ // Same, with every other extension disabled. Use when something looks off
+ // and you need to rule out interference from your own installed extensions.
+ "name": "Run Extension (clean profile)",
+ "type": "extensionHost",
+ "request": "launch",
+ "args": [
+ "--extensionDevelopmentPath=${workspaceFolder}",
+ "--disable-extensions",
+ "${workspaceFolder}"
+ ],
+ "outFiles": [
+ "${workspaceFolder}/out/**/*.js"
+ ],
+ "preLaunchTask": "npm: compile"
+ }
+ ]
+}
diff --git a/.vscode/tasks.json b/.vscode/tasks.json
new file mode 100644
index 0000000..9b0863d
--- /dev/null
+++ b/.vscode/tasks.json
@@ -0,0 +1,24 @@
+{
+ "version": "2.0.0",
+ "tasks": [
+ {
+ // preLaunchTask for both launch configurations — F5 compiles before it launches,
+ // so the Extension Development Host never runs stale out/*.js.
+ "type": "npm",
+ "script": "compile",
+ "group": "build",
+ "problemMatcher": "$tsc",
+ "label": "npm: compile"
+ },
+ {
+ // Long-running alternative: leave this going and use "Reload Window" in the
+ // Extension Development Host instead of restarting the debug session.
+ "type": "npm",
+ "script": "watch",
+ "group": "build",
+ "isBackground": true,
+ "problemMatcher": "$tsc-watch",
+ "label": "npm: watch"
+ }
+ ]
+}
diff --git a/.vscodeignore b/.vscodeignore
index 9fe2cfb..c341b8e 100644
--- a/.vscodeignore
+++ b/.vscodeignore
@@ -1,6 +1,7 @@
.vscode/**
.vscode-test/**
.github/**
+.claude/**
src/**
out/**/*.map
**/*.ts
@@ -20,6 +21,11 @@ build.ps1
build.sh
# Maintainer-facing; the marketplace page renders README.md only.
docs/**
+AGENTS.md
+CLAUDE.md
+CONTRIBUTING.md
+# Repo branding (GitHub social preview), not extension assets — media/ holds those.
+.assets/**
# Ship only Mermaid's self-contained UMD bundle (loaded by the graph webview via a
# classic
+
+