[singkia]

Prepared and merged

Merged as 0e105404820bb76b3333ae1542321ab7cee77964. All PR checks passed; the merged tree equals the tested head. No tag or Release has been created. The bilingual notes draft below remains pending the final publication confirmation.

Summary

Prepare v1.5.0 after the merged macOS integration in #245:

• Synchronize Cargo workspace/lock, CLI package, Runtime manifest and README version examples with the existing release-preparation script.
• Correct the Chinese Screen Recording Allow description to match the unchanged Rust behavior; document registered default macOS recovery, manual fallback and the explicit legacy ad-hoc signing migration.
• Separate the main-entry VM contract's notification transport from real OS watcher integration. The VM still executes the actual main and responder, keeps the original assertions and deadline, and adds before-notification and watcher-disposal checks. The Node integration suite retains real filesystem events and its withheld-event negative control. No production code, Runtime asset bytes or CI workflow changed.

Validation

• Main-entry + real Node watcher suite: 27 passed; main-entry file repeated 20 times: 220 passed.
• Before version metadata synchronization: complete bun run check passed (718 shared + 451 macOS, 10 existing skips), including dist rebuild equality; typecheck and lint passed with existing warnings.
• After version synchronization: release/version/manifest/architecture contracts 47 passed; committed dist rebuild matches.
• The exact PR head passed check, cargo and windows-cargo on its first CI attempt. Earlier hosted signing failures and VM watcher timeouts remain in feat(macos): integrate update recovery and permission continuity #245's history; neither is relabeled as a production fix.

Release boundary

This PR does not tag, publish binaries, update the tap, or modify the installed App. The public manual remains on the published v1.4.0 baseline until v1.5.0 and its approved bilingual notes actually exist. Publishing requires the repository owner's final confirmation.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-19T11:53:30.079933Z	ea8baf4	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[singkia]

v1.5.0 release notes draft

Pending the final publication confirmation; no tag or Release has been created.

Incodex

Incognito toggle for Codex desktop.

Changelog

1. macOS update recovery: A registered default install attempts to restore its integration after an official Sparkle update while retaining its local signing identity. If integration remains missing, run incodex install against the current app. --app and --clone do not use this recovery path.
2. Two-permission setup: The default macOS install checks Accessibility and Screen Recording in one native guide. Use incodex perm to reopen setup; completion requires fresh confirmation of both grants. Screen Recording reset requires an explicit Allow and a locked fresh check confirming missing access; it does not grant permission.
3. Permission rechecks after updates: Successful Runtime publication and official-update recovery recheck current permissions. Confirmed missing access can reopen the shared guide; unknown stays pending. Automatic checks do not reset permissions or promise continuity across signing changes.
4. Upgrading: Run inc update to update the CLI and bundled Runtime. Existing ad-hoc-signed default macOS installations must explicitly run incodex uninstall, then incodex install once to establish the persistent local signing identity; initial authorization may be needed. Source installations use git pull, cargo install --locked --path crates/incodex-cli, and incodex runtime. Windows Store auto-recovery remains experimental: after an official update, fully quit Codex and run incodex install for the current package generation.

更新日志

1. macOS 更新恢复：已登记的默认安装会尝试在官方 Sparkle 更新后恢复集成，并保留本地签名身份。若集成仍缺失，请针对当前应用运行 incodex install。--app 和 --clone 不使用此恢复路径。
2. 双权限设置：macOS 默认安装通过一张原生向导检查辅助功能与屏幕录制。运行 incodex perm 可重新打开设置；只有新鲜读数确认两项均已授权后才完成。重置屏幕录制登记须明确选择“允许”，并且锁内新鲜复验仍确认缺权；该操作不会授予权限。
3. 更新后重查权限：Runtime 发布成功或官方更新恢复成功后，重新检查当前权限。确认缺权时可重新打开共用向导；unknown 保持待确认。自动检查不重置权限，也不承诺跨签名授权连续。
4. 升级方式：运行 inc update 更新 CLI 及其内置 Runtime。现有默认 macOS 安装若使用临时签名，须显式运行一次 incodex uninstall，再运行 incodex install，建立持久本地签名身份；首次可能需要授权。源码安装使用 git pull、cargo install --locked --path crates/incodex-cli 和 incodex runtime。Windows Store 自动恢复仍属实验能力：官方更新后，请完全退出 Codex，再针对当前包代际运行 incodex install。