fix: preserve desktop settings and validate beta.9 artifacts - #40
Merged
Conversation
devswha
marked this pull request as ready for review
September 6, 2026 06:48
devswha
marked this pull request as draft
September 6, 2026 07:10
devswha
marked this pull request as ready for review
September 6, 2026 07:35
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.
Desktop UI preferences were lost whenever the supervised server received a new loopback port. The desktop now records its first verified server port and reuses that origin across launches, while rotating authentication secrets and retaining PID/health checks. An occupied or invalid saved port enters recovery instead of adopting another server.
This also preserves streaming tool metadata, errors, text and running state across partial updates. The model picker dismisses on Escape without bypassing global Stop. Ctrl+Enter guidance occupies a separate row so long or invisible text cannot squeeze toolbar controls; typing preserves their positions. macOS acceptance gets explicit isolated server/WebKit profiles; QA windows use the public builder setter because the pinned runtime drops the UUID during configuration conversion. Profile locks and path validation prevent competing or invalid launches from modifying profile data.
Release preparation advances to beta.9 / desktop 0.2.3. Linux server archives gain exact-source builds and authenticated runtime/data-survival checks on Ubuntu 22.04 and 24.04. Desktop artifact checkouts are pinned to the reviewed commit. The local release verifier now checks the actual gajae-app-server package identity, sharing that constant with the builder and smoke harness.
Validation: full npm run verify and all 16 GJC/browser/clone/native E2Es passed on 828d986. All eight PR checks passed, including both Linux packaging lanes and both Ubuntu versions. Independent adversarial review verified the QA isolation fixes and accepted the persisted-origin guards. Real signed-app GUI checks confirmed settings/project persistence, same-origin profile separation, rejection of an occupied port with zero foreign requests, Retry recovery and complete child-process shutdown. The corrected toolbar remains horizontal while typing with Ctrl+Enter enabled. The exact-head beta.9 release is published with the macOS DMG, Linux deb/AppImage and server archive plus all four checksums. App and DMG notarization, mounted/quarantined-copy signatures and Gatekeeper, packaged-server/data-survival checks, installed-copy GUI and remote release-asset verification all passed before publication.
OMG skill execution is excluded from this acceptance scope. Historical issue #3 is not declared resolved by the app transport fixes. Hosted signing still requires owner-provided secrets; local release preparation uses the existing identity and notary profile without exporting credentials. No announcement is sent by the new archive workflow.