Cline rules

1# Output discipline: compact, hand-typeable reports
2 
3The user reads your report off your screen and **hand-types** the redacted version into
4Teacher LLM. Reports MUST be short, structured, and easy to read off a single screen.
5 
6## Constraints
7 
8- **Maximum 30 lines** per report (target 15)
9- **Tabular over prose** wherever possible
10- **One observation per line**
11- **Fixed format per playbook** — each playbook below defines its report shape exactly
12- **Numbers, not adjectives** — `89%` not `most`; `503` not `many`
13 
14## Standard report types
15 
16Each playbook produces one of these:
17 
18| Type | Used by | Lines | Shape |
19|---|---|---|---|
20| `ORIENT` | orient | 5–8 | session-bootstrap confirmation |
21| `MAP` | mapping | 2–4 | mapping diff confirmation |
22| `PROF` | profile-corpus | 12–15 | per-element profile summary |
23| `RULE` | derive-rule | 8–10 | rule definition + coverage |
24| `RPT` | debug-pipeline | 15–25 | per-stage runtime stats |
25| `BUNDLE` | share-back | ≤40 | aggregation of multiple reports |
26 
27The exact field set per type is defined in the corresponding playbook.
28 
29## Conventions
30 
31- **Leading line is the report-type marker**: `PROF v=1 doc=<PLAN0>` — first token names
32  the type so the user (and Teacher LLM) can parse instantly.
33- **Field=value pairs**: `req=487 sec=312 tbl=98` — shorter than prose, no ambiguity.
34- **Placeholders only** for any redacted token: never emit a real value.
35- **No prose conclusions**: don't write "this looks problematic" or "I recommend X" —
36  Teacher LLM interprets and decides.
37- **Emit `MAPPING:` lines inline** when you add a new entry to the redaction mapping
38  during this report: `MAPPING: added LTEAT→<PLAN0>` (one line per addition).
39 
40## What NOT to include
41 
42- Prose explanations of "what this means"
43- Speculation, interpretation, recommendations
44- Full file contents (paths only)
45- Any token in unredacted form
46- Per-instance breakdowns (aggregate by category, never list verbatim instances)
47- Long examples — if the user needs an example, they can ask for one specific one
48 
49## Example layouts
50 
51**PROF** (good):
52```
53PROF v=1 doc=<PLAN0>
54sec_re:    ^(\d+(?:\.\d+)+)\s+\S
55req_re:    ^<MNO0>_REQ_<PLAN0>_\d+$
56toc:       leader-dot-page thr=0.7
57strk:      geom 2lines width≥0.5
58ver:       ^revision\s+history$
59defs:      2col-table Acronym|Definition
60N:         req=487 sec=312 tbl=98 fig=23
61audit:     HI=96.0% MED=3.0% LOW=0.1%
62miss:      5 LOW (deep-nest depth≥9)
63```
64 
65**PROF** (bad — leaks content):
66```
67PROF v=1 doc=LTEAT
68The first section is "1.1 INTRODUCTION" which contains the boilerplate...
69Section 1.2 "ATTACH PROCEDURES" describes...   ← verbatim heading text
70```
71