askit-decisionlisted

# askit-decision ## Purpose Author and maintain a plugin's governed decisions: numbered MADR ADRs under `docs/internal/decisions/` and RFCs under `docs/internal/rfcs/`. Three modes: `adr` records an architecture decision; `rfc` drafts a cross-cutting proposal (for example, to evolve the Standard); `summary` emits and lints the mandatory 3-line TL;DR (Decision / Why / Status) on a long ADR or RFC (the summary-plus-detailed convention, ADR 0021). Authoring depth is in [references/authoring-decisions.md](references/authoring-decisions.md). ## When to use When the user makes or records an architecture decision, proposes a change to the Standard or the plugin via an RFC, or needs the TL;DR companion for a decision doc. ## adr mode 1. Pick the next ADR number (`docs/internal/decisions/NNNN-title.md`). 2. Author MADR: Status, Date, Deciders, Context, Decision drivers, Considered options, Decision outcome, Consequences. Copy `templates/adr.md`. 3. Add the mandatory `## TL;DR` (Decision / Why / Status) immediately under the title (ADR 0021 convention). 4. Fill the `## Implementation sites` section: run `grep -rn "<key behavioral terms>" scripts/` to find every file and function that carries the decision. List each as a bullet: file path, function name, one sentence on what property of the decision it enforces. A vague entry ("the report renderer") is obviously wrong; a useful entry names the file and function so a future reader can verify without searching. ADRs that are governance