Files
gstack/qa
garrytan 4dfed0b783 fix(qa-only,qa): name the exploratory read point and finalization order; judge qa with its browser assets
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).
2026-09-30 22:07:25 +00:00
..