Export a QA report
Export an already recorded QA run. This workflow publishes a report package; it does not create
test results or reinterpret evidence commands. Read workflow,
safety, artifacts,
evidence, and reports first.
Inputs
- An explicit private manifest path and an explicit project root path. Never infer either path
from the current directory, a run ID, or a prior conversation.
- The explicit objective or intent for the export, target identity, contract source/hash,
complete acceptance-criterion catalog, cases, evidence, defects, limitations, recorded
authorization, and existing QA verdict carried by that manifest.
- Explicit authorization to create a new report package beneath the supplied project root. The
manifest's run ID must identify a new destination; export never grants any other authority.
Procedure
- Preserve the explicit objective or intent, target, contract, criteria, cases, evidence,
defects, limitations, authorization, and recorded results. Do not infer missing criteria,
applicability, assessments, execution, approval, or risk acceptance.
- Identify the affected QA surfaces and consult installed applicable
qa-specialist-requirements, qa-specialist-defects, or other qa-specialist-* skills only
to expose semantic gaps already present in the supplied record. An unavailable applicable
specialist is a limitation. Specialist guidance does not expand authorization or change the
normalized manifest.
- Before export, require a complete acceptance criteria catalog that preserves all criterion
IDs, text, applicability and reason, assessment expected and observed values, and referenced
case IDs. Confirm the identified contract and completed criteria review are recorded. Missing
semantic confirmation remains a limitation and prevents a newly inferred
PASS.
- Use the explicit manifest and project root unchanged. The workflow invokes the exporter
exactly once and never permits a second exporter invocation. Its only process invocation is
qa_report.py report --manifest PATH --project-root PATH. Replace each PATH with its
separately supplied path; do not add another subcommand, omit either option, or reuse an
implicit root.
- Let the exporter enforce schema and verdict precedence. Before HTML or PDF rendering, the
exporter must validate acceptance criteria, confinement, limits, hashes, target/contract
binding, sanitization, and evidence safety. The exporter renders HTML and PDF from the same
normalized manifest. It publishes only a complete validated package. Never edit the private
or public manifest around validation.
- Preserve returned diagnostics, sanitization outcomes, and verdict without suppressing,
repairing, or reclassifying them. Preserve
export_status, output_dir, publication digest,
and snapshot when present. Exit code 0 means both formats exported; it does not mean the QA
verdict is PASS. Exit codes 2 and 3 remain refusal and incomplete export respectively.
- Stored
command values are inert text. It never executes or re-executes tests, manifest
commands, or evidence commands. It never uses a stored command to fill a missing result and
never retries the export after a failure or collision.
Output
Return exactly these labels in this order. Tables may follow their labels. Report facts from the
exporter result and manifest; do not derive the QA verdict from the process exit code.
TARGET: <manifest target, project, environment/build/change identity when recorded>
OBJECTIVE: <preserved explicit export objective or intent>
CONTRACT: <manifest contract path, hash, and criteria-review actor/time/completeness>
CRITERIA: <complete preserved IDs/text, applicability/reasons, assessments, case IDs, and criterion results>
OPERATION: report (export only; execute no tests or evidence commands)
AUTHORIZATION: <preserved export actor, authority, scope, target, project root, limits, and gaps>
EXPORT: <command outcome, exit code, export_status, output_dir, publication digest/snapshot, HTML/PDF state, and diagnostics>
RESULTS: <preserved case and criterion statuses: PASS|FAIL|BLOCKED|NOT_RUN|NOT_APPLICABLE>
LIMITATIONS: <missing semantic confirmation, unsafe/insufficient evidence, unavailable specialist, incomplete export, or none>
EVIDENCE_REFERENCES: <verified copied evidence IDs, public relative paths, hashes, target/contract binding, sanitization outcome, or none>
CURRENT_DEFECTS: <all current in-scope defects and explicitly separated out-of-scope defects, including unlinked defects, or none>
VERDICT: <preserved exporter QA verdict: PASS|FAIL|BLOCKED; independent of export exit code>
NEXT: <smallest separately selected and explicitly authorized correction, new run, or consumer revalidation action>
Failure modes
- Missing or implicit manifest/project-root paths, missing export authorization, invalid schema,
unsafe input/output, limit violation, symlink, or destination collision: do not substitute a
path or retry; return the refusal diagnostic and no complete package.
- Missing, changed, target-mismatched, or sanitization-pending evidence remains withheld,
produces a diagnostic, and prevents
PASS. Never conceal it to make export succeed.
- A rendering or dependency failure is an incomplete export. Preserve the exclusive partial
diagnostic path if returned, and never describe it as the complete run package.
- A complete export with verdict
FAIL or BLOCKED is still an exported report. Do not rewrite
the verdict from exit code 0.
Safety
- Never execute tests, stored commands, or evidence content during report export. Never install
dependencies, alter personal configuration, expose secrets, or attach rejected evidence.
- Load testing, penetration testing, production access, and external effects require explicit
authorization for a separate exact operation; report export performs none of them.
- Never correct product code, tests, contracts, results, evidence, defects, approvals, or
authorization; product corrections are allowed only when separately requested.
- Never publish externally, push, merge, deploy, overwrite a prior run, or treat a partial
diagnostic directory as a complete report.
Related skills
qa-specialist-requirements exposes acceptance-catalog gaps without rewriting the manifest.
qa-specialist-defects checks the meaning of recorded current defects without resolving them.
qa-status summarizes the resulting state without exporting or mutation.
qa-release produces a readiness opinion separately from export status.
1---2name: qa-report3description: Export one validated QA manifest as matching HTML and PDF without executing tests or evidence commands.4metadata:5 source: https://skillmd.com/skills/pwdev-solucoes/qa-report6---78# Export a QA report910Export an already recorded QA run. This workflow publishes a report package; it does not create11test results or reinterpret evidence commands. Read [workflow](../../references/workflow.md),12[safety](../../references/safety.md), [artifacts](../../references/artifacts.md),13[evidence](../../references/evidence.md), and [reports](../../references/reports.md) first.1415## Inputs1617- An explicit private manifest path and an explicit project root path. Never infer either path18 from the current directory, a run ID, or a prior conversation.19- The explicit objective or intent for the export, target identity, contract source/hash,20 complete acceptance-criterion catalog, cases, evidence, defects, limitations, recorded21 authorization, and existing QA verdict carried by that manifest.22- Explicit authorization to create a new report package beneath the supplied project root. The23 manifest's run ID must identify a new destination; export never grants any other authority.2425## Procedure26271. Preserve the explicit objective or intent, target, contract, criteria, cases, evidence,28 defects, limitations, authorization, and recorded results. Do not infer missing criteria,29 applicability, assessments, execution, approval, or risk acceptance.302. Identify the affected QA surfaces and consult installed applicable31 `qa-specialist-requirements`, `qa-specialist-defects`, or other `qa-specialist-*` skills only32 to expose semantic gaps already present in the supplied record. An unavailable applicable33 specialist is a limitation. Specialist guidance does not expand authorization or change the34 normalized manifest.353. Before export, require a complete acceptance criteria catalog that preserves all criterion36 IDs, text, applicability and reason, assessment expected and observed values, and referenced37 case IDs. Confirm the identified contract and completed criteria review are recorded. Missing38 semantic confirmation remains a limitation and prevents a newly inferred `PASS`.394. Use the explicit manifest and project root unchanged. The workflow invokes the exporter40 exactly once and never permits a second exporter invocation. Its only process invocation is41 `qa_report.py report --manifest PATH --project-root PATH`. Replace each `PATH` with its42 separately supplied path; do not add another subcommand, omit either option, or reuse an43 implicit root.445. Let the exporter enforce schema and verdict precedence. Before HTML or PDF rendering, the45 exporter must validate acceptance criteria, confinement, limits, hashes, target/contract46 binding, sanitization, and evidence safety. The exporter renders HTML and PDF from the same47 normalized manifest. It publishes only a complete validated package. Never edit the private48 or public manifest around validation.496. Preserve returned diagnostics, sanitization outcomes, and verdict without suppressing,50 repairing, or reclassifying them. Preserve `export_status`, `output_dir`, publication digest,51 and snapshot when present. Exit code `0` means both formats exported; it does not mean the QA52 verdict is `PASS`. Exit codes `2` and `3` remain refusal and incomplete export respectively.537. Stored `command` values are inert text. It never executes or re-executes tests, manifest54 commands, or evidence commands. It never uses a stored command to fill a missing result and55 never retries the export after a failure or collision.5657## Output5859Return exactly these labels in this order. Tables may follow their labels. Report facts from the60exporter result and manifest; do not derive the QA verdict from the process exit code.6162```text63TARGET: <manifest target, project, environment/build/change identity when recorded>64OBJECTIVE: <preserved explicit export objective or intent>65CONTRACT: <manifest contract path, hash, and criteria-review actor/time/completeness>66CRITERIA: <complete preserved IDs/text, applicability/reasons, assessments, case IDs, and criterion results>67OPERATION: report (export only; execute no tests or evidence commands)68AUTHORIZATION: <preserved export actor, authority, scope, target, project root, limits, and gaps>69EXPORT: <command outcome, exit code, export_status, output_dir, publication digest/snapshot, HTML/PDF state, and diagnostics>70RESULTS: <preserved case and criterion statuses: PASS|FAIL|BLOCKED|NOT_RUN|NOT_APPLICABLE>71LIMITATIONS: <missing semantic confirmation, unsafe/insufficient evidence, unavailable specialist, incomplete export, or none>72EVIDENCE_REFERENCES: <verified copied evidence IDs, public relative paths, hashes, target/contract binding, sanitization outcome, or none>73CURRENT_DEFECTS: <all current in-scope defects and explicitly separated out-of-scope defects, including unlinked defects, or none>74VERDICT: <preserved exporter QA verdict: PASS|FAIL|BLOCKED; independent of export exit code>75NEXT: <smallest separately selected and explicitly authorized correction, new run, or consumer revalidation action>76```7778## Failure modes7980- Missing or implicit manifest/project-root paths, missing export authorization, invalid schema,81 unsafe input/output, limit violation, symlink, or destination collision: do not substitute a82 path or retry; return the refusal diagnostic and no complete package.83- Missing, changed, target-mismatched, or sanitization-pending evidence remains withheld,84 produces a diagnostic, and prevents `PASS`. Never conceal it to make export succeed.85- A rendering or dependency failure is an incomplete export. Preserve the exclusive partial86 diagnostic path if returned, and never describe it as the complete run package.87- A complete export with verdict `FAIL` or `BLOCKED` is still an exported report. Do not rewrite88 the verdict from exit code `0`.8990## Safety9192- Never execute tests, stored commands, or evidence content during report export. Never install93 dependencies, alter personal configuration, expose secrets, or attach rejected evidence.94- Load testing, penetration testing, production access, and external effects require explicit95 authorization for a separate exact operation; report export performs none of them.96- Never correct product code, tests, contracts, results, evidence, defects, approvals, or97 authorization; product corrections are allowed only when separately requested.98- Never publish externally, push, merge, deploy, overwrite a prior run, or treat a partial99 diagnostic directory as a complete report.100101## Related skills102103- `qa-specialist-requirements` exposes acceptance-catalog gaps without rewriting the manifest.104- `qa-specialist-defects` checks the meaning of recorded current defects without resolving them.105- `qa-status` summarizes the resulting state without exporting or mutation.106- `qa-release` produces a readiness opinion separately from export status.