Add repeated paragraphs

.github/workflows/release.yaml

@@ -1,11 +1,14 @@
 name: Release
 on:
   push:
+    branches:
+      - main
     tags:
       - "v*"
   workflow_dispatch:
 permissions:
   contents: write
+
 jobs:
   build:
     strategy:

.github/workflows/tests.yaml

@@ -1,35 +1,28 @@
 name: Tests
-
 on:
   push:
-
 jobs:
   test:
     runs-on: ubuntu-latest
-
     permissions:
       contents: read
       actions: write
-
     steps:
       - name: Checkout
         uses: actions/checkout@v4
         with:
           fetch-depth: 0
-
       - name: Install Nix
         uses: cachix/install-nix-action@v31
         with:
           extra_nix_config: |
             experimental-features = nix-command flakes
-
       - name: Restore Nix store
         id: nix-cache
         uses: nix-community/cache-nix-action/restore@v7
         with:
           primary-key: nix-${{ runner.os }}-${{ hashFiles('**/flake.lock') }}
           restore-prefixes-first-match: nix-${{ runner.os }}-
-
       - name: Restore Cargo cache
         uses: actions/cache/restore@v4
         id: cargo-cache
@@ -43,13 +36,12 @@ jobs:
           key: cargo-${{ runner.os }}-${{ hashFiles('**/Cargo.lock') }}
           restore-keys: |
             cargo-${{ runner.os }}-
-
       - name: Build project
         run: nix develop --command cargo build
-
       - name: Run tests
         run: nix develop --command cargo test
-
+      - name: Run clippy
+        run: nix develop --command cargo clippy -- -D warnings
       - name: Save Cargo cache
         if: always()
         uses: actions/cache/save@v4
@@ -61,7 +53,6 @@ jobs:
             ~/.cargo/git/db/
             target/
           key: ${{ steps.cargo-cache.outputs.cache-primary-key }}
-
       - name: Save Nix store
         uses: nix-community/cache-nix-action/save@v7
         if: always()
@@ -72,4 +63,4 @@ jobs:
           purge-prefixes: nix-${{ runner.os }}-
           purge-created: 0
           purge-last-accessed: P7D
-          purge-primary-key: never
+          purge-primary-key: never

AGENTS.md

@@ -0,0 +1,25 @@
+## ts_types imports
+- Always import `ts_types` via wildcard (`use crate::mdschema::validator::ts_types::*;`) so we do not list individual members.
+
+## Test imports
+- Prefer `super::...` imports inside `#[cfg(test)]` modules (e.g., `super::test_utils::ValidatorTester` or `super::TextualVsTextualValidator`) so the tests stay concise and structured.
+- Keep using wildcard `ts_types::*` in tests as well.
+
+## Documentation
+- When a doc block lists both `schema_str` and `input_str`, use the exact wording:
+  - `schema_str`: The full input document (so far).
+  - `input_str`: The full schema document.
+- Every `///` doc line that mentions `got_eof` must read verbatim `/// * \`got_eof\`: Whether we have received the full input document.`
+
+## Node-walker validator docs
+- Every file under `src/mdschema/validator/node_walker/validators` should start with a module doc comment and list each validator type defined in that file.
+
+## Walker usage
+- Never add aliases such as `let schema_str = walker.schema_str()` or `let input_str = walker.input_str()`; call the walker methods directly.
+
+## Contributing-from-CONTRIBUTING.md
+- When we talk about a data structure that stores references to schema and input, keep the schema entry first.
+- Prefer `get_node_text` from `ts_utils` over calling `utf8_text` directly.
+- In tests, keep assertion order consistent: position assertions first, followed by errors, then values.
+- Avoid `ValidationResult::destruct`; use accessors like `result.errors()`, `result.value()`, or `result.farthest_reached_pos()`.
+- When debugging tests, call `test_logging!();` (from `utils.rs`) at the top of the suite to hydrate logs and trace output.