Fix: workaround dist install bug.

.config/nextest.toml

@@ -0,0 +1,40 @@
+# The CodeChat Editor, a word processor for software developers.<br>Copyright
+# (C) 2024-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).
+#
+# `nextest.toml` -- a cargo-nextest configuration file
+# ====================================================
+#
+# See the [docs](https://nexte.st/docs/configuration/) for this file. nextest
+# reads it only from `.config/` in the workspace root.
+#
+# Browser-backed tests
+# --------------------
+#
+# The `overall` test binary (`server/tests/overall.rs`, which gathers the
+# `overall_*.rs` modules) drives a browser through WebDriver. Overlapping
+# WebDriver sessions are unreliable on macOS CI, so run these tests one at a
+# time. nextest runs each test in its own process; a
+# [test group](https://nexte.st/docs/configuration/test-groups/) limits how many
+# of those processes run at once, while other tests still run in parallel.
+[test-groups]
+web-driver = { max-threads = 1 }
+
+[[profile.default.overrides]]
+filter = "binary_id(codechat-editor-server::overall)"
+test-group = "web-driver"

.github/workflows/check.yml

@@ -58,5 +58,4 @@ jobs:
       - name: Run tests
         run: |
           rustup update
-          # <fragment id="cc-Y8gI-nu0l_"></fragment>
           ./bt install && ./bt full

.github/workflows/release.yml

@@ -64,7 +64,7 @@ jobs:
         # we specify bash to get pipefail; it guards against the `curl` command
         # failing. otherwise `sh` won't catch that `curl` returned non-0
         shell: bash
-        run: "curl --proto '=https' --tlsv1.2 -LsSf https://github.com/axodotdev/cargo-dist/releases/download/v0.33.1/cargo-dist-installer.sh | sh"
+        run: "curl --proto '=https' --tlsv1.2 -LsSf https://github.com/axodotdev/cargo-dist/releases/download/v0.34.0/cargo-dist-installer.sh | sh"
       - name: Cache dist
         uses: actions/upload-artifact@v7
         with:

AGENTS.md

@@ -61,10 +61,10 @@ project:
 
 1. Assign a unique id for that section: `<h3 id="some_unique_id">section
    title</h3>` for a level-3 section; 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 this section's heading: `[Foo](#cc-sZ0Glsgjhu)`
+   doc block. Any HTML element with an id can be the target of a
+   cross-reference.
+2. Refer to it using a cross-reference. For example, the following syntax links
+   directly to this section's heading: `<xref ref="cc-sZ0Glsgjhu">Foo</xref>`
    (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
@@ -73,15 +73,15 @@ 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
+   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
+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.
 
@@ -103,6 +103,11 @@ the root of the project.
 * To format and lint the entire project, execute `./bt flint`.
 * To run all tests, execute `./bt test`.
 
+### Testing
+
+Browser-based integration tests (see [overall.rs](server/tests/overall.rs)) run
+slowly. Use other, faster tests where possible.
+
 Commenting guide
 ----------------
 
@@ -150,10 +155,9 @@ consistent.
   fn set_contents(&mut self, contents: String);
   ```
 
-* Scale a comment's length to its altitude instead of aiming for uniform
-  brevity: file- and section-level comments carry the design narrative and may
-  run for dozens of lines (see `server/src/processing/cache.rs`), while a
-  comment on a single statement is a line or two.
+* Place specifications or long documentation for a file in an accompanying
+  Markdown file; see `server/src/processing/cache.rs` and
+  `server/src/processing/cache-spec.md`. Comments in source should be short.
 
 * In new work, mark deferred work with `TODO:` followed by both the task and the
   condition which will resolve it, so a later reader knows when it may be
@@ -173,11 +177,11 @@ rustdoc renders neither. Many existing signatures are not yet annotated this
 way; add annotations to signatures you touch rather than sweeping the tree:
 
 ```rust
-/// Phase 1 of hydration: parse the HTML, walk the DOM, then commit the
-/// collected facts to the cache.
+/// Phase 1 of hydration: walk the DOM, then commit the collected facts to the
+/// cache.
 fn hydrate_dom(
-    // The HTML to hydrate.
-    html: &str,
+    // The parsed HTML to hydrate.
+    dom: Rc<Node>,
     // The cache for the project containing this file.
     cache: &Arc<Mutex<Cache>>,
     // The parsed, patched DOM plus the walk results needed by later phases.
@@ -206,7 +210,8 @@ Source files follow this template (a few predate it; match it in new files):
    separate from the title which follows it.
 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.
+4. A short file-level design narrative or reference to additional content in the
+   related Markdown file, 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
    `### Local`; the Client and the VSCode extension use their own names, so

CHANGELOG.md

@@ -23,7 +23,19 @@ Changelog
 [Github master](https://github.com/bjones1/CodeChat_Editor)
 -----------------------------------------------------------
 
-* No changes.
+Version 0.3.2 -- 2026-Nov-09
+----------------------------
+
+* Changed `<xref>` to support optional content.
+* Close an unclosed tag, comment, or declaration at the end of its doc block,
+  instead of letting it hide or move later doc blocks.
+* Report an error instead of crashing when an unclosed code block hides later
+  doc blocks, and instead of erasing text when an unclosed tag hides the text
+  after it. The Client shows this error in a toast and keeps showing the last
+  text which translated, read-only until the error is fixed.
+* Keep anything inside a `<fragment>`, such as the text after a missing
+  `</fragment>`, instead of erasing it on the next save.
+* Fix retranslations of math in gather elements.
 
 Version 0.3.2 -- 2026-Oct-31
 ----------------------------