doc-stest-audit
Purpose
Run a single STEST audit workflow:
-
doc-stest-validator
-
doc-stest-reviewer
Then emit a combined fixer-ready report.
Output Contract
Primary output:
- STEST-NN.A_audit_report_vNNN.md
Fixer compatibility:
- doc-stest-fixer accepts .A_ (preferred) and .R_ (legacy-compatible).
Combined Status Rules
-
PASS: validator PASS AND reviewer score = 100 AND no blocking/manual-required issues
-
FAIL: validator FAIL OR reviewer score < 100 OR blocking/manual-required issues present
Deployment-gate policy:
- Timeout budget violations, missing rollback procedures, missing 100%-gate markers, or non-binary pass/fail criteria are manual_required or blocked and cannot auto-pass.
Combined Report Sections
-
Summary
-
Score Calculation
-
Validator Findings
-
Reviewer Findings
-
Coverage Findings
-
Deployment Gate Findings
-
Fix Queue (auto_fixable , manual_required , blocked )
-
Recommended Next Step
Handoff Rule
If remediation needed:
-
Run doc-stest-fixer with newest report.
-
On timestamp/version tie, prefer .A_ over .R_ .
Example
/doc-stest-audit docs/10_TSPEC/STEST/STEST-01_scope/STEST-01_scope.md
Version History
Version Date Changes
1.0 2026-02-27 Initial STEST audit wrapper with validator->reviewer orchestration and strict 100% deployment-gate pass contract
Implementation Plan Consistency (IPLAN-004)
-
Treat plan-derived outputs as valid source mode and verify intent preservation from implementation plan scope/objectives.
-
Validate upstream autopilot precedence assumption: --iplan > --ref > --prompt .
-
Flag objective/scope conflicts between plan context and artifact output as blocking issues requiring clarification.
-
Do not introduce legacy fallback paths such as docs-v2.0/00_REF .