Quality Gates

Purpose

Define the canonical release-quality gates for DSAMbayes v1.2.2, including commands, pass/fail criteria, and evidence requirements.

Audience

• Maintainers preparing a release candidate
• Reviewers signing off release readiness
• Engineers running local pre-merge quality checks

Gate Matrix

Gate Definitions

QG-1 Lint

Command:

R_LIBS_USER="$PWD/.Rlib" Rscript scripts/check.R --lint

Fail conditions:

• Non-zero exit code
• Any lint issue reported
• Any SKIP: output

QG-2 Style

Command:

R_LIBS_USER="$PWD/.Rlib" Rscript scripts/check.R --style

Fail conditions:

• Non-zero exit code
• Any file reported as requiring reformat
• Any SKIP: output

QG-3 Unit Tests

Command:

R_LIBS_USER="$PWD/.Rlib" R -q -e 'testthat::test_dir("tests/testthat")'

Fail conditions:

• Non-zero exit code
• Any test failure or error

QG-4 Package Check

Command:

R_LIBS_USER="$PWD/.Rlib" R -q -e 'rcmdcheck::rcmdcheck(args = c("--no-manual","--compact-vignettes=gs+qpdf"))'

Fail conditions:

• Any ERROR
• Any WARNING for release sign-off

Escalation condition:

• Any NOTE must be reviewed and explicitly accepted with rationale.

QG-5 Runner Smoke: Validate

Command:

R_LIBS_USER="$PWD/.Rlib" \
  Rscript scripts/dsambayes.R validate \
    --config config/blm_synthetic_mcmc.yaml \
    --run-dir results/quality_gate_validate

Fail conditions:

• Non-zero exit code
• Missing results/quality_gate_validate/00_run_metadata/config.resolved.yaml

QG-6 Runner Smoke: Run

Command:

R_LIBS_USER="$PWD/.Rlib" \
  Rscript scripts/dsambayes.R run \
    --config config/blm_synthetic_mcmc.yaml \
    --run-dir results/quality_gate_run

Fail conditions:

• Non-zero exit code
• Missing results/quality_gate_run/00_run_metadata/config.resolved.yaml
• Missing results/quality_gate_run/20_model_fit/model.rds
• Missing results/quality_gate_run/30_post_run/posterior_summary.csv
• Missing results/quality_gate_run/40_diagnostics/diagnostics_report.csv

QG-7 Docs Build Check

Command:

R_LIBS_USER="$PWD/.Rlib" \
  Rscript -e 'pkgdown::build_site_github_pages(new_process = FALSE, install = FALSE)'

Fail conditions:

• Non-zero exit code
• pkgdown build aborts before site generation

Command Reference

Recommended environment setup before running gates:

# Navigate to your local DSAMbayes checkout
cd /path/to/DSAMbayes
mkdir -p .Rlib .cache
export R_LIBS_USER="$PWD/.Rlib"
export XDG_CACHE_HOME="$PWD/.cache"

Optional consolidated local gate (does not replace all release gates):

R_LIBS_USER="$PWD/.Rlib" Rscript scripts/check.R --all

scripts/check.R --all covers lint, style, tests, and coverage. It does not run rcmdcheck, runner smoke checks, or pkgdown build.

Evidence Requirements

Minimum evidence bundle per release candidate:

1. Full terminal output and exit code for each gate QG-1 to QG-7.
2. Runner smoke artefacts under results/quality_gate_validate/.
3. Runner smoke artefacts under results/quality_gate_run/.
4. rcmdcheck summary with explicit handling of NOTEs.
5. Confirmation that no gate result is SKIP.

Evidence review should reference:

• Release Readiness Checklist
• Release Evidence Pack
• Release Sign-off Template

Failure and Escalation Rules

1. Any gate failure blocks release tagging.
2. Do not proceed to sign-off with unresolved ERROR or WARNING.
3. NOTEs require written rationale and reviewer acceptance.
4. If a gate fails due to environment setup, fix the environment and re-run the full affected gate.
5. If a gate fails due to product code, raise a remediation change and re-run from QG-1.

Sign-off Criteria

Release sign-off requires all of the following:

1. QG-1 to QG-7 passed.
2. No SKIP outcomes across mandatory gates.
3. Evidence bundle completed and reviewed.
4. Final decision recorded in sign-off-template.md.