mirror of
https://github.com/garrytan/gstack.git
synced 2026-10-03 09:56:57 +02:00
garrytan
4dfed0b783
qa-only judges cited 'next section' pointing at the wrong heading, an exploratory trigger that contradicted its read point, clock ownership in mixed runs and the unstated order of exploratory section 4 vs reporting. The qa judge penalized the absent qa-report-template and issue-taxonomy that qa-patterns loads; with them in, it found issue-taxonomy's dangling 'rule 13' (the consent rule is browser rule 3).
20 lines
570 B
JSON
20 lines
570 B
JSON
{
|
|
"$schema": "https://gstack.dev/schemas/section-manifest.json",
|
|
"skill": "qa-only",
|
|
"version": 1,
|
|
"sections": [
|
|
{
|
|
"id": "exploratory",
|
|
"file": "exploratory.md",
|
|
"title": "Report-only exploratory QA",
|
|
"trigger": "selecting surfaces and later running the selected report-only probes without product or test writes (one Read covers both)"
|
|
},
|
|
{
|
|
"id": "reporting",
|
|
"file": "reporting.md",
|
|
"title": "Evidence-grounded report finalization",
|
|
"trigger": "finalizing the report after probing stops"
|
|
}
|
|
]
|
|
}
|