[hm21]

Description

Upgrades the pinned toolchain from Flutter 3.44.9 / Dart 3.12 to Flutter 3.47.2 / Dart 3.13.2, and upgrades the release CLI from Shorebird 1.6.117 to Shorebird 1.6.120. Shorebird 1.6.120 bundles and supports Flutter 3.47.2, so local, CI, and store release builds now use a compatible pair.

Dart 3.13 rejects the constructor syntax emitted by Freezed 3. Freezed 4 cannot currently coexist with this workspace dependency graph, so the four legacy state models are handwritten as Equatable values and Freezed leaves the dependency graph.

Compatibility preserved

• Nullable copyWith fields retain the omitted-versus-explicit-null distinction.
• Collection getters remain unmodifiable.
• Collection getters also keep comparing equal when the underlying collection did not change. dart:collection's views compare by identity, so a getter that allocates one per read tells every select watcher that the field changed on every unrelated state change — curationProvider.select((state) => state.editorsPicks) is the one such watcher in the tree today. Freezed's three EqualUnmodifiable*View wrappers are restored next to the state models for exactly that reason, and copyWith passes the raw field so a long-lived state no longer accumulates one delegating view per copy.
• Equatable retains deep collection equality.
• Regression tests pin those contracts, including clearing a stale feed error. The tests build their fixtures from mutable collections: a const collection is already unmodifiable, so const fixtures would have stayed green even with the wrappers removed.

Native release safeguards

Flutter 3.47 changed the generated iOS Swift package floor. Both the Xcode pre-build action and Codemagic now call one version-aware helper that raises any generated floor below iOS 16, preserves newer floors, and fails clearly on an invalid manifest. This was verified with flutter build ios --config-only on Flutter 3.47.2.

Additional upgrade work

• Resolves the analyzer findings introduced by Dart 3.13.
• Applies Dart 3.13 formatter output in an isolated commit.
• Regenerates the two affected Ubuntu golden references through the golden workflow.
• Aligns the remaining nostr_sdk Flutter constraint.
• Relocks the reduced service god-file ceilings.
• Removes obsolete Freezed instructions and hook behavior from active developer and agent documentation.

Everyone needs to re-run cd mobile && mise run setup_hooks after this merges. Git hooks are generated copies, so an already-installed pre-commit/pre-push hook keeps looking for *.freezed.dart files that no longer exist. The same edit also drops *.mocks.dart from the changed-file scan, which is unrelated to Freezed and is called out here rather than buried: generated mocks now no longer select tests to run in the pre-push hook.

Related Issue: Closes #7354

Out of Scope

• The 59 packages uniformly declaring sdk: ^3.11.0; this is not version drift and has no effect inside this workspace.
• hive_ce_generator remains on its current constraint because the state migration removes the conflicting Freezed requirement.
• Publishing an App Store or Shorebird production release. Release creation remains a deliberate maintainer action after physical-device acceptance.

Verification

• Flutter 3.47.2 / Dart 3.13.2 installed and used locally
• Shorebird 1.6.120 exact revision verified to bundle and list Flutter 3.47.2
• flutter analyze lib test integration_test tools packages — clean
• Changed-file pre-push suite — 4,913 passed, 4 skipped, 0 failed
• State compatibility, feed refresh, and iOS pre-build tests — 38 passed
• iOS floor and Codemagic configuration tests — 41 passed
• dart run build_runner build — generated output clean
• flutter build ios --config-only — succeeds and generates an iOS 16 package floor
• flutter build apk --debug — succeeds
• Service god-file ratchet and repository configuration checks — pass
• Rebased onto current main; repository-wide dart format reports no changes and the async-safety, skip, placeholder, ungrouped-test, layer-direction and unpinned-assertion ratchets all pass on the rebased tree
• Physical Samsung Galaxy S25 (SM-S942B, Android 16) branch smoke test — launch, navigation, camera/microphone permissions, recording, upload, feed playback and app restart all pass
• A full local app run completed 19,866 tests; the only six failures were three Linux-reference goldens run on macOS and three networked manual acceptance cases. The changed-file suite and GitHub platform lanes are the authoritative gates for those environments.

Release gates

Both pre-ready gates are now met. The takeover commits have been reviewed (see the follow-up commits on top of them), and the branch build was smoke-tested on a physical Samsung Galaxy S25 (SM-S942B, Android 16): launch and basic navigation, camera and microphone permission flows, recording, upload, feed playback, and app restart all behave correctly. A screen recording follows in the comments.

The store workflows intentionally refuse to create Shorebird releases from non-main branches. After merge, but before any public promotion, a maintainer must build the Shorebird-enabled artifacts from main and validate the exact internal artifacts:

• Physical iPhone/TestFlight: launch, camera/microphone, recording, upload, feed playback, and app restart
• Samsung Galaxy/Play internal: launch, camera/microphone, recording, upload, feed playback, and app restart
• Confirm both candidates use Shorebird 1.6.120 / Flutter 3.47.2

If either internal artifact fails, do not promote it; fix the failure through a new PR and cut a new internal build.

Type of Change

• ✨ New feature
• 🛠️ Bug fix
• ❌ Breaking change
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[NotThatKindOfDrLiz]

@hm21 Pulling this back to draft while I figure out how it interacts with Shorebird and whether we need to do the updates in tandem. Thanks for your patience.

[NotThatKindOfDrLiz]

@hm21 I pushed the clear, low-risk remediation directly to this branch and updated the PR description. The automated checks are green.

The takeover changes:

• pin Codemagic to Shorebird 1.6.120, whose bundled Flutter is 3.47.2 / Dart 3.13.2
• make the iOS Swift-package deployment-floor repair version-aware and cover it with tests
• preserve the former Freezed state contracts, including explicit-null copyWith behavior and collection immutability, with regression tests
• align nostr_sdk's Flutter constraint, relock the reduced service-size ceilings, and remove stale active Freezed guidance/hooks

Please keep this PR in draft until you complete and document the remaining release-critical physical-device acceptance:

1. Samsung Galaxy: camera, recording, upload, and feed playback.
2. Physical iPhone using the release/TestFlight candidate: launch, camera and microphone permission flows, recording, upload, and feed playback.
3. Record that the tested release candidate was built with Shorebird 1.6.120 / Flutter 3.47.2.

Please also review the commits I pushed before marking the PR ready. No App Store or Shorebird release has been created by this takeover.

Superseded to separate the achievable pre-merge device gate from post-merge TestFlight and Play internal validation.

[NotThatKindOfDrLiz]

@hm21 Correction to my superseded review: the store workflows intentionally refuse to create Shorebird releases from a non-main branch, so TestFlight and Play internal validation are post-merge gates, not work you can complete on this PR branch.

Before this PR is marked ready, please:

1. Review the takeover commits pushed to this branch, including the Shorebird pin, iOS deployment-floor repair, and state-model compatibility tests.
2. Run the required Samsung Galaxy smoke test from this branch and document the device/build tested and results for:
   • launch and basic navigation
   • camera and microphone permissions
   • recording
   • upload
   • feed playback
   • app restart

Once that evidence is here, this review can be replaced with an approval. After merge—but before any public promotion—Liz will build the Shorebird-enabled artifacts from main and validate the exact TestFlight and Play internal builds on physical iPhone and Samsung devices. A failure at that gate means no promotion and a new fix PR/build.

[hm21]

@NotThatKindOfDrLiz Reviewed your takeover commits. The Shorebird pin is the important one — my commits moved Flutter to 3.47.2 and left Codemagic on 1.6.117, which would have broken the store build. Verified independently: revision 5ac7f9a9a5c4a5e66a958e608da0f73e34a3d6bb is tag v1.6.120, and 1.6.120 (28 Aug) is the release that added Flutter 3.47.2 / Dart 3.13.2 support. The version-aware iOS floor helper and the async-safety relock are right as well; that ratchet's own header documents that both tracked rules are type-resolving, so relocking after an SDK bump is required rather than optional.

Three follow-up commits pushed on top of yours:

• fix(state) — the handwritten models hand out a dart:collection UnmodifiableListView/SetView/MapView on every read, and those compare by identity. So state.editorsPicks == state.editorsPicks was false, and curationProvider.select((state) => state.editorsPicks) was told the picks changed on every unrelated change to that state, a loading flag included. Freezed's EqualUnmodifiable*View wrappers compare the wrapped source, which is what made a selector work; they are restored next to the state models. copyWith and props now read the raw field, which also stops a long-lived state accumulating one nested delegating view per copy.
• test(state) — four of the new contract tests built their fixtures from const collections. A const collection is already unmodifiable, so expect(state.editorsPicks.clear, throwsUnsupportedError) passed whether or not the getter wrapped anything, and the two const SeenVideosState values meant to prove "distinct instances compare deeply" were canonicalised into one object. Fixtures are mutable now, plus four tests covering the equality half of the contract.
• chore(baseline) — service size ceilings relocked after the rebase; every entry is below main's.

Heads up on two things: the PR was showing merge conflicts, so I rebased onto current main (one conflict, in the service god-file baseline) and force-pushed — your commit SHAs changed. And your cleanup commit also drops *.mocks.dart from the pre-push hook's changed-file scan, which is unrelated to removing Freezed; I left it in as an improvement and called it out in the description instead of burying it. The description now also tells everyone to re-run mise run setup_hooks, since installed hooks are generated copies and keep looking for *.freezed.dart.

Device gate: smoke-tested from this branch on a physical Samsung Galaxy S25 (SM-S942B, Android 16) — launch and basic navigation, camera and microphone permission flows, recording, upload, feed playback, and app restart all behave correctly. A screen recording follows in a separate comment.

I left your nostr_sdk reconnect test alone. Asserting exactly 4 and 8 created channels against a 50 ms wall-clock budget is in principle sensitive to a loaded runner, but the assertions are genuinely stronger than the old greaterThan(0) and no flake has been observed, so weakening them on speculation seemed like the worse change. Flag it if you would rather move it to fakeAsync.

Verification: flutter analyze lib test integration_test tools packages clean, repository-wide dart format reports no changes, changed-file pre-push suite 4991 passed / 4 skipped / 0 failed, and the async-safety, service god-file, skip, placeholder, ungrouped-test, layer-direction, l10n-delegate and unpinned-assertion ratchets all pass on the rebased tree. All GitHub checks are green on d1909e3.

flutter-upgrade.mp4