chore(release): prepare VaultSync 2.0.0 build 36

[psimaker]

What & why

Release-readiness for 2.0.0 / build 36 per issue #97 (no auto-close; the issue closes only after public availability): version and build bumped in both targets, CHANGELOG section ## [2.0.0] added with the Controlled Diagnostics roundtrip check as the headline entry. StoreKit product IDs, bundle IDs, signing, and entitlements are untouched.

Verification at this exact tree

• cd go && make patch && go test -tags noassets ./bridge -count=1: green (real Syncthing instances)
• XCFramework rebuilt from this exact tree (make xcframework)
• Complete iOS plan against the fresh framework: 431 tests / 438 runs, zero failed/skipped
• Release-configuration simulator build: green
• notify suite + vet + gofmt: green
• relay suite at the deploy candidate bd81752 (separate repo): green, build ok
• Design-token, strings-parity (884 keys), sync-proof privacy lints: green
• Internal WHATS-NEW-2.0.0 (en/de/es/zh-Hans) prepared in the gitignored appstoremetadata directory — not part of this diff by design
• Physical-device/TestFlight smoke: not executed — owner-approved physical-device waiver (2026-07-15); substitute evidence per the readiness audit

Component(s)

• ios (version/build only)
• docs (CHANGELOG)

Summary

• Prepared VaultSync 2.0.0 build 36 for release, updating app and widget versions.
• Added a Controlled Diagnostics end-to-end roundtrip workflow to the changelog, including localized availability.
• StoreKit product IDs, bundle IDs, signing, and entitlements remain unchanged; no privacy or security behavior changes.
• No background execution or regular sync behavior changes.
• Verification passed across Go, XCFramework generation, iOS tests, simulator release builds, formatting, relay, design tokens, strings parity, and sync-proof privacy checks.
• Physical-device and TestFlight smoke testing were not performed under an owner-approved waiver.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d795a5ac-dceb-4e83-860b-25267aacc010

📥 Commits

Reviewing files that changed from the base of the PR and between a126ac9 and 2a52a8b.

📒 Files selected for processing (2)

• CHANGELOG.md
• ios/project.yml

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (4)

**/*

⚙️ CodeRabbit configuration file

**/*: VaultSync syncs private Obsidian notes through Syncthing. Treat data loss,
privacy leaks, security regressions, and broken sync behavior as high priority.
Do not nitpick formatting unless it affects maintainability, correctness, or public API clarity.
Flag any accidental logging, telemetry, crash reporting, or network transfer of note contents,
vault paths, filenames with private context, API keys, APNs tokens, relay keys, or security-scoped bookmark data.

Files:

• ios/project.yml
• CHANGELOG.md

ios/project.yml

⚙️ CodeRabbit configuration file

ios/project.yml: This generates the Xcode project and Info.plist. Review changes for bundle ID,
entitlements, background modes, URL schemes, signing settings, and accidental secret exposure.

Files:

• ios/project.yml

**/*.{md,sh,go,swift}

📄 CodeRabbit inference engine (README.md)

Keep Relay-side request observation and wake-ups received on the iPhone as separate diagnostics evidence; one must not be treated as proof of the other.

Files:

• CHANGELOG.md

**/*.md

⚙️ CodeRabbit configuration file

**/*.md: Review public documentation for technical accuracy, privacy/security claims, App Store-facing wording,
setup correctness, and consistency with the free app plus optional Cloud Relay subscription model.

Files:

• CHANGELOG.md

🔇 Additional comments (2)

CHANGELOG.md (1)

7-12: LGTM!

ios/project.yml (1)

67-68: LGTM!

Also applies to: 141-142

---

📝 Walkthrough

Walkthrough

The changelog now documents the 2.0.0 release, while the VaultSync app and widget targets move to version 2.0.0 with build 36.

Changes

2.0.0 Release Metadata

Layer / File(s)	Summary
Versioned release update CHANGELOG.md, ios/project.yml	Adds the dated 2.0.0 changelog entry and updates both iOS targets from version 1.8.2/build 35 to 2.0.0/build 36.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related issues

• Issue 97 — Matches the 2.0.0 release milestone, including both target version bumps and the changelog entry.

Poem

Two targets climb to version two,
A changelog marks the launch anew.
Build thirty-six takes flight,
Release notes shine bright—
Metadata neatly aligned.

🚥 Pre-merge checks | ✅ 7

✅ Passed checks (7 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title uses conventional-commit style and clearly matches the release-preparation changes for VaultSync 2.0.0 build 36.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
No Private Note Leakage	✅ Passed	Touched files are changelog and build config only; no new runtime logging, analytics, network, or secret-bearing data paths were added.
Bounded Ios Background Work	✅ Passed	PASS: This PR only bumps versions/changelog; no Swift background-execution code changed. The existing background service already uses deadlines, Task.isCancelled, and expiration handlers.
Bridge Contract Compatibility	✅ Passed	Diff only touches CHANGELOG.md and ios/project.yml; no Go/Swift bridge code, types, or tests changed, so the bridge contract is unaffected.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/release-readiness-2.0.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}