@@ -65,27 +65,19 @@ parallelism: they run under the GIL for coverage, but the proof comes from the f
 
 ## Workflow
 
-Real work **not scheduled** becomes a GitHub issue.
-
 Every link in `README.md` must be absolute: `https://github.com/modern-python/<repo>/blob/main/<path>`,
 or `.../tree/main/<path>` for a directory. Never a relative path: `README.md` is also the PyPI long
 description, and PyPI does not rewrite relative links, so a relative one 404s on the package page.
 
-An invariant is a test whose name is the claim, with a docstring opening `INVARIANT:` and a second
-paragraph naming **what breaks it** — design rationale, not a report of what this one test catches;
-a sibling test may be the one that trips.
-
 ## Code Style
 
 - Design principle: thin wrapper, small public surface. `httpware.__all__` is checked against an
   explicit expected set in `tests/test_public_api.py`, so a symbol cannot appear unnoticed
 - `Http` is two letters in a class name (`AsyncClient`, not `ASYNCClient`); no `a` prefix on async
   methods, matching `httpx2` — `aclose()` is the sole exception
-- Type suppressions are `# ty: ignore[<rule>]`, never `# type: ignore`: this project checks with
-  `ty`, which silently accepts the latter without checking the rule
 - Docstrings: public API documents the contract; internal helpers get a one-line contract, plus at
   most 1–2 lines for a genuinely non-obvious constraint. Never narrate implementation or justify
-  code to a reviewer — cross-file rationale lives in an `INVARIANT:` test docstring
+  code to a reviewer — cross-file rationale lives in an invariant test's docstring
 
 ## Agent skills