feature-doc: closed-loop feature documentation

Produces one evidence-backed feature article end to end. Capture needs no manual gesture: a bundled recorder grabs frames from the browser through the DevTools protocol. Publishing the docs PR stays a gate for you at CP-6.

Configuration

Set these once (a .env, your kit.toml, or pass them as arguments). Nothing below is hardcoded.

Setting	Meaning	Example
`APP_URL`	Start page of the live app to drive	`https://app.example.com/projects/1`
`ISSUE_REPO`	Issue tracker holding the feature issues	`your-org/your-product`
`DOCS_REPO`	Local path of the docs repo	`../your-docs`
`DOCS_DIR`	Folder inside the docs repo for the article	`docs/features/`
`EVIDENCE_DIR`	Where screenshots and video land	`./evidence/<feature>/`

Keep the docs repo in a folder your tools can always read. Some operating systems block background reads of the Documents folder mid-session, which breaks the verifier.