Release readiness definition (Level 20.1)

Author: DavidQ

docs/dev/CODEX_COMMANDS.md

@@ -1,10 +1,6 @@
 MODEL: GPT-5.3-codex
 REASONING: high
 
-Execute BUILD_PR_LEVEL_19_23_ENGINE_TOOL_BOUNDARY_LEAK_VALIDATION:
-
-- inspect src/engine
-- detect any tool-specific references or dependencies
-- validate boundary rules
-- output findings to docs/dev/reports
-- do not modify code
+Execute BUILD_PR_LEVEL_20_1_RELEASE_READINESS_DEFINITION:
+- define release criteria
+- produce checklist in docs/dev/reports

docs/dev/COMMIT_COMMENT.txt

@@ -1,3 +1 @@
-Engine/tool boundary leak validation (Phase 19 final lane)
-
-BUILD_PR_LEVEL_19_23_ENGINE_TOOL_BOUNDARY_LEAK_VALIDATION
+Release readiness definition (Level 20.1)

docs/dev/reports/BUILD_PR_LEVEL_20_1_RELEASE_READINESS_DEFINITION_checklist.md

@@ -0,0 +1,47 @@
+# BUILD_PR_LEVEL_20_1_RELEASE_READINESS_DEFINITION Checklist
+
+Date: 2026-04-17
+Scope: Define measurable release-readiness criteria aligned to Level 20 roadmap tracks.
+
+## Roadmap Alignment
+- Track A - Release Readiness
+- Track B - Stability & Monitoring
+- Track C - Documentation Completeness
+
+## Release Criteria Checklist
+- [ ] A1. Release criteria baseline approved and recorded in this checklist.
+- [ ] A2. Build pipeline is finalized and reproducible:
+  - Required command set is documented.
+  - Build output artifact path and structure are consistent.
+  - Build failure exits non-zero and surfaces actionable logs.
+- [ ] A3. Deployment flow validated end-to-end:
+  - Dry-run deployment path succeeds.
+  - Rollback path is documented and verified.
+  - Post-deploy smoke checks are defined and executable.
+
+- [ ] B1. Runtime error tracking is active:
+  - Runtime error events are captured.
+  - Error context includes subsystem and timestamp.
+  - Unhandled exceptions are surfaced in validation logs.
+- [ ] B2. Performance monitoring hooks are active:
+  - Frame/update timing metrics are emitted.
+  - Memory-use snapshot reporting is available for validation runs.
+  - Performance regressions are detectable with a documented threshold.
+- [ ] B3. Logging standardization is enforced:
+  - Log levels are consistent across runtime/tooling surfaces.
+  - Validation logs are machine-parseable where required.
+  - No blocking workflows depend on ad-hoc console-only output.
+
+- [ ] C1. Developer documentation is complete for release operations.
+- [ ] C2. Tool documentation is complete for supported workflows.
+- [ ] C3. Onboarding flow is validated with current repo layout and commands.
+
+## Validation Evidence Requirements (for later BUILD slices)
+- [ ] Full test command(s) and results captured in a release report.
+- [ ] Smoke validation command(s) and results captured.
+- [ ] Any blockers are documented with exact failing command and error surface.
+- [ ] Final release gate summary includes pass/fail per criterion above.
+
+## Notes
+- This PR defines criteria only; it does not claim completion of criteria execution.
+- Status promotion to `[.]` or `[x]` should occur only in execution-backed follow-up BUILD PRs.

docs/dev/reports/change_summary.txt

@@ -1 +1 @@
-Docs-only PR to validate no tool logic leaks into engine
+docs-only

docs/dev/reports/file_tree.txt

@@ -1,4 +1 @@
-docs/pr/BUILD_PR_LEVEL_19_23_ENGINE_TOOL_BOUNDARY_LEAK_VALIDATION.md
-docs/dev/codex_commands.md
-docs/dev/commit_comment.txt
-docs/dev/reports/*
+generated

docs/dev/reports/validation_checklist.txt

@@ -1,4 +1 @@
-[ ] No tool imports in engine
-[ ] No tool assumptions in engine
-[ ] Boundary rules enforced
-[ ] Report generated
+[ ] criteria defined

docs/pr/BUILD_PR_LEVEL_20_1_RELEASE_READINESS_DEFINITION.md

@@ -0,0 +1,16 @@
+# BUILD_PR_LEVEL_20_1_RELEASE_READINESS_DEFINITION
+
+## Purpose
+Define release criteria for production readiness.
+
+## Scope
+- docs-only
+- no implementation
+
+## Codex Responsibilities
+- define measurable release criteria
+- ensure alignment with roadmap
+
+## Acceptance
+- release criteria documented
+- validation checklist created