Files
gstack/qa/sections/manifest.json
T
Garry Tan dcaea52800 v1.91.7.0 feat: add functional QA and pre-publication docs checks (#2983)
* feat: add surface-aware exploratory QA and ship documentation gates

* test: preserve delegated QA setup authority after main integration

* fix(qa): clarify exploration order and preserve report artifacts

* test(qa): follow the shared setup reference directly

* refactor(ship): make verification and recovery routes explicit

* test(ship): align evidence and review guards with explicit routes

* fix(workflows): clarify ship recovery and functional QA evidence

* fix(workflows): clarify approval recovery and full QA coverage

* refactor(workflows): order review transactions and clarify ship state

* fix(ship): clarify final verification and fail closed at publication

* fix(evals): attribute native atomic documentation writes

* fix(ship): clarify recovery and documentation lifecycle guidance

* fix(test): preserve observed native placeholder styling in CI

* fix(codex): report watchdog timeouts without a process-exit race

* Checkpoint functional QA implementation and workflow validation repairs

* Fix documentation and shared-review fixture contracts

* docs: clarify judge reuse and evaluation supervision

* test: align review evidence and selected case contracts

* test: verify append-only documentation checkpoints and recovery

* fix: qualify QA workflows and CI validation repairs

* fix: launch shared-libs fixture scripts on Windows

* fix: qualify QA deadlines, fixture isolation, and shard cleanup

* fix: preserve qualified QA and cancellation repairs

* fix: enforce functional fixture authority and share strict event decoding

* fix: retain free-test evidence and explain recovery

* fix: reject malformed native evidence after decoder consolidation

* test: use reliable capture for telemetry privacy filters

* test: refresh measured quick coverage and document validation costs

* Fix native fixture receipts and preserve VM validation evidence

* Align negative judge controls with upstream clarity policy

* Fix report-only QA preparation and public evidence handling

* Clarify QA-only preparation and current-report preservation

* Stream Ship quality judgments with an explicit 64k response contract

* Validate compact judge reasoning locally with supported wire schema

* Align functional QA fixture instructions with evidence acceptance

* Bind native browser diagnostics to execution evidence and align review verdicts

* Preserve native diagnostic line boundaries

* Serialize functional QA evidence from native captures

* Keep large QA evidence fixture payload out of Windows argv
2026-09-29 06:07:35 -07:00

51 lines
2.3 KiB
JSON

{
"$schema": "https://gstack.dev/schemas/section-manifest.json",
"skill": "qa",
"version": 1,
"note": "PASSIVE registry (v2 plan T9 / CM2). Fields are IDs, file paths, human titles, and human-readable trigger text ONLY. The skeleton's decision-tree prose is the ONLY place that decides WHEN to read a section; required-reads live in the E2E fixtures. No machine predicate here — see docs/designs/v2_PLAN.md:663.",
"sections": [
{
"id": "scope",
"file": "scope.md",
"title": "Surface selection and safe probe authority",
"trigger": "setting up or probing a target, unless this invocation already established its surfaces and isolation"
},
{
"id": "browser-setup",
"file": "browser-setup.md",
"title": "Browser-only setup",
"trigger": "setting up an explicitly selected browser surface; never for functional-only targets"
},
{
"id": "exploratory",
"file": "exploratory.md",
"title": "Shared exploratory QA",
"trigger": "running the selected target's QA baseline and exploratory probes, with caller-owned authority"
},
{
"id": "system-functional",
"file": "system-functional.md",
"title": "Native functional contracts and evidence",
"trigger": "probing a selected API, CLI, job, worker or webhook surface with repository-supported tools"
},
{
"id": "browser-verify",
"file": "browser-verify.md",
"title": "Browser-only repair verification",
"trigger": "rechecking a reproduced browser defect after repair; never for a functional-only repair"
},
{
"id": "test-bootstrap",
"file": "test-bootstrap.md",
"title": "Test Framework Bootstrap",
"trigger": "checking the browser target's test framework during Setup; never for functional-only targets — ecosystem detection, authorized bootstrap, CI pipeline and first tests"
},
{
"id": "qa-patterns",
"file": "qa-patterns.md",
"title": "Core QA patterns — modes, Phases 1-6 workflow, health rubric, framework guidance, testing rules",
"trigger": "running the QA baseline (Phases 1-6) — mode selection (Diff-aware/Full/Quick/Regression), the phase-by-phase browser workflow, the Health Score Rubric, framework-specific guidance, and the browser-testing Important Rules"
}
]
}