Publish and verify codex-sdlc-wizard 1.0.0

[BaseInfinity]

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 and Fable approvals, required CI, tag, package, plugin payload, and release all bind the exact same immutable candidate.
• Tag and publish 1.0.0 through the trusted release workflow.
• Verify the GitHub release, npm package, plugin payload, and clean install from the public artifact.
• Record any release failure as a dedicated issue instead of silently repairing unrelated scope.

Boundary

This issue owns the publish-and-verify operation. 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, consumer default high, with the wizard maintainer repo's explicit xhigh exception.
• 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.

[BaseInfinity]

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.

[BaseInfinity]

1.0 README audience disclosure

Add an honest, prominent audience note during the 1.0 documentation pass. Suggested wording:

Codex SDLC Harness was designed and field-tested by a software engineer with 15+ years of experience for power-user software engineers who are already comfortable with Git, testing, code review, pull requests, and the software delivery lifecycle. It provides strong automation and guardrails, but it is not a substitute for understanding those workflows; mileage may vary for users who are new to SDLC practices.

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]

1.0 tracker synchronization completed and integrated through PR #161 at commit 500384289ffc8ce3bf73fe78200eee1aa967ad5b.

Durable state:

• ROADMAP now contains the complete 54-open-issue snapshot and the explicit #158 -> #109 -> remaining blockers -> Windows acceptance -> #88 publish release order.
• Every open issue has a milestone; unmilestoned count is zero.
• The 1.0.0 milestone is 12 open / 11 closed and its description matches the queue.
• Published v0.7.37, development metadata 0.7.38, and next public 1.0.0 are distinguished.
• fix(review): stop tool-free cross-model reviews when Claude invokes advisor #158 and Implement incremental corrective commits with a final whole-PR review gate #109 have current cold-session comments.

Evidence:

• Roadmap regression: RED on stale/masked ordering, then 14/14 GREEN.
• Canonical proof: 11/11 GREEN on the final tree.
• One reviewer-driven corrective round fixed queue-scoped order lookup; final Sol High + Fable High joint verdict: CERTIFIED.
• PR-head Windows check and post-merge main Windows check both passed.

This synchronization does not close #88. The next release slice remains #158.