Repository navigation
Publish and verify codex-sdlc-wizard 1.0.0 #88
Description
Goal
Publish the verified 1.0.0 trust-contract release and confirm that every public release surface serves the same artifact.
Acceptance criteria
- Merge all required 1.0.0 release-blocking issues in milestone order.
- Bump and verify package/plugin version alignment.
- Run the full proof suite once for the frozen release candidate and required independent release checks.
- Confirm Sol High and Fable High approvals, required CI, tag, package, plugin payload, and release all bind the exact same immutable candidate.
- Confirm Run the frozen 1.0 candidate on real Windows Codex Desktop and CLI #79 passed against that exact candidate, including Codex Desktop install/enable/update/restart, single-workflow picker discovery, and real-Windows evidence.
- Tag and publish 1.0.0 through the trusted release workflow.
- Verify the GitHub release, npm package, plugin payload, and clean installation through the supported Codex Desktop and Codex CLI paths.
- Record any release failure as a dedicated issue instead of silently repairing unrelated scope.
Boundary
This issue owns the publish-and-verify operation. #79 owns the final hardware-dependent Codex Desktop and CLI acceptance gate. Plugin Directory submission remains tracked by #66.
1.0 documentation and compatibility gate
- Put the certified model baseline in the README first screen: GPT-5.6 Sol at High for consumers and this wizard maintainer repo; a different implementation effort requires a current explicit user request for that bounded run.
- State that older Codex/model combinations are best-effort unless covered by the release matrix; do not claim unsupported compatibility.
- Point users who require the prior contract to the last compatible pre-1.0 release.
- Keep README, install/update guidance, release notes, npm metadata, plugin metadata, generated repo-local skill, and templates consistent.
- Document the migration from the pre-1.0 review/proof behavior and confirm update preserves consumer customizations.
- Complete a release documentation readback at the milestone boundary; docs are part of the candidate, not a follow-up.
Activity
BaseInfinity commentedon Aug 8, 2026
Release sequencing updated by maintainer on 2026-08-08: publish and verify 0.7.36 after all automated tests/CI and review gates pass; real-Windows Desktop/CLI acceptance in #79 may run against the published package afterward. Red required CI still blocks publishing. A post-release Windows defect becomes a follow-up patch release rather than requiring manual E2E before this publish.
[-]Publish and verify codex-sdlc-wizard 0.7.36[/-][+]Publish and verify codex-sdlc-wizard 1.0.0[/+]BaseInfinity commentedon Aug 16, 2026
1.0 README audience disclosure
Add an honest, prominent audience note during the 1.0 documentation pass. Suggested wording:
Keep this informative rather than exclusionary: link the install path and workflow explanation immediately afterward, and avoid implying that less-experienced users cannot use the project. Also ensure the major-release README accurately identifies the supported Sol 5.6 / Codex CLI baseline and points older host/model users to a compatible prior release when necessary.
BaseInfinity commentedon Aug 18, 2026
1.0 tracker synchronization completed and integrated through PR #161 at commit
500384289ffc8ce3bf73fe78200eee1aa967ad5b.Durable state:
#158 -> #109 -> remaining blockers -> Windows acceptance -> #88 publishrelease order.v0.7.37, development metadata0.7.38, and next public1.0.0are distinguished.Evidence:
mainWindows check both passed.This synchronization does not close #88. The next release slice remains #158.
BaseInfinity commentedon Aug 22, 2026
1.0 release audit (2026-08-22): the milestone is now limited to nine defensible blockers in this order: #158 → #157 → #109 → #141 → #127 → #92 → #93 → #79 → #88.
#124, #131, and #147 moved to 1.1.0; #164 now owns provider heartbeat UX. Freeze the release candidate only after the seven software blockers integrate. #79 remains the real-Windows human gate and this issue remains the terminal publish/immutable-artifact verification gate.