Temp

.cargo/config.toml

@@ -28,24 +28,23 @@ TS_RS_IMPORT_EXTENSION = "ts"
 # -------------------------
 #
 # Link the Microsoft C runtime statically on Windows. The default, dynamic
-# linkage, makes every Windows artifact -- the Server executable and the
-# VSCode extension's `.node` addon alike -- import `VCRUNTIME140.dll`, which
-# Windows does not ship: it arrives only with the Visual C++ redistributable.
-# A machine without that redistributable therefore fails to load the addon
-# with `ERROR_MOD_NOT_FOUND`, which Windows reports against the addon's own
-# path, so the artifact which is present is accused of being missing (see the
-# diagnosis in `extensions/VSCode/src/index.js`). The UCRT half of the C
-# runtime, named by the `api-ms-win-crt-*` imports, is part of Windows itself
-# and needs no such treatment.
+# linkage, makes every Windows artifact -- the Server executable and the VSCode
+# extension's `.node` addon alike -- import `VCRUNTIME140.dll`, which Windows
+# does not ship: it arrives only with the Visual C++ redistributable. A machine
+# without that redistributable therefore fails to load the addon with
+# `ERROR_MOD_NOT_FOUND`, which Windows reports against the addon's own path, so
+# the artifact which is present is accused of being missing (see the diagnosis
+# in `extensions/VSCode/src/index.js`). The UCRT half of the C runtime, named by
+# the `api-ms-win-crt-*` imports, is part of Windows itself and needs no such
+# treatment.
 #
 # Nothing crosses the C runtime boundary here. The addon talks to Node through
 # N-API, which passes no allocations, locales or `FILE*`s between the two, and
-# it embeds the whole Server rather than linking to a second Rust artifact --
-# so the usual hazard of a statically linked runtime inside a DLL does not
-# arise.
+# it embeds the whole Server rather than linking to a second Rust artifact -- so
+# the usual hazard of a statically linked runtime inside a DLL does not arise.
 #
-# This applies to the host triple as well as to a cross build, so Cargo hands
-# it to build scripts and proc macros too whenever `--target` is absent.
+# This applies to the host triple as well as to a cross build, so Cargo hands it
+# to build scripts and proc macros too whenever `--target` is absent.
 #
 # The `cfg` form covers `i686` and `aarch64` alongside `x86_64` -- the three
 # MSVC triples the VSCode loader searches for -- so adding one of them to the
@@ -54,3 +53,15 @@ TS_RS_IMPORT_EXTENSION = "ts"
 # included.
 [target.'cfg(all(windows, target_env = "msvc"))']
 rustflags = ["-C", "target-feature=+crt-static"]
+
+# Security
+# --------
+#
+# Set a minimum publish age to combat supply-chain attacks. Copied from
+# [Dependency Cool-Downs Land in Stable](https://weeklyrust.substack.com/p/dependency-cool-downs-land-in-stable).
+# Not yet released, so produces a warning.
+[resolver]
+incompatible-publish-age = "deny"
+
+[registry]
+global-min-publish-age = "7 days"   # or "14 days", "1 week", "6 months" etc.

.devcontainer/postCreateCommand.sh

@@ -8,6 +8,6 @@ if [ -x /usr/local/bin/chrome ] && [ ! -e /usr/local/bin/google-chrome ]; then
     sudo ln -s /usr/local/bin/chrome /usr/local/bin/google-chrome
 fi
 
-cd server
+# <fragment id="cc-ZTqrakWBqI"></fragment>
 ./bt install --dev
 ./bt build

.github/workflows/check.yml

@@ -50,9 +50,11 @@ jobs:
       ##      builder
       ##      server
       ##      extensions/VSCode
+      # On Windows, GitHub Actions runs these commands in PowerShell, which runs
+      # `bt.ps1`; elsewhere, bash runs `bt`.
+      # <fragment id="cc-T3IsnVlz14"></fragment>
       - name: Run tests
         run: |
           rustup update
-          cd server
           ./bt install --dev
           ./bt full

.github/workflows/release.yml

@@ -144,12 +144,15 @@ jobs:
       - name: Install dependencies
         run: |
           ${{ matrix.packages_install }}
+      # dist generated this file; the `bt` calls in this step are hand-added,
+      # which `allow-dirty = ["ci"]` in `dist-workspace.toml` permits.
+      # <fragment id="cc-ENVtePRoYi" following="3"></fragment>
       - name: Build artifacts
         run: |
-          server/bt prerelease
+          ./bt prerelease
           # Actually do builds and make zips and whatnot
           dist build ${{ needs.plan.outputs.tag-flag }} --print=linkage --output-format=json ${{ matrix.dist_args }} > dist-manifest.json
-          server/bt postrelease ${{ matrix.dist_args }} ${{ needs.plan.outputs.tag-flag }}
+          ./bt postrelease ${{ matrix.dist_args }} ${{ needs.plan.outputs.tag-flag }}
           echo "dist ran successfully"
       - id: cargo-dist
         name: Post-build

.ignore

@@ -0,0 +1,30 @@
+# Copyright (C) 2026 Bryan A. Jones.
+#
+# This file is part of the CodeChat Editor.
+#
+# The CodeChat Editor is free software: you can redistribute it and/or modify it
+# under the terms of the GNU General Public License as published by the Free
+# Software Foundation, either version 3 of the License, or (at your option) any
+# later version.
+#
+# The CodeChat Editor is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# the CodeChat Editor. If not, see
+# [http://www.gnu.org/licenses/](http://www.gnu.org/licenses/).
+#
+# `.ignore` -- Show hidden directories to the CodeChat Editor
+# ===========================================================
+#
+# The CodeChat Editor's project cache walks the project with the
+# [ignore](https://docs.rs/ignore) crate, which skips hidden files and
+# directories unless an ignore file whitelists them. These directories contain
+# fragments gathered elsewhere in the project, such as the calls to `bt`
+# gathered in `docs/implementation.md`. ripgrep honors this file as well.
+!.github/
+!.devcontainer/
+
+# CodeChat Editor lexer: python

CHANGELOG.md

@@ -24,6 +24,15 @@ Changelog
 
 * No changes.
 
+Version 0.3.1 -- 2026-Oct-21
+----------------------------
+
+* Support navigation of links in gather elements, fragments, and cross
+  references.
+* Clicking on a link activates the TinyMCE editor when the link's doc block is
+  pure HTML, instead of navigating to the link.
+* Improved HTML to Markdown conversion.
+
 Version 0.3.0 -- 2026-Oct-09
 ----------------------------
 

CLAUDE.md

@@ -32,18 +32,50 @@ void foo();
 // since they are separated by a code block.
 ```
 
+### <span id="cc-sZ0Glsgjhu">Cross-references, gather elements, and fragments</span>
+
+To refer to text in another section of the current document or any file in this
+project:
+
+1. Assign a unique id for that section: `<span id="some_unique_id">section
+   title</span>`; in a code file, this must be placed in a doc block. Any HTML
+   element with an id can be the target of either a hyperlink or a
+   cross-reference.
+2. Refer to it using a hyperlink or cross-reference. For example, the following
+   syntax links directly to the `<span>` inside this section's heading:
+   `[Foo](#cc-sZ0Glsgjhu)` (link text is "Foo") / `<xref
+   ref="cc-sZ0Glsgjhu"></xref>` (link text comes from the cross-referenced span:
+   "Cross-references, gather elements, and fragments"); the same syntax (a bare
+   id with no file) also links to any file in the project.
+
+When implementing a specification:
+
+1. Label each doc block preceding non-contiguous section of code of more than
+   three lines with a fragment placed at the end of the doc block: `<fragment
+   id="some_unique_id1"></fragment>`.
+2. Gather these fragments in a subheading following the specification: `<h4
+   id="another_unique_id" data-gather="some_unique_id1 some_unique_id2
+   ...">Implementation of [title of this section]</h4>`.
+
+Each id must be unique throughout the entire project. To create an id:
+
+1. Randomly generate an id of the form `cc-[10 random ASCII letters or
+   numbers]`.
+2. grep the project to ensure this id is unique.
+
 Architecture
 ------------
 
-A Visual Studio Code extension in `extensions/VSCode` exchanges messages with
-the CodeChat Editor Server, located in `server/` (also termed the Server), which
-also exchanges messages with the CodeChat Editor Client (also termed the Client)
-located in `client/`.
+A Visual Studio Code extension in `extensions/VSCode` or the standalone server
+in `extensions/standalone` exchanges messages with the CodeChat Editor Server,
+located in `server/` (also termed the Server), which also exchanges messages
+with the CodeChat Editor Client (also termed the Client) located in `client/`.
 
 Project build
 -------------
 
-All build commands must be executed from the `server/` directory.
+Execute these build commands, which run the [`bt`](#cc-1s8bUScadp) script, from
+the root of the project.
 
 * To build the entire project, execute `./bt build`.
 * To format and lint the entire project, execute `./bt flint`.
@@ -139,6 +171,8 @@ Because comments become doc blocks, these mechanical rules apply:
 * Denote paragraphs using an empty comment (`//` or `///`), not an empty line.
 * A comment on the same line as code is never a doc block; it stays part of the
   code block.
+* When commenting out code, use `/*** ... */` to prevent the code from being
+  treated as a doc block.
 
 ### File structure
 
@@ -148,8 +182,8 @@ Source files follow this template (a few predate it; match it in new files):
 2. The GPL copyright and license block, copied verbatim from a neighboring file
    rather than retyped. In Rust it uses plain `//`, so it stays a doc block
    separate from the title which follows it.
-3. A single level-1 heading titling the file: the file name in a monospaced font
-   -- matching the file's actual name -- then `--`, then a short description.
+3. A single level-1 heading titling the file: the file name in backticks --
+   matching the file's actual name -- then `--`, then a short description.
 4. The file-level design narrative, if the file needs one.
 5. A `Modules` section, if the file has submodules, then an `Imports` section.
    In Rust its subsections are `### Standard library`, `### Third-party`, and
@@ -186,7 +220,7 @@ use std::collections::HashMap;
 
 ### TypeScript specifics
 
-* Use `//` tags instead of `/**` blocks.
+* Use `//` comments instead of `/**` blocks.
 * Document parameters as described above instead of using `@param` tags.
 
 ### Editing existing comments