Skip to content

Fix release audit findings and prepare 1.2.0-rc.1 - #19

Merged
Sparkz400 merged 1 commit into
mainfrom
codex/stable-release-hardening
Nov 3, 2026
Merged

Sparkz400 merged 1 commit into
mainfrom
codex/stable-release-hardening

Conversation

@Sparkz400

@Sparkz400 Sparkz400 commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner

Fixes the twelve reproducible release-audit defects: session-timeout transitions, empty operator restrictions, manual minimization, lifecycle-script cancellation, scheduler registration, renamed/deleted references, stale HTTP health, unsupported website controls, ineffective appearance options, icon-only display, persisted UI validation, and bounded multiline history.

Settings now save explicitly and offer discard on close; expiry restores the last saved configuration. Compact layouts, inline validation, search coverage, localized audit labels and synthetic screenshots are updated. Schema 12 preserves empty restricted scopes; rollback requires the prior configuration backup. Large-editor work avoids repeated snapshots/list reconstruction, and operation locks have bounded storage.

Validation: 273 .NET and 32 Node tests; final native UI run passed 10,088 assertions with no binding warnings; 30/30 process restore/focus cycles and authenticated recovery passed. Chrome/Edge/Firefox each passed 20 isolated switching cycles; Chromium and Firefox Developer Edition passed full restart recovery. A 10-minute synthetic churn run passed with 59 samples and one abrupt launcher restart. The 500-app editor comparison improved median edit/render from 465.45 to 82.28 ms and total allocation from 1.73 GB to 70.8 MB over 20 cycles (includes harness render delay). The clean f08d2b2 candidate also passed 15 bundled setup assertions, all 23 installer install/upgrade/rollback/uninstall checks, and eight-asset manifest/checksum/SPDX validation. It is intentionally unsigned. Required CI independently validates this revision.

Release automation supports beta/RC/stable with existing integrity/scanner/attestation gates, optional configured publisher signing, and explicit stable qualification records. This is a release candidate: real offline-package, target-workstation, Narrator and publisher-signing acceptance remain pending in docs/release-readiness.json. Development fixtures do not close those gates. Detailed evidence, limits and follow-ups are in docs/RELEASE_RESOLUTION_2026-11-03.md and docs/RELEASE_TODO.md.

@Sparkz400
Sparkz400 merged commit 0472a98 into main Nov 3, 2026
4 checks passed
@Sparkz400
Sparkz400 deleted the codex/stable-release-hardening branch November 3, 2026 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant