[codex] gate update checks and pointer persistence#77
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adopts the current pointer-app tranche into a branch and makes the release story stricter instead of broader.
release-source-state-check, so public release gates require a clean committed tree and a rebuilt app/DMG newer than the commit being certifiedWhy
Research showed
NSCursor.set()and AppKit cursor rectangles are not a durable system-wide pointer replacement. Other apps can reset cursor state through their normal cursor-update behavior, so the least-permission path is a supervised reapply mechanism before any privileged helper or private API route.Update checks are also a network action, so they now require explicit Settings consent and a user-initiated check.
Validation
swift test --package-path apps/macospassed: 216 tests, 0 failures./scripts/check-monorepo-references.sh && ./scripts/check-website-boundary.sh && ./scripts/check-distribution-boundary.sh && ./scripts/check-compatibility-boundary.sh && ./scripts/check-local-first.sh && ./scripts/check-app-ui-contract.shpassedgit diff --checkpassedbash -n apps/macos/Scripts/release-source-state-check.sh apps/macos/Scripts/release-readiness.sh apps/macos/Scripts/north-star-audit.sh scripts/check-local-first.sh scripts/check-app-ui-contract.shpassedapps/macos/Scripts/release-source-state-check.sh --app apps/macos/.build/release/CursorDesigner.app --dmg apps/macos/CursorDesigner.dmgcorrectly fails after this commit because the existing signed artifact predatesead3856Release Blocker
This PR intentionally does not mark the product mass-production ready. After merge, the signed DMG must be rebuilt, signed, notarized, stapled, release metadata updated if needed, and manual release evidence completed against that same Gatekeeper-accepted artifact before
make north-star-auditcan pass.