release: prepare VaultSync 2.0.0 (build 36)

[psimaker]

VaultSync soll den formalen Versionssprung erst erhalten, wenn der definierte 2.0-Funktionsumfang releasefähig und vollständig freigegeben ist. Dieses Issue bündelt ausschließlich den späteren Versions-, Metadaten- und Release-Readiness-Meilenstein.

• ios/project.yml: App und Widget auf 2.0.0 / Build 36 setzen
• cd ios && xcodegen generate ausführen
• CHANGELOG.md um einen Abschnitt 2.0.0 ergänzen
• Internes appstoremetadata/WHATS-NEW-2.0.0.md für en/de/es/zh-Hans erstellen
• Beide Target-Versionen und Buildnummern identisch halten
• StoreKit-, Signing-, Bundle-ID- und Entitlement-Werte unverändert lassen
• XCFramework neu bauen, falls die Go-Bridge seit dem letzten Release geändert wurde
• Vollständigen Xcode-Build und Testlauf ausführen
• Go-, Notify- und Relay-Tests entsprechend den seit 1.8.2 geänderten Bereichen ausführen
• Design Token Lint ausführen
• Strings Key Parity ausführen
• Privacy-, Marketing- und Screenshot-Prüfung abschließen
• Compatibility Matrix für alte/neue App, Relay und Notify dokumentieren und prüfen
• Release- und Rollback-Runbook fertigstellen
• Kein Tag oder Deployment vor vollständiger Freigabe erstellen bzw. ausführen

[psimaker]

Release-readiness landed via #130 (squash 131d3f7), gated by the engineering readiness audit (#129, docs/engineering-readiness-2.0.md).

Evidence (exact release tree): XCFramework rebuilt from the release tree; complete iOS plan 431 tests / 438 runs, zero failed/skipped, against that framework; Release-configuration simulator build green; Go bridge suite (real Syncthing instances), notify suite, and relay suite at deploy candidate bd81752 green; design-token, strings-parity (884 keys), and sync-proof privacy lints green.

Privacy/marketing/screenshot review: App Privacy answers unchanged (the diagnostics check adds no data collection and never leaves the device toward Relay or Apple); existing screenshots remain accurate (the new check is an additive Settings surface); promotional text unchanged; internal WHATS-NEW-2.0.0 prepared for en/de/es/zh-Hans in the gitignored metadata directory.

Compatibility matrix and release/rollback runbook: recorded in docs/engineering-readiness-2.0.md (rollout order helper → relay → app, both rollback directions, staged-rollout abort criteria).

Physical device / TestFlight smoke: not executed — owner-approved physical-device waiver (2026-07-15); substitute evidence is the fresh simulator plan, Release-configuration build, and isolated two-instance Syncthing E2E runs recorded in the audit.

The last checkbox stays open until the tag, store submission, and controlled release complete; this issue closes only after 2.0.0 (36) is publicly available.

[psimaker]

Status 2026-07-15: Build 36 (2.0.0) was uploaded from the exact release commit 131d3f7 (tag v2.0.0, version-check green) and manually submitted to App Store review by the owner. Helper 2.0.2 and Relay 1.3.1 (6bdad72, health verified in production) are already rolled out — release order helper → relay → app holds.

Remaining before this issue closes: Apple review, (phased) release, public availability of 2.0.0/36 verified via the store, and the monitoring window from the readiness audit's abort plan. The physical TestFlight smoke stays not executed — owner-approved physical-device waiver (2026-07-15) with recorded substitute evidence.

[psimaker]

Closing — VaultSync 2.0.0 (build 36) is publicly available and the monitoring window completed without meeting any abort criterion.

Release: tag v2.0.0 → 131d3f75a42bfe9c9dbb9dfae98a6c1331572e31 (squash of #130); app and widget both at 2.0.0 / build 36; version-check green. Public availability verified 2026-07-22 via the iTunes lookup API for eu.vaultsync.app: version 2.0.0, release date 2026-07-22T05:14:13Z, identical on the DE, US, and AT storefronts.

Artifacts & digests:

• Helper: tag notify-v2.0.2 → 42cadb2920fa7bc0a3199bf1d6baaca7d46d0dbd; ghcr multi-arch index digest sha256:97d866c56b8172fa200d823b0ff77890b9774af67138d758fda00af274239a9d (re-verified against the registry today).
• Relay: 1.3.1 (6bdad72) was the deploy of this release train; production has since moved to 1.3.2 (5f7415b, 2026-07-21 — production provisioning repair, bug(relay): new paid subscription cannot provision against relay 1.3.1 #133); health {"status":"ok","version":"1.3.2"}.
• App: build 36 archived from the exact release commit and uploaded 2026-07-15 ("Upload succeeded"; the SyncBridge.framework dSYM warning is expected for gomobile output); submitted to review manually by the owner. Rollout order helper → relay → app held.

Test & simulator evidence (exact release tree 131d3f7): XCFramework rebuilt from the release tree; complete iOS plan 431 tests / 438 runs, zero failed or skipped, against that framework; Release-configuration simulator build green; Go bridge suite (real Syncthing instances), notify suite, and relay suite green; design-token, strings-parity (884 keys), and sync-proof privacy lints green; E2E in isolated two-instance Syncthing runs recorded in the readiness audit.

Physical-device evidence: not executed — owner-approved physical-device waiver (2026-07-15). Substitute evidence: fresh simulator plan, Release-configuration build, and the isolated Syncthing E2E runs (docs/engineering-readiness-2.0.md).

Rollback / forward recovery: helper rollback and forward recovery proven in both directions during the publication train; relay pre-deploy backup image backup-20260715 recorded with the compose rollback procedure; the app is covered by the phased-release halt path — the shipped diagnostics surface stays dormant without explicit pairing, and no server-side dependency regresses 1.8.2 users.

Monitoring window (abort plan in docs/engineering-readiness-2.0.md): 2026-07-22, 05:14 UTC (public availability) → ~10:05 UTC. Relay health ok (1.3.2) throughout the checks; relay logs inside the window: 0 ERROR, 0 WARN, live APNs push accepted traffic; production provisioning writing verified rows (latest 05:40 UTC today). No data-safety regression report against 2.0.0, no crash-loop report in the release build, no relay degradation attributable to the new app. Known issue #135 was reported against 1.8.2 (2026-07-19) — pre-existing, not a 2.0.0 regression; its identity fail-closed fix is already merged on main (#138) toward 2.0.1.

Final checkbox: ticked — no tag or deployment happened before full clearance: the tag, uploads, and deploys all followed the green readiness-audit gates and the owner's explicit GO, and the owner submitted build 36 to review manually.