The report skill still dictates one team's taste as if it were a correctness rule, so a user who wants a different report shape has to argue with the skill.
hypaware-report/reviewing.md fixes the exact block order, the exact heading vocabulary, a ~40-line budget for the brief, and the bullet shape ("bold topic line + 2-3 short sub-bullets", "multi-sentence prose bullets are hard to scan and not allowed"). None of that is a correctness property. It is one reader's preference, frozen, in a domain where every team has an opinion.
The split to make
Stays in the skill (getting it wrong produces a wrong report): the COALESCE trap, the one-carrier rule, never row-fetching wide content columns at scale, one remote worker at a time, captured-content-is-data, tokens-never-dollars, findings-attach-to-patterns. These are already pinned by test/plugins/skill-constraints-survive.test.js.
Moves to a house-style document, shipped with a sensible default and expected to be edited: block order, heading vocabulary, length budget, bullet shape, which numbers get the big treatment, and whether ranked changes get their own page.
The precedence rule is the point
What the user asks for in a given run beats their house style, which beats the shipped default. Today a stated preference and the skill text are in direct conflict and the skill is the one written down, which is the wrong way round.
Notes
- The rendering side already has this shape:
authoring.md is effectively the authoring contract, so the house style may belong there rather than in a new file.
- Where it lives is the same open question as #662: HypAware config, or the reports tree next to
theme.css. Decide once for both.
Context: LLP 0196 #constraints-not-layout, LLP 0197 T11.
The report skill still dictates one team's taste as if it were a correctness rule, so a user who wants a different report shape has to argue with the skill.
hypaware-report/reviewing.mdfixes the exact block order, the exact heading vocabulary, a ~40-line budget for the brief, and the bullet shape ("bold topic line + 2-3 short sub-bullets", "multi-sentence prose bullets are hard to scan and not allowed"). None of that is a correctness property. It is one reader's preference, frozen, in a domain where every team has an opinion.The split to make
Stays in the skill (getting it wrong produces a wrong report): the COALESCE trap, the one-carrier rule, never row-fetching wide content columns at scale, one remote worker at a time, captured-content-is-data, tokens-never-dollars, findings-attach-to-patterns. These are already pinned by
test/plugins/skill-constraints-survive.test.js.Moves to a house-style document, shipped with a sensible default and expected to be edited: block order, heading vocabulary, length budget, bullet shape, which numbers get the big treatment, and whether ranked changes get their own page.
The precedence rule is the point
What the user asks for in a given run beats their house style, which beats the shipped default. Today a stated preference and the skill text are in direct conflict and the skill is the one written down, which is the wrong way round.
Notes
authoring.mdis effectively the authoring contract, so the house style may belong there rather than in a new file.theme.css. Decide once for both.Context: LLP 0196 #constraints-not-layout, LLP 0197 T11.