Use this checklist before publishing the repository or cutting a release snapshot.
data/,artifacts/,ckpt/,runs/,wandb/, andmodels/are empty or absent.- No private paths, ad hoc local scripts, or machine-specific configs have been introduced.
- No secrets, tokens, or cached credentials are present.
Run the unified local gate:
bash scripts/audit/release_gate.shThis gate currently runs:
pytest -q tests- fixture-based math smoke
- fixture-based code smoke
- dummy figure generation for the plotting path
bash scripts/audit/pre_release.sh
These are recommended before a public paper artifact release:
- Strict data verification:
bash scripts/data/prepare_all.sh --out_dir data --strict 1- SFT-only main-results sweep:
bash scripts/reproduce/paper_main_results.sh sweep \
--registry configs/main_results_registry.yaml \
--only_methods SFT- Optional release gate with a real HF base model:
HF_BASE='Qwen/Qwen2.5-3B-Instruct' RUN_SFT_EVAL=1 bash scripts/audit/release_gate.shREADME.mdmatches the current release policy and entrypoints.docs/GETTING_STARTED.mdmatches actual installation and smoke commands.docs/CODE_MAP.mdanddocs/IMPLEMENTATION_AUDIT.mdstill match the primary implementation path.docs/DATA_SOURCES.mdandconfigs/data_manifest.yamlremain consistent.
LICENSE,CITATION.cff, andTHIRD_PARTY_NOTICES.mdare up to date..github/workflows/pre-release-audit.ymland.github/workflows/ci-lite.ymlstill match the intended release gate.- Community files (
CONTRIBUTING.md,CODE_OF_CONDUCT.md,SECURITY.md) still describe the current workflow.