RELEASE_CHECKLIST.md

Release Checklist

Use this checklist before creating a public release tag or release package.

1. Product Surfaces

• Demo chain runs end-to-end.
• report.html is generated and readable.
• learn/index.html is generated and readable.
• patterns.json / pattern_summary.json are generated.
• ai_summary.*, ai_risks/*, ai_explain/* generation is validated.
• Studio run page can open key views.

2. Testing and Gates

• Key focused tests pass.
• Full python -m unittest -v status is recorded.
• Warning status is recorded (including ResourceWarning trend).
• Production chain validated on at least one real run:
  • ci run
  • verify --strict
  • gate
  • patch exports
  • run manifest

3. Documentation

• README first screen is clear (value + boundary + quickstart).
• Quickstart command is copy-runnable.
• Docs entry points are complete and up to date.
• Grounded boundary language is consistent (Evidence-first, deterministic, Facts first).

4. OSS and Compliance

• License layering is confirmed (code/docs/case data policy).
• Third-party case data keeps minimal necessary snippets and repo_ref.
• No secrets/private tokens/private paths in tracked artifacts.
• Machine-specific assumptions are documented or removed.

See also: OSS_PREP.md

5. Release Artifacts

• run_manifest.json is stable and readable.
• exports/context_pack.zip is generated and valid.
• Demo output paths are stable and documented.
• Release assets list is explicit (if publishing artifacts):
  • report sample
  • patterns sample
  • ai summary sample
  • risks sample
  • manifest sample

6. Final Sign-off

• No schema changes (schema_version unchanged) unless explicitly planned.
• No grounded-boundary violations.
• Release notes include known limits and deferred items.