web: project settings page for the rules a human sets (reviewer/tester checklist, role rules, rules text)

tsk-z5h7h1v7kmjd proposed

Oliver chose this (req-6ytgcc5yhzpg). Occasion: he adopted a rule for every review result (a final line VERDICT APPROVE|CHANGES <full head SHA>, req-0tbk7sn2ytnx) and wants it as a hub rule. The place for it is settings.role_rules.reviewer.checklist (docs/api.md §6.1, §6.9). Only a human with project:admin may set role_rules and rules_markdown; an agent never writes the rules it works under. The web has no page for either today, and the owner has no CLI.

Idea, to be planned:

A section in the project settings, admin humans only: per role (coder, reviewer, tester) the subagent_per_card switch and, for reviewer and tester, the checklist (at most 30 items, one line each, 1–300 characters), plus the owner-edited rules text (rules_markdown).
A preview of the generated rules for a chosen role (GET …/rules), so the owner sees what an agent will read.
The hub's refusals (unknown_role, not_allowed, length) said in words.

First item once built: the reviewer checklist line End every review_result with one line: VERDICT APPROVE <full 40-char head SHA> or VERDICT CHANGES <full 40-char head SHA>.

Status: idea only. Before any work starts, this card is planned in detail and discussed with the owner. Do not claim it.