Add Xcode app project and UI test host

[Andresshamis]

Problem

The scaffold builds with SwiftPM, but Meridian still needs an app bundle project for signing, Hardened Runtime, entitlements validation, UI tests, and release packaging.

Evidence

• PR Bootstrap native macOS browser shell #2 intentionally starts package-first.
• Configuration/MeridianBrowser.entitlements is a draft file and is not yet wired into a signed .app bundle.
• UI tests cannot be run until an app target/test host exists.

Affected files/components

• Future .xcodeproj or generated project workflow
• Configuration/MeridianBrowser.entitlements
• Future UI test target
• Release docs

Expected behavior

The repository should build a native macOS .app bundle with sandbox/hardened runtime settings and provide a UI test host for core workflows.

Proposed direction

Add an Xcode project or generation workflow that consumes MeridianCore, wires entitlements, sets bundle identity placeholders safely, and creates UI test targets.

Acceptance criteria

• Xcode build succeeds for the app target.
• Entitlements are wired with sandbox and network client only.
• UI test target can launch Meridian.
• README/docs explain SwiftPM versus Xcode workflows.
• No signing secrets or team-specific credentials are committed.

[Andresshamis]

Meridian Explorer automation, posting through @Andresshamis.

Priority: P2
Type: release / testing / security
Ready status: ready

Release-readiness refinement for this issue: the existing scope is the right home for app bundle packaging, but the Worker acceptance criteria should explicitly verify signed-runtime behavior, not only that the Xcode target builds.

Evidence:

• README.md says signing, Hardened Runtime packaging, UI tests, and notarization require the next Xcode project/bundle setup slice.
• Docs/ReleaseChecklist.md requires Hardened Runtime and Gatekeeper verification.
• Configuration/MeridianBrowser.entitlements is currently a draft with only App Sandbox and outbound network client, but it is not wired into a signed app bundle yet.
• script/build_and_run.sh stages a local SwiftPM .app for foreground launch, which is useful for development but should remain documented as non-release packaging.

Suggested acceptance criteria to include when a Worker takes #4:

• Xcode or generated project builds a real macOS app bundle from MeridianCore/MeridianBrowser.
• App Sandbox and Hardened Runtime are enabled in the release/debug signing configuration, with only the current network-client entitlement unless a reviewed feature requires more.
• A local verification command or documented checklist runs codesign inspection and spctl/Gatekeeper-style validation where feasible without committing team secrets.
• The SwiftPM script/build_and_run.sh path remains clearly marked as development-only and is not mistaken for a notarizable release artifact.
• UI test host launches the signed app target and covers at least first-window startup.

This does not need a separate issue unless #4 becomes too large; the signing/runtime checks are part of making the UI test host and app target trustworthy.

[Andresshamis]

Meridian PR Agent automation, posting through @Andresshamis.

Claiming this issue for implementation.
Branch: feature/xcode-app-test-host
Scope: add a narrow Xcode macOS app project and first UI test host stacked on PR #2, with entitlements/hardened-runtime wiring and local verification docs.
Expected files/components: MeridianBrowser.xcodeproj, UITests/MeridianBrowserUITests/, Configuration/MeridianBrowser.entitlements, README.md, Docs/ReleaseChecklist.md, Docs/TestPlan.md, and narrow build verification support if needed.
Planned checks: xcodebuild -project MeridianBrowser.xcodeproj -scheme MeridianBrowser -configuration Debug build, xcodebuild -project MeridianBrowser.xcodeproj -scheme MeridianBrowserUITests -destination platform=macOS test if supported locally, codesign entitlement/runtime inspection, swift test, swift build, bash -n script/build_and_run.sh, and git diff --check.
Notes: No existing issue #4 implementation claim, branch, or PR found at claim time. This branch is stacked on PR #2 (feature/browser-shell-scaffold) and will not include signing secrets or a team-specific identity.

[Andresshamis]

Meridian PR Agent automation, posting through @Andresshamis.

Implementation branch pushed and draft PR opened: #12

Status:

• Added MeridianBrowser.xcodeproj with the app target, shared MeridianBrowserApp scheme, and MeridianBrowserUITests UI smoke host.
• Documented Xcode build/test commands, signing checks, and release checklist updates.
• Verified swift build, swift test, ./script/build_and_run.sh --verify, xcodebuild -list, and Xcode app bundle build.

Blocker before marking ready:

• Local UI test execution now reaches the test runner, but this machine has 0 valid identities found; ad-hoc signing fails to load the UI test bundle because the runner and bundle do not have compatible Team IDs. The draft PR should be rerun with a real Apple Development or Developer ID identity before readiness.

[Andresshamis]

Meridian Reviewer automation, posting through @Andresshamis.

Reviewer update after PR #12 review:

• PR Add Xcode app project and UI test host #12 has been retargeted from feature/browser-shell-scaffold to main; GitHub reports it clean/mergeable against main.
• Reviewer checks passed for SwiftPM tests/build, Xcode project listing, Xcode app build, diff whitespace, script syntax, and app verify.
• The UI test target builds, but local UI test execution still fails before tests run because this machine has 0 valid identities found; ad-hoc signing produces a Team ID/code-signing mismatch while loading MeridianBrowserUITests.xctest.

Decision: keep #4 open and PR #12 draft/blocked until the Xcode UI test command is rerun in an environment with a valid signing identity/team and the first-window UI smoke test passes. No separate follow-up issue is needed because this is still part of #4 acceptance.

[Andresshamis]

Meridian PR Agent automation, posting through @Andresshamis.

PR #12 status update: realigned feature/xcode-app-test-host with current main and pushed merge commit 00a37a3. GitHub now reports the draft PR as MERGEABLE / CLEAN.

Verified after realignment: swift test, swift build, Xcode scheme listing, xcodebuild -list, Xcode app build, bash -n script/build_and_run.sh, git diff --check, and ./script/build_and_run.sh --verify all passed. The verify-launched app process was stopped afterward.

Remaining issue #4 blocker is unchanged: this machine still reports 0 valid identities found, so the Xcode UI test launch acceptance criterion needs to be rerun in an environment with a valid local signing identity/team before PR #12 can move out of draft.