Skip to content

Add production macOS app wrapper - #1

Draft
melonamin wants to merge 1 commit into
mainfrom
bb/implement-quackridge-macos-app-thr_isai9cxy4t
Draft

melonamin wants to merge 1 commit into
mainfrom
bb/implement-quackridge-macos-app-thr_isai9cxy4t

Conversation

@melonamin

Copy link
Copy Markdown
Member

Summary

  • add management protocol v2, bounded local IPC, transactional configuration/credential state, recovery metadata, lifecycle supervision, certificate storage, and secure ODBC property handling
  • add the native SwiftUI menu-bar and manager app with onboarding, source management, pairing, diagnostics, settings, manifest verification, and app-owned backend supervision
  • add unsigned packaging, backend/lifecycle smoke gates, privacy/accessibility audits, protocol fixtures, compatibility documentation, and the preserved implementation plan
  • retain existing CLI behavior and Linux/Windows portability for shared Go packages

Why

QuackRidge needs a production macOS wrapper that can safely own one per-user backend and manage source configuration without exposing credentials, weakening the local trust boundary, or breaking existing command-line workflows.

Impact

This is a large additive feature. Existing CLI entry points remain available, while live operations can coordinate with an app-owned backend. macOS release packaging gains explicit architecture, ODBC, Hardened Runtime, signing, and notarization gates rather than assuming those environments are available.

Validation

Passed on the ARM64 macOS worktree:

  • make check
  • make integration
  • make e2e
  • make macos-backend-smoke (exact pinned ARM64 extensions and app-owned lifecycle)
  • make macos-privacy-audit
  • make macos-accessibility-audit (static audit)
  • plist/XML/shell syntax checks and git diff --check
  • targeted Windows and Linux cross-compilation for the portable config/control paths
  • iterative Codex reviews; accepted serious findings were fixed and the full Go check matrix was rerun

Remaining release gates

  • Full Xcode is not installed on this host, so make macos-app-unsigned, make macos-test, and UI tests could not run here.
  • Signing and notarization are intentionally deferred and are not represented as passing.
  • Native Intel, mounted final-DMG, representative external ODBC driver, and manual accessibility/macOS-version acceptance remain release gates.

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