Refresh agent documentation standards - #150
Conversation
Import the latest Rust agent template guidance into `AGENTS.md` and `docs/documentation-style-guide.md` so the repository follows the current shared documentation, testing, observability, and contribution rules. Update the documentation contents and repository layout pages to match the new style guide expectations, then apply the repository Markdown formatter and repair existing lint failures that blocked the documentation gate.
WalkthroughThis PR comprehensively refresh the repository documentation: rewrite AGENTS.md with expanded Rust guidance, add a Documentation maintenance section, standardise ExecPlan "living document" formatting, expand the documentation style guide and repository layout, and reflow many docs across the docs/ tree. ChangesAssistant Instructions and Repository Contributor Guidance
Documentation Conventions, Style Guide, and Repository Mapping
ExecPlan Living Document Standardisation
Design Specifications and Architectural Documentation
Developers' and Users' Guides, and Technical Walkthroughs
Roadmap and Archive Documentation
Sequence Diagram(s)(Skip — changes are documentation reflows and policy additions; no new runtime component interactions introduced.) Possibly related PRs
Suggested labels
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
|
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/documentation-style-guide.md`:
- Line 285: The RFC template's fenced code block currently uses the "markdown"
language identifier; update the RFC template code fence to use "plaintext"
(matching the ADR template's usage) so non-code text uses the correct language
identifier—locate the RFC template code block (the block starting with
```markdown and the header "# RFC 0001: <title>") and change the fence
identifier to ```plaintext.
In `@docs/execplans/7-1-4-cache-integration-for-card-extraction-keyed-by-uri.md`:
- Around line 310-315: Fix the corrupted markdown list by correcting item 1 to
show the CardCacheKey struct fields with balanced backticks and proper
punctuation: list the fields as path: PathBuf, content_hash: [u8; 32], language:
SupportedLanguage (from weaver-syntax), detail: DetailLevel, line: u32, column:
u32 and end the sentence with "Implement `Hash` and `Eq`." Remove or merge the
nonsensical item 2 ("`. `") so the numbered list is coherent and only contains
the intended entries related to CardCacheKey.
In
`@docs/execplans/7-2-1-define-stable-jsonl-request-and-response-schemas-for-observe-graph-slice.md`:
- Around line 76-80: Rewrite the fragmented introductory sentence into a single
complete line: "The following documents must all be updated before the work is
complete:" and insert a blank line after that sentence and before the bulleted
list; also ensure there's a blank line after the list per docs style. Update the
paragraph containing that sentence in
docs/execplans/7-2-1-define-stable-jsonl-request-and-response-schemas-for-observe-graph-slice.md
so the intro is one continuous sentence and the list is separated by blank
lines.
In `@docs/rust-testing-with-rstest-fixtures.md`:
- Line 1349: The table row for the attribute #[rstest] uses the incorrect
indefinite article "an"; update the text to "Marks a function as a rstest test;
enables fixture injection and parameterization." by replacing "an rstest test"
with "a rstest test" in the docs/rust-testing-with-rstest-fixtures.md entry for
#[rstest], and ensure the change follows the repository's en-GB Oxford
spelling/documentation style.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: cfca8538-f426-4ca9-879c-61cf70d576c6
📒 Files selected for processing (55)
AGENTS.mddocs/archive/prototype-roadmap.mddocs/complexity-antipatterns-and-refactoring-strategies.mddocs/contents.mddocs/developers-guide.mddocs/documentation-style-guide.mddocs/execplans/13-3-3-archive-3-2-2-daemon-start-help-guidance.mddocs/execplans/2-2-1-act-apply-patch-sub-command.mddocs/execplans/2-2-2-list-all-domains-in-top-level-help.mddocs/execplans/2-2-3-top-level-version-output.mddocs/execplans/2-2-4-provide-contextual-domain-guidance.mddocs/execplans/2-3-1-validate-domains-client-side-before-daemon-startup.mddocs/execplans/2-3-2-valid-operation-alternatives-for-unknown-operations.mddocs/execplans/2-3-3-standardize-actionable-guidance-in-startup-errors.mddocs/execplans/2-3-4-return-argument-requirements-for-act-refactor.mddocs/execplans/3-1-1a-plugin-for-rope.mddocs/execplans/3-1-1b-plugin-for-rust-analyzer.mddocs/execplans/3-2-1-surface-configuration-flags-in-clap-help-output.mddocs/execplans/4-1-1-scaffold-sempai-core-and-sempai.mddocs/execplans/4-1-2-structured-diagnostics-with-stable-error-codes.mddocs/execplans/4-1-3-yaml-rule-parsing-via-saphyr-and-serde-saphyr.mddocs/execplans/4-1-4-mode-aware-sempai-validation.mddocs/execplans/4-1-5-normalization-into-canonical-formula-model.mddocs/execplans/5-1-1-entry-help.mddocs/execplans/5-2-1-define-the-rename-symbol-capability-contract.mddocs/execplans/5-2-2-update-weaver-plugin-rope-manifest.mddocs/execplans/5-2-3-update-rust-plugin-to-declare-rename-symbol.mddocs/execplans/5-2-4-daemon-capability-resolution-for-rename-symbol.mddocs/execplans/5-2-5-unit-behavioural-and-end-to-end-coverage-for-rename-symbol.mddocs/execplans/7-1-1-stable-jsonl-schemas-for-observe-get-card.mddocs/execplans/7-1-2-tree-sitter-symbol-card-extraction.mddocs/execplans/7-1-3-implement-optional-lsp-enrichment-for-observe-get-card.mddocs/execplans/7-1-4-cache-integration-for-card-extraction-keyed-by-uri.mddocs/execplans/7-2-1-define-stable-jsonl-request-and-response-schemas-for-observe-graph-slice.mddocs/execplans/adopt-ortho-config-v0-8-0.mddocs/execplans/phase-1-implement-the-socket-listener-in-weaverd.mddocs/execplans/sempai-design.mddocs/execplans/weaver-agent-roadmap.mddocs/formal-verification-methods-in-weaver.mddocs/jacquard-card-first-symbol-graph-design.mddocs/ortho-config-users-guide.mddocs/pratt-parser-for-ddlog-expressions.mddocs/reliable-testing-in-rust-via-dependency-injection.mddocs/repository-layout.mddocs/rfcs/0001-o11y.mddocs/roadmap.mddocs/rstest-bdd-users-guide.mddocs/rust-doctest-dry-guide.mddocs/rust-extricate-actuator-plugin-technical-design.mddocs/rust-parser-testing-comprehensive-guide.mddocs/rust-testing-with-rstest-fixtures.mddocs/semgrep-language-reference/semgrep-minimal-examples.mddocs/sempai-query-language-design.mddocs/users-guide.mddocs/weaver-design.md
Correct the `CardCacheKey` field list entry and remove the malformed numbered item so the stage plan list in the cache integration execplan is coherent and parsable.
Summary
This branch refreshes the repository's agent and documentation standards from the upstream Rust agent template, then formats the documentation set so the repository gates pass under the new rules.
Issue: none.
Roadmap task: none.
Execplan: none.
Review walkthrough
Validation
make fmt: passed.make check-fmt: passed.make lint: passed.make test: passed; nextest ran 1430 tests with 1430 passed and 4 skipped, and doctests passed.make markdownlint: passed.make nixie: passed.Notes
The upstream
AGENTS.md.jinjacontained no active Jinja control tokens at import time, so it was imported as Markdown after verification. The repository Markdown formatter touched existing documentation files beyond the two imported templates; those formatting changes are included becausemake fmtis part of the documented workflow for documentation updates.