dialog-ide 0.5.0

package/CHANGELOG.md

@@ -0,0 +1,69 @@
+# Changelog
+
+## 0.5.0 - 25 Aug 2026
+
+- Add `dgbuild`, a headless CLI (`test`, `run-skein`, `sources`) for running project checks from scripts/CI without the VS Code extension host
+
+## 0.4.1 - 22 Aug 2026
+
+- Fix `dialog.json`'s `binDir` being ignored when set to a relative path (e.g. `"bin"`) - it's now resolved against the project root like source entries, instead of the extension host's own working directory
+- Fix a script-load race that could break the Skein/Trace webview on startup ("sk is not defined") - each page now loads a single `skein-loader.js`/`trace-loader.js` entry point whose static imports guarantee `main.js`/`trace.js` finish before `datastar.js` runs, instead of relying on `<script>` tag order
+
+## 0.4.0 - 21 Aug 2026
+
+- Nav graph: zoom in/out via mouse wheel (centered on the cursor) or new bottom-right +/- buttons
+- Knots can carry one of four color markers (actions menu), shown next to the label chip and persisted in the .skein file; navbar filter buttons show only knots with a chosen marker (or a marked descendant)
+- Prompt to reload the active session's .skein file when it changes on disk outside Dialog IDE
+- "Export Web Page..."'s story-metadata query (title/author/IFID/etc.) now also respects `<name>.dgdebug.dg`/`<name>.<format>.dg` source-suffix filtering, matching every other dgdebug launch - a source meant only for a specific export format could previously leak into it
+
+## 0.3.0 - 19 Aug 2026
+
+- "Export Web Page..."'s attachments ("feelies", e.g. the "how to play IF" PDFs) are now configurable via `dialog.json`'s `feelies` array, instead of a hardcoded pair of filenames; "Add Feelie..." (also available via right-click in the Explorer) and "Remove Feelie..." commands manage them. A configured feelie whose file is missing is now an export error, not a silent omission
+- Command input (new commands and "Edit Command...") now lowercases and collapses consecutive whitespace, not just trims
+- "Edit Command..." and "Insert Parent..." no longer reject a command that collides with an existing sibling - the two knots merge instead (recursively, through matching descendants), keeping the merged knot locked/labeled if either side was
+- Warn when `dialog.json` declares the same source file in more than one category (or twice in one), since Dialog would compile it twice - new `dialog-ide.warnOnDuplicateSource` setting
+
+## 0.2.0 - 16 Aug 2026
+
+- Run the Skein using `frotz`/`frotz-release` (dfrotz) as the engine - requires `dfrotz` on `PATH` or `binDir` (not yet bundled)
+- "Initialize Dialog Project" no longer asks for target format(s); removed `dialog.json`'s `target` field
+- "Export Web Page..." now asks which export configuration builds the downloadable story file, instead of building every target
+- ⌘⇧A / Ctrl+Shift+A now opens the Command Palette while the Skein or Trace panel has focus
+- A labeled knot is now treated as locked (can't be deleted) even if never explicitly locked
+- Export commands' post-export notification now says "Reveal in Finder" on macOS instead of "Reveal in Explorer"
+- Fixed the nav graph's expand/collapse icon drifting off its connector line for a small/narrow skein
+
+## 0.1.0 - 15 Aug 2026
+
+- Bundle the Dialog toolchain (`dgdebug`/`dialogc`) and AAmachine (`aambundle`) with the extension on Windows, Apple Silicon Macs, and Linux (x64), so most users no longer need to install either separately; other platforms still resolve via `PATH` or `dialog.json`'s `binDir`, which always takes priority
+- "Initialize Dialog Project" command: scaffolds `dialog.json`, `main`/`lib`/`debug`/`test` directories, a starter `main/main.dg`, bundled copies of the standard libraries (`stdlib.dg`/`stddebug.dg`/`unit.dg`), a placeholder `cover.png`, and the two "how to play IF" PDFs used by "Export Web Page..." into an open, empty workspace folder
+- "Configure Exports..." and "Export Dialog Project..." commands: define named export configurations (output format, whether to include debug sources, output path, extra `dialogc` options such as `--heap`/`--aux`) in `dialog.json`, then compile a `.zblorb`/`.z8`/`.aa` game file via `dialogc`; a `zblorb` export bakes in the project's `cover.png`, if present. "Configure Exports..." also sets a project-wide default set of `dialogc` options, used by any export configuration that doesn't specify its own, and by "Export Web Page..."
+- "Export Web Page..." command: builds every one of the project's targets plus an AAmachine in-browser player, and assembles a downloadable web page (cover thumbnail, story file downloads, "how to play IF" PDFs, an optional walkthrough from `default.skein`) into `out/web/` plus a zip; deleting a PDF (or `cover.png`) from the project root simply omits it from the exported page rather than erroring
+- "Run Tests" command: runs `dgdebug` in a terminal with the `main`/`debug`/`test` source categories all active, so `test`'s own `lib/unit.dg` overrides `(program entry point)` and runs the project's `(test *)`-trait objects; dgdebug drops into its own debug prompt once the tests finish (rather than quitting immediately), so the pass/fail output stays visible; re-running the command replaces the previous run's terminal instead of opening a new tab each time
+
+## 0.0.2 - 13 Aug 2026
+
+- Rewrote `README.md` for end users (Dialog authors), covering the Skein workflow, keyboard shortcuts, and project setup
+- Moved developer-facing content (source layout, build/test/package workflow) into `technical-design.md`
+- Nav graph connectors now use an orthogonal elbow (vertical, then a sharp turn to horizontal, then a slightly curved turn back to vertical) instead of a bezier curve
+- Nav graph's expand/collapse control is now a larger boxed +/- icon instead of a small chevron, with an opaque interior so the connector line no longer bleeds through it
+- Outline view (and breadcrumbs, Ctrl+Shift+O) for `.dg` source files: topics as collapsible nodes, rule definitions nested underneath
+- Workspace-wide "Go to Symbol" (Ctrl+T/Cmd+T) across all `.dg` source files in a project, kept current via a file watcher as sources are edited/added/removed
+- Editing, adding, or deleting a project's `.dg` source files, or its `dialog.json`, now restarts the `dgdebug` process on the next command so changes take effect immediately
+- Warn when a newly created `.dg` file isn't covered by any `dialog.json` source: a dismissible notification plus a persistent Explorer badge, both with a one-click "Add to dialog.json" fix; configurable via `dialog-ide.warnOnUncoveredSource`
+- Vendored `.dg` syntax highlighting, folding, and bracket/indentation support directly into the extension (previously provided by the separate `sideburns3000.dialog-language-support` extension via `extensionDependencies`, which also brought along conflicting "Compile to Z8/etc." commands); that dependency has been dropped. If it's still separately installed, a one-time startup notice suggests disabling/uninstalling it
+- A custom `.dg` file icon (two overlapping speech bubbles) for icon themes that don't already provide one of their own
+
+## 0.0.1 - 11 Aug 2026
+
+Initial release.
+
+- Skein engine for the `dgdebug` interpreter: process management, session orchestration, tag-line prompt detection
+- Transcript and nav-graph webview UI, with full keyboard-first navigation
+- Bless/undo/redo, Replay and Replay All, time travel, Insert Parent, Splice Out, knot labels and locking
+- Dynamic state capture and diffing (`@dynamic`)
+- Trace panel with click-through to source
+- Full-text search over knot labels and responses
+- `.skein` file persistence, compatible with dialog-tool's flat-file format
+- `dialog.json` project support (source discovery/ordering)
+- VS Code extension packaging (`.vsix`), icon, and Apache-2.0 license

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the
+      purposes of this License, Derivative Works shall not include works
+      that remain separable from, or merely link (or bind by name) to the
+      interfaces of, the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including the
+      original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Howard Lewis Ship
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,211 @@
+# Dialog IDE
+
+Dialog IDE is a VS Code extension for developing interactive fiction in the [Dialog](https://github.com/dialog-if/dialog) programming language. Its centerpiece is the **Skein**: an interactive, web-style panel for running, testing, and debugging your project without leaving the editor.
+
+> [!NOTE]
+> Not every work of IF is a "game", so the Dialog tooling generally says "project" instead.
+
+## What the Skein does
+
+At its simplest, the Skein is a live wrapper around Dialog's own debugger (`dgdebug`): you type player commands, and the project's responses come back into the panel. What makes it powerful is that it *remembers*. Every command and response you've ever tried is kept in an ever-growing tree, so you can:
+
+- **Time travel** back to any earlier point and try a different command, without losing the path you already explored
+- **Bless** a response as correct, so you'll be warned if a later code change ever produces a different response
+- **Replay All** every path through your project in seconds, to confirm a change didn't break anything
+- **Trace** exactly which predicates fired for a given command, with clickable links to the source
+- Inspect the **dynamic state** (flags, relations, attributes) that changed as a result of a command
+
+Each command/response pair is called a **knot**. Knots form a tree - the same command can appear at multiple points in the tree, each with its own knot, because the same input can mean something different depending on what came before.
+
+## Requirements
+
+- On Windows, Apple Silicon Macs, and Linux (x64): nothing extra - the Dialog toolchain (`dgdebug`, `dialogc`) and [AAmachine](https://github.com/dialog-if/aamachine) (`aambundle`) are bundled with the extension and just work.
+- On other platforms (Intel Macs, Linux ARM, etc.): install the [Dialog toolchain](https://github.com/dialog-if/dialog) yourself, with `dgdebug`/`dialogc` on your `PATH`, or point `dialog.json`'s `binDir` at it (see [Project Setup](#project-setup)). **Export Web Page...** additionally needs `aambundle` from [AAmachine](https://github.com/dialog-if/aamachine) on your `PATH`/`binDir` - the other commands don't need it.
+- Running a skein with the `frotz`/`frotz-release` engine additionally needs `dfrotz` (from [frotz](https://gitlab.com/DavidGriffith/frotz)) on your `PATH`/`binDir`, on every platform - it isn't bundled yet.
+- A project folder containing a `dialog.json` file (see [Project Setup](#project-setup)) - or use **Dialog IDE: Initialize Dialog Project** to create one from scratch
+
+`.dg` syntax highlighting, folding, and bracket/indentation support are built in, along with an Outline view (and breadcrumbs, ⌘⇧O / Ctrl+Shift+O) and workspace-wide "Go to Symbol" (⌘T / Ctrl+T) across every `.dg` file in the project. Dialog IDE itself doesn't otherwise touch source editing; it's all about running the project through the Skein.
+
+> [!NOTE]
+> If you previously had the separate [`dialog-language-support`](https://marketplace.visualstudio.com/items?itemName=sideburns3000.dialog-language-support) extension installed, Dialog IDE will warn you once at startup and suggest disabling or uninstalling it - having both installed can cause inconsistent `.dg` highlighting and a duplicate "Compile to..." context menu.
+
+## Installing
+
+Search for **Dialog IDE** in the VS Code Extensions view and install it, or install from the command line:
+
+```bash
+code --install-extension hlship.dialog-ide
+```
+
+## Project Setup
+
+Dialog IDE reads a `dialog.json` file at the root of your project (opened as a VS Code workspace folder). This is what **Dialog IDE: Initialize Dialog Project** scaffolds:
+
+```json
+{
+  "name": "my-project",
+  "sources": {
+    "main": ["main"],
+    "test": ["test", "lib/unit.dg"],
+    "debug": ["debug", "lib/stddebug.dg"],
+    "library": ["lib/stdlib.dg"]
+  }
+}
+```
+
+- Each entry under `sources` is a list of directories (all `.dg` files in the directory) or individual file paths
+- `main` is always included; `debug` is pulled in for Skein/debug sessions; `library` (including the Dialog standard library) is always included; `test` is loaded by **Dialog IDE: Run Tests** (see [Getting Started](#getting-started)), but not by a running Skein session
+- Order is very important: main comes before test, which comes before debug, which comes before library.
+
+The order of sources in a single directory is not guaranteed; if order counts, you should list the files in the directory
+in the order you need them to be.  Remember that Dialog searches for rules top to bottom, so you should have 
+exceptions first, before default rules.
+
+A source file named `<name>.<format>.dg` is only included when building for that format - e.g. `colors.zblorb.dg` is
+included in a `zblorb` export but skipped everywhere else, and `layout.dgdebug.dg` is included only when running a
+Skein session, **Debug in Terminal**, or **Run Tests** (all of which run against `dgdebug`). This lets you fine-tune
+things like colors or layout per format without those tweaks leaking into other builds. A file with no such suffix
+(or one that doesn't match any format Dialog IDE builds for) is always included.
+
+If you create a `.dg` file that isn't covered by any of the categories above, Dialog IDE flags it - a dismissible notification plus a persistent Explorer badge, both with a one-click "Add to dialog.json" fix. Turn this off via the `dialog-ide.warnOnUncoveredSource` setting.
+
+Dialog IDE also flags a source file declared in more than one category (or twice in the same one) - since order matters, a duplicate isn't harmless, it's compiled twice. Turn this off via the `dialog-ide.warnOnDuplicateSource` setting.
+
+If you need a specific `dgdebug` (e.g. a locally built one, or a platform Dialog IDE doesn't bundle a toolchain for - see [Requirements](#requirements)), add a `binDir` field pointing at the directory containing it:
+
+```json
+{
+  "name": "my-project",
+  "binDir": "/opt/dialog/bin",
+  "sources": { "main": ["src"] }
+}
+```
+
+`binDir` always takes priority, overriding both Dialog IDE's bundled toolchain and anything found on `PATH`.
+
+## Getting Started
+
+Open your project folder in VS Code, then use the Command Palette (⌘⇧P / Ctrl+Shift+P) for:
+
+| Command | Effect |
+|---|---|
+| **Dialog IDE: Initialize Dialog Project** | Scaffold a new project into an empty folder: `dialog.json`, `main`/`lib`/`debug`/`test` directories, starter source, a placeholder `cover.png`, and the two "how to play IF" PDFs used by **Export Web Page...** |
+| **Dialog IDE: New Skein...** | Create a new `.skein` file (prompts for a random seed and file name) |
+| **Dialog IDE: Run Default Skein** | Run `default.skein` if one already exists |
+| **Dialog IDE: Run Skein...** | Pick from any existing `.skein` file in the project |
+| **Dialog IDE: Open Skein** | Reveal the Skein panel for whatever session is currently running |
+| **Dialog IDE: Save Skein** | Save the current session's tree back to its `.skein` file |
+| **Dialog IDE: Stop Skein** | Stop the running session |
+| **Dialog IDE: Debug in Terminal** | Open a plain, unmanaged `dgdebug` session in a VS Code terminal |
+| **Dialog IDE: Run Tests** | Run the project's unit tests (the `test` source category) in a VS Code terminal |
+| **Dialog IDE: Add File to dialog.json...** | Add the current (or a picked) `.dg` file to one of dialog.json's source categories |
+| **Dialog IDE: Configure Exports...** | Define named export configurations, and the project's default `dialogc` options (see [Building & Exporting](#building--exporting)) |
+| **Dialog IDE: Export Dialog Project...** | Compile one of those export configurations |
+| **Dialog IDE: Export Web Page...** | Build a downloadable web page for the project, with an in-browser player |
+| **Dialog IDE: Add Feelie...** | Add an attachment (e.g. a PDF) that **Export Web Page...** links from the page |
+| **Dialog IDE: Remove Feelie...** | Remove a previously added feelie |
+
+A status bar item on the left also shows the current session (or lets you start the default one with a click).
+
+**Dialog IDE: Run Tests** compiles with the `main`, `debug`, and `test` categories all active and runs `dgdebug` in a terminal - `test`'s own `lib/unit.dg` (see [Project Setup](#project-setup)) overrides `(program entry point)` to run every object with the `(test *)` trait instead of starting the game. Once the tests finish, dgdebug drops into its own `suspended>` debug prompt rather than quitting automatically, so the pass/fail output stays on screen - exit it yourself (`@quit` or Ctrl+D) once you've read the results. See the "Testing and Debugging" chapter of the Dialog manual (bundled with the [Dialog toolchain](https://github.com/dialog-if/dialog)'s own docs) for how to write `(test *)`/`(assert ...)` objects.
+
+`.skein` files are plain text, designed to diff cleanly under version control - commit them alongside your source.
+
+## Building & Exporting
+
+**Dialog IDE: Configure Exports...** defines named export configurations, stored in `dialog.json`'s `exports` array: an output format (`zblorb`, `z8`, or `aa`), whether to include debug sources, an output path, and (optionally) extra `dialogc` options for that export specifically (e.g. `--heap 2000 --aux 1000`, for a project that needs a bigger heap). The same menu also sets a project-wide *default* set of `dialogc` options, used by any export configuration that doesn't specify its own, and by **Export Web Page...** (below).
+
+**Dialog IDE: Export Dialog Project...** picks one of those configurations and compiles it with `dialogc`.
+
+**Cover image.** If a `cover.png` exists at your project root (seeded automatically by **Initialize Dialog Project**, or add your own), a `zblorb` export bakes it in automatically via `dialogc`'s `--cover`/`--cover-alt` flags - no configuration needed.
+
+**Dialog IDE: Export Web Page...** asks which of `dialog.json`'s named export configurations should build the downloadable story file (same picker as **Export Dialog Project...**), then builds a complete web page into `out/web/` (plus a zip at `out/<name>-<release>.zip`): that configuration's story file, compiled fresh with its own format/debug/`dialogc`-options settings; an in-browser player powered by [AAmachine](https://github.com/dialog-if/aamachine) (built separately as `aa`, unless the picked configuration is itself `aa`, in which case that same build drives both); the cover image, resized to a thumbnail; the project's configured feelies (below); and, if `default.skein` has a knot labeled `WALKTHROUGH`, a walkthrough transcript (everything from the root to that knot, skipping any command starting with `*`). Story title/author/blurb/release/IFID on the page come from the project's own `(story ...)` directives, queried live via `dgdebug`. Directs to **Configure Exports...** first if no export configurations are defined yet.
+
+**Feelies.** A feelie is any attachment linked from the exported page - traditionally a "how to play interactive fiction" PDF for newcomers, but any file works. **Initialize Dialog Project** seeds two starter PDFs (`introduction-to-if.pdf`, `play-if-card.pdf`) and wires them into `dialog.json`'s `feelies` array automatically. Right-click a file in the Explorer and choose **Add Feelie** to attach it directly (or run **Dialog IDE: Add Feelie...** from the Command Palette, which prompts you to pick a file instead), then give it a display name; **Dialog IDE: Remove Feelie...** takes one out again. Unlike the cover image, a configured feelie whose file has gone missing is an error at export time, not a silent omission - fix the path in `dialog.json` or remove the feelie.
+
+## Command-Line Interface
+
+`dgbuild` runs project checks headlessly - no VS Code, no extension host - for scripts and CI (e.g. gating a release on a GitHub Action). Install it with `npm install -g dgbuild` (or use `npx dgbuild ...` without installing), then run it from your project root or pass `--project <dir>`:
+
+- **`dgbuild test`** - runs the project's unit tests (`dgdebug --unit-test`) and exits non-zero on any failure, *or if `dialog.json` declares no `test` sources at all* (nothing to run is treated as a failure, not a silent pass). `--no-debug` excludes debug sources (included by default, matching **Dialog IDE: Run Tests**); extra arguments after the options are passed through to `dgdebug`.
+- **`dgbuild run-skein [names...]`** - replays one or more saved skeins (default: `default`, matching `default.skein`) against a fresh `dgdebug` process each, exits non-zero if any knot's live response no longer matches its blessed response across any of them, and prints a `valid/new/error` count summary per skein plus a `total` line when running more than one, e.g. `default: 200/0/1 (valid/new/error)`. Errored knots are printed above the summary. Add `-v/--verbose` to see the underlying `dgdebug` process commands/lifecycle logging (suppressed by default - busy otherwise, especially with multiple skeins).
+- **`dgbuild sources`** - prints the project's expanded source file list (`-d/--debug`, `-t/--test` to include those categories, `-T/--target <suffix>` to filter by target suffix, `-1/--single-line` for a colon-joined line instead of one path per line).
+
+A minimal release-gating step in a GitHub Action:
+
+```yaml
+- run: npx dgbuild test && npx dgbuild run-skein
+```
+
+## Using the Skein
+
+The Skein panel opens beside your editor, split into a **nav graph** (left) and a **transcript** (right), with a command field at the bottom.
+
+**Transcript.** Each knot shows a command and its response. The active knot (the one you're positioned at) has a blue left border. Others are colored by status:
+
+| Color | Meaning |
+|---|---|
+| Grey | Valid - matches the blessed response |
+| Yellow | New - no blessed response yet |
+| Red | In error - the latest response doesn't match what's blessed |
+
+New or errored knots are shown in a fixed-width font with visible whitespace, and word-level diffs (red for removed, blue for added) when a response has changed.
+
+**Nav graph.** The full tree of every knot you've ever explored, color-coded the same way (with faded tinting on ancestors that have a new/errored descendant, so you can spot trouble without expanding every branch). Click any knot to make it active; the transcript updates to show the path down to it. Clicking through a chain with only one child at each step auto-expands down to the next branch or leaf.
+
+**Blessing.** *Bless Knot* accepts that the active knot's response is correct; *Bless Transcript* blesses every knot visible in the transcript. Once blessed, a knot turns from new/error to valid.
+
+**Replaying.** *Replay* re-runs the project from the root through the active knot and checks each response against what's blessed - the fast way to confirm a source change did what you intended. *Replay All* does this for every leaf in the tree at once, so you know the *entire* skein still holds together, not just the path you happen to be looking at.
+
+**Time travel.** Click any earlier knot, then *New Child* to branch off with a different command from that point - nothing you already recorded is lost, it's just no longer on the displayed path.
+
+**Trace and Dynamic State** (dgdebug only). From a knot's action menu, *Trace...* (also ⌥T) shows which predicates were tried, in what order, and why, with clickable links into your source; *Dynamic State...* shows exactly what changed in the game world as a result of that command. A navbar toggle can also switch on an always-visible summary of dynamic state changes, which are displayed inline in the transcript (after each knot).
+
+## Keyboard shortcuts
+
+The Skein is designed to be fully usable without a mouse (all shortcuts below are Option/⌥ on Mac, Alt on Windows/Linux):
+
+| Shortcut | Action |
+|---|---|
+| ⌥↑ / ⌥↓ | Parent / child knot |
+| ⌥← / ⌥→ | Previous / next sibling |
+| ⌥⇧↑ / ⌥⇧↓ | First knot (root) / last knot (leaf) |
+| ⌥B / ⌥⇧B | Bless Knot / Bless Transcript |
+| ⌥R / ⌥⇧R | Replay to active knot / Replay All |
+| ⌥A | New Child (time travel) |
+| ⌥E | Edit Command |
+| ⌥L | Edit Label |
+| ⌥K | Toggle Lock |
+| ⌥D | Delete |
+| ⌥X | Toggle Expand (nav graph) |
+| ⌥T | Trace... |
+| ⌥F | Focus search |
+| ⌘S / ⌘Z / ⌘⇧Z | Save / Undo / Redo |
+
+Insert Parent and Splice Out are available from a knot's action menu but have no keyboard accelerator.
+
+Undo/redo is unlimited and covers structural edits (bless, delete, splice, running a new command); it doesn't re-run anything, so it's always instant.
+
+VS Code normally can't forward other keybindings through a webview at all (a platform limitation, not something extensions can fix generically), so Dialog IDE explicitly punches through ⌘⇧A / Ctrl+Shift+A to open the Command Palette while the Skein or Trace panel has focus - handy if you've remapped it there instead of the default ⌘⇧P / Ctrl+Shift+P.
+
+## Known limitations
+
+- `frotz`/`frotz-release` need `dfrotz` on `PATH` (or set as `binDir` in `dialog.json`) - unlike `dgdebug`/`dialogc`, it isn't bundled with the extension yet
+- No "Reload from disk" action yet for picking up external changes to a `.skein` file
+- Dynamic state and tracing require `dgdebug`, and are unavailable for a command that ends on a single-keystroke prompt (the debugger can't be interrupted mid-keystroke to ask for either)
+- **Export Web Page...** needs `aambundle` (from [AAmachine](https://github.com/dialog-if/aamachine)) in addition to `dgdebug`/`dialogc` - see [Requirements](#requirements)
+- An existing export configuration can't be edited in place yet - remove it and add it again with the new settings
+
+## Future Improvements
+
+This is an early release of the extension; we have many more features planned, including:
+
+- Bundle `dfrotz` per platform, like `dgdebug`/`dialogc` already are
+- Upload projects to the Interactive Fiction Archive
+- Provide binaries for OS X on Intel hardware
+
+Get involved at [Interactive Fiction Community Forum](https://intfiction.org/t/dialog-ide-0-0-1/81465/7) to provide feedback and ideas!
+
+## License
+
+[Apache License 2.0](LICENSE). The vendored `.dg` TextMate grammar and language configuration are separately MIT-licensed - see [THIRD_PARTY_LICENSES.md](THIRD_PARTY_LICENSES.md).

package/THIRD_PARTY_LICENSES.md

@@ -0,0 +1,157 @@
+# Third-Party Licenses
+
+## `syntaxes/dialog.tmLanguage.json` and `language-configuration.json`
+
+These two files are vendored, essentially verbatim, from the
+[`dialog-language-support`](https://github.com/sideburns3000/vscode-dialog-language) VS Code
+extension (version 1.1.0), by Michael Lauenstein. They provide the TextMate grammar and editor
+configuration (comments, brackets, folding, indentation, word pattern) for Dialog's `.dg` source
+files.
+
+Nothing else from that extension was carried over — in particular its `dialog.compileTo*`
+commands, `dialog` task type, problem matcher, and `dialog.compiler`/`dialog.includeWhenCompiling`
+settings were deliberately not reimplemented or derived from, since Dialog IDE has its own
+project-level build/export tooling planned that will cover the same ground independently.
+
+The original extension is MIT licensed:
+
+```
+MIT License
+
+Copyright (c) 2019 Michael Lauenstein
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## `bin/` — bundled `dgdebug`/`dialogc` binaries
+
+Platform-specific builds of this extension (`win32-x64`, `darwin-arm64`, `linux-x64`) bundle the
+`dgdebug` and `dialogc` binaries under `bin/<target>/`. These are unmodified, prebuilt
+redistributions from the [Dialog-IF/dialog](https://github.com/Dialog-IF/dialog) project — a
+community-maintained fork of the Dialog interactive fiction language originally created by
+Linus Åkesson — taken from the release pinned in `scripts/dialog-toolchain-version.json`
+(currently `release-1c02-1.2.3`). They are staged at package time by
+`scripts/fetch-dialog-binaries.js` and are not bundled in the universal (no-target) package,
+which continues to rely on `PATH`/`dialog.json`'s `binDir` like every prior release of this
+extension.
+
+The upstream `license.txt` (2-clause-BSD-style, permitting binary redistribution with the
+copyright notice retained), reproduced verbatim:
+
+```
+Copyright 2018-2026 Linus Åkesson and the Dialog Project contributors
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+	1. Redistributions of source code must retain the above copyright
+	notice, this list of conditions and the following disclaimer.
+
+	2. Redistributions in binary form must reproduce the above copyright
+	notice, this list of conditions and the following disclaimer in the
+	documentation and/or other materials provided with the distribution.
+
+	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
+	IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
+	TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+	PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+	HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+	SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+	LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+	DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+	THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+	(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+	OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+This license is intended to apply to the Dialog compiler and debugger and
+the source code of the standard libraries. Any time those components are
+distributed, this copyright notice should be attached. But it is not meant
+to limit what the compiler's output can be used for, even for projects that
+include the standard libraries. To make this explicit, the project is ALSO
+released under a modified two-clause BSD license, which is exactly the same
+as the above but adds this exception:
+
+	As an exception, if, as a result of you compiling your source code,
+	portions of this software are embedded into compiler output in binary
+	form, you may redistribute such embedded portions without complying
+	with condition 2 of the license.
+
+In other words, you can distribute the Z-machine and Å-machine bytecode that
+the compiler produces in any way you like, without needing to include this
+license file or comply with the attribution requirements (for the library
+or for the Z-machine runtime routines).
+```
+
+(The full upstream `license.txt` also covers the Windows GUI debugger's bundled Glk/WinGlk/libogg/
+libvorbis components — this extension does not bundle `dgdebug_gui.exe` or `Glk.dll`, only the
+console `dgdebug`/`dialogc` binaries covered by the BSD-style block above.)
+
+## `bin/` — bundled `aambundle` binary
+
+The same platform-specific builds also bundle `aambundle` under `bin/<target>/`, alongside
+`dgdebug`/`dialogc`. This is an unmodified, prebuilt redistribution from the
+[Dialog-IF/aamachine](https://github.com/Dialog-IF/aamachine) project (the Å-machine, used by
+"Export Web Page..." to produce an in-browser player for the exported story), taken from the
+release pinned in `scripts/dialog-toolchain-version.json` (currently `release-1.0.1`) and staged
+by the same `scripts/fetch-dialog-binaries.js`. Only `aambundle` itself is bundled — not
+`aamrun`/`aamshow`, which this extension doesn't use.
+
+The upstream `license.txt` (2-clause-BSD-style, permitting binary redistribution with the
+copyright notice retained), reproduced verbatim:
+
+```
+Copyright 2019-2026 Linus Åkesson and the Dialog Project
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+	1. Redistributions of source code must retain the above copyright
+	notice, this list of conditions and the following disclaimer.
+
+	2. Redistributions in binary form must reproduce the above copyright
+	notice, this list of conditions and the following disclaimer in the
+	documentation and/or other materials provided with the distribution.
+
+	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
+	IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
+	TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+	PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+	HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+	SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+	LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+	DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+	THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+	(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+	OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Note that the aambundle tool will automatically insert a license file that
+complies with these requirements.
+```
+
+(The full upstream `license.txt` also covers jquery/minimist, redistributed by `aambundle`
+itself inside the web-player output it generates at export time — not something this extension
+vendors separately — and a public-domain 6502 emulator used only by `aambox6502`, which this
+extension does not bundle.)
+
+## `resources/bundle/` — vendored web-export assets
+
+`default-cover.png`, `style.css`, `play.css`, `introduction-to-if.pdf`, and `play-if-card.pdf`
+under `resources/bundle/` are copied from the
+[dialog-tool](https://github.com/hlship/dialog-tool) project (the same author, also Apache-2.0
+licensed) to keep "Export Web Page..." at feature parity with dialog-tool's own `dgt bundle`.