release: v1.1 (build 6)

[LeoHChen]

Tracking issue: #128.

What this is

A small App Store submission build over the same v1.1 release. No new tag, no marketing-version bump — we're shipping 1.1 (6) against the same v1.1 GitHub release, per the user decision recorded on #128.

Changes in build 6 (vs build 5)

Commit	Layer	Notes
f2b1d34	docs only	Public TestFlight link in README + landing
206beba	docs only	Non-tech setup guide (docs/getting-started.html)
8c4c3f0	app code	Quiet llama easter egg in About (5 taps on the Version row)
ea3eab7 add9d9e eb29086	CI / agent docs only	Release-agent workflow polish

Plus this PR's own edits:

• project.yml: CFBundleVersion 5 → 6 (main app + Live Activity); ITSAppUsesNonExemptEncryption: false on the main app so App Store Connect auto-answers export-compliance going forward.
• xcodegen generate (Info.plist regenerated to match).
• README: v1.1 build 6 — 2026-05-09 subsection under the existing v1.1 release notes.
• Stages the v1.1 App Store screenshots (originals at docs/screenshots/v1.1/*.jpg, sips-padded 1320×2868 set under docs/screenshots/v1.1/appstore/).

docs/index.html is unchanged — no user-visible feature changes since v1.1 shipped.

Security review

Walked the criteria from the release-agent prompt against git diff v1.1..HEAD plus this PR's own edits.

• Hardcoded secrets / API keys / tokens — none.
• .env-style files — none committed.
• New outbound network calls — none. The new docs page (getting-started.html) only links externally with target="_blank" rel="noopener". The TestFlight URL in README + landing resolves to testflight.apple.com/join/y4Nmt7V1 (legitimate Apple TestFlight invitation domain).
• New file-system writes outside the sandbox / drive scope — none. The llama easter egg is a stateless Canvas drawing — no I/O, no URLSession, no FileManager. The SettingsView change adds an in-memory tap counter that resets on .onDisappear.
• New WKWebView / external-URL flows — none.
• New URLSession configurations that disable TLS validation — none.
• Entitlement / privacy-plist changes that broaden access — only addition is ITSAppUsesNonExemptEncryption: false, which narrows the export-compliance attestation (declares no non-exempt cryptography is used). The app continues to use only standard OS-provided HTTPS for the existing opt-in album-art / artist-photo fetchers.
• New third-party Swift packages — none. Still just ZIPFoundation.
• Weakened availability guards around Apple Intelligence — none touched.
• Security-scoped bookmark lifecycle regressions — none touched.
• ExportOptions.plist — already-tracked since add9d9e. No compileBitcode / signingCertificate / TLS-disabling fields; just app-store method, team 79DDZ6D8WT, automatic signing.

No [BLOCKING] findings. No [ADVISORY] findings. Clean.

Smoke pass — TESTING.md Section A

Run on iPhone 17 simulator (iOS 26.4, ID 53741523-1988-4492-8737-D8173B9B5F6C):

• xcodegen generate produces no diff in project.pbxproj after re-running. (Verified — second invocation idempotent.)
• xcodebuild build … -configuration Debug is green with zero new warnings. (Build log grepped for warning: / error: returned nothing.)
• App cold-launches to the Library tab without crashing. (Screenshotted — For You / Smart Play + Browse (All Tracks / Artists / Albums / Language / Folders) all render against the Charcoal Phosphor backdrop.)
• Launch screen renders the branded gradient (verified visually after simctl launch).
• git status clean before commit (no .DS_Store / build artifacts).
• Settings → About surfaces real Version / Build / Commit / Tag / Built-at via the existing build-time Info.plist injection script (unchanged this build).

Spot-check: llama easter egg is a stateless Canvas view in LlamaSilhouette.swift revealed by 5 Version-row taps within 2s in SettingsView. Diff reviewed; tap counter resets on .onDisappear and on window-exceeded. No persistence, no network, no file I/O.

Workflow note

Per project policy, wait for the designer agent's Codex review before merging. After merge: archive, export, upload to App Store Connect via xcrun altool using the API key already at ~/.appstoreconnect/private_keys/AuthKey_SRTMB3ZZUN.p8. The user will attach build 6 to the v1.1 listing and click Submit themselves — release agent stops at upload.

After upload, will amend the existing v1.1 GitHub release notes with a "Build 6 (2026-05-09)" subsection. Will not move the v1.1 tag.