Skip to content

docs: Standardize via CONTRIBUTING.md + WRITING.md - #551

Merged
tony merged 2 commits into
masterfrom
house-style
Aug 22, 2026
Merged

docs: Standardize via CONTRIBUTING.md + WRITING.md#551
tony merged 2 commits into
masterfrom
house-style

Conversation

@tony

@tony tony commented Aug 22, 2026

Copy link
Copy Markdown
Member

AGENTS.md is read on every task, so a policy that matters to one class of change costs context on all the others. This splits how the project works from how it writes, so each loads when it applies, and makes both discoverable to humans rather than only to agents.

The root file becomes a router. It carries what should always be visible — what the repository is, where things live, and the change discipline every diff is held to — then points at one document per class of change.

Layout

AGENTS.md            router
CLAUDE.md -> AGENTS.md
.github/
├── CONTRIBUTING.md  how we work: setup, the gates, tests, docs, releases, pull requests
└── WRITING.md       how we write: README, CHANGES, release notes, docstrings, comments, commits

What moved

Nothing was deleted without a destination. Environment, commands, gates, testing strategy and fixtures moved to .github/CONTRIBUTING.md. Docstring conventions, doctest rules, changelog conventions, code-block rules, the comment gates and slop prevention moved to .github/WRITING.md, along with the whole of docs/AGENTS.md ("Documentation voice"), which is prose policy and now has one home.

Verification

Every gate was run, and the doctest collection count was recorded before and after. Documented examples are executed by pytest, so a preserved example that stopped being collected would be an invisible test deletion — the count is the proof it did not happen.

This repository

AGENTS.md goes from 728 lines to 67, across 8 changed files. No source, test, or CI file is touched.

why: AGENTS.md is read on every task, so a policy that matters to one
class of change costs context on all the others. Splitting how we work
from how we write lets each be loaded when it applies, and keeps both
discoverable to humans rather than only to agents.

what:
- Replace the AGENTS.md body with a router: the project map, universal
  change discipline, then one pointer per class of change
- Add .github/WRITING.md for prose policy, folding in docs/AGENTS.md's
  voice guidance and the prose-policy parts of the old AGENTS.md
- Add .github/CONTRIBUTING.md for workflow policy, folding in the
  workflow parts of the old AGENTS.md plus Logging Standards (kept out
  of src/libvcs/ so it cannot leak into the built wheel)
- Turn docs/project/contributing.md and docs/project/code-style.md
  into pointer pages to the canonical .github/ files; code-style.md
  keeps its one executing doctest, since testpaths includes docs/ but
  not .github/
- Delete docs/AGENTS.md and docs/CLAUDE.md, absorbed into WRITING.md
- Rewrite README.md to the new prose policy; fix the stale version
  pin example (>=0.37,<0.38 -> >=0.45,<0.46); preserve every link and
  every heading anchor
@codecov

codecov Bot commented Aug 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.34%. Comparing base (c90447f) to head (35cdd84).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #551   +/-   ##
=======================================
  Coverage   61.34%   61.34%           
=======================================
  Files          40       40           
  Lines        6556     6556           
  Branches     1104     1104           
=======================================
  Hits         4022     4022           
  Misses       1940     1940           
  Partials      594      594           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

why: The link used the pre-move `pytest-plugin.html` path, which only
resolves through a 301. Naming the current page directly removes a hop
and survives the next redirect cleanup.

what:
- Link the pytest fixtures reference at /api/pytest-plugin/
@tony tony changed the title Docs(refactor[agents]): Route instead of restate docs: Standardize via CONTRIBUTING.md + WRITING.md Aug 22, 2026
@tony
tony merged commit b178a99 into master Aug 22, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant