docs(requirements): split pitch runtime claim

Split the pitch overview into checked-hypermedia and no-app-JavaScript rows so redgate no longer reports pitch/001 as oversized.

req: pitch/001

req: pitch/005

AGENTS.md

@@ -15,7 +15,7 @@ Keep it stable. Prefer pointers to canonical sources over copied structure, file
 - Cite relevant requirements in code, tests, or docs as `req: <component>/001`.
 - Do not add citation-only padding to satisfy tooling; cite only where the requirement constrains the text.
 - Use requirement tags consistently: stable area tags like `[parser]`, `[auth]`, `[ui]`; temporary planning tags like `[bootstrap]`, `[mvp]`, or `[milestone-1]` only while they are useful.
-- Run `redgate list`, `redgate refs`, and `redgate health` when requirements change.
+- Run `redgate list`, `redgate refs`, and `redgate health` when requirements change; include `redgate lint` when the change is meant to reduce requirement maintainability warnings.
 
 ## Git workflow
 

REQUIREMENTS.md

@@ -31,7 +31,10 @@ client app state framework.
 ## pitch
 
 ### req: pitch/001
-001	hemx is checked hypermedia for Rust. Write `.heml`, write Rust handlers, return generated UI commands. The compiler checks every cross-file reference. The browser runtime only sees lowered ids and effect bytes. No JS app code is required for ordinary server-first apps. [north_star]
+001	hemx is checked hypermedia for Rust: authors write `.heml`, write Rust handlers, and return generated UI commands while the compiler checks every cross-file reference. [north_star]
+
+### req: pitch/005
+005	For ordinary server-first apps, no app-owned JavaScript is required: the browser runtime only sees lowered ids and effect bytes. [north_star]
 
 ### req: pitch/002
 002	No CSS selectors. No hx-* strings. No virtual DOM. No client framework. No hidden global proxy magic. No component hydration. SSR state bootstrap via `data-hemx-st` is allowed, but the browser never reconstructs a component tree. [north_star]