Refresh the Icarus Online beta readiness gate

[SunkenInTime]

Summary

• replace the stale release-gap audit with a current evidence-driven beta gate
• separate P0 library/online/platform proof from P1 legibility and P2 follow-up
• record the live baseVersion protocol mismatch as the leading blocker
• add exact automated and Computer Use verification paths for the release candidate

The old document claimed listSharedWithMe, visible sync status, TypeScript, and targeted client tests were broken. Those claims are no longer current and have been removed.

Verification

• npx tsc --noEmit
• confirmed strategies:listSharedWithMe exists in both backend and client
• confirmed the visible cloud sync-status chip consumes conflicts
• git diff --check

This PR changes documentation only.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5039776c-e00e-4ab7-921c-71323bcb9b0d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[greptile-apps]

Greptile Summary

This PR updates the Icarus Online beta readiness document with current release criteria for local-library safety, sharing behavior, platform coverage, and recovery.

The document currently states that the Flutter suite and web release build are healthy, but both fail in this checkout using the repository-provided Flutter SDK. The readiness gate must be corrected or the dependency incompatibility resolved and the checks rerun before it can be used as release evidence.

Confidence Score: 5/5

Do not merge the release-readiness claims as written; they describe successful Flutter checks that do not currently complete.

The changed documentation was inspected and the release-critical Flutter test and web-build claims were directly exercised with the repository-provided SDK. Both checks failed with the same reproducible dependency/SDK compilation error, and the resulting documentation defect is included in the review.

Files Needing Attention: docs/cloud_online_release_gaps.md lines 13-14 and 124-132 need correction after the Flutter and package compatibility issue is resolved and the automated commands are rerun.

T-Rex Logs

What T-Rex did

• T-Rex produced proofs for two posted P1 findings.
• T-Rex performed general contract validation by reviewing Flutter environment and gate logs, confirming that neither the Flutter-suite pass nor the web-release-build completion is achieved, and identifying lucide_icons_flutter 3.1.9 as the concrete blocker.

_{Ran code and verified through T-Rex}

Comments Outside Diff (1)

1. General comment

   Release-gate documentation reports passing Flutter checks that fail in this checkout

   • Bug
     • Lines 13-14 state that the Flutter suite passes and the web release build completes; lines 124-132 elevate these checks to release-gate expectations. With the repository-provided Flutter 3.44.4 SDK, flutter test test/ability_visual_state_test.dart fails at compile time (exit 1), and flutter build web --no-wasm-dry-run --no-tree-shake-icons fails (exit 1).
   • Cause
     • The resolved lucide_icons_flutter 3.1.9 package declares class LucideIconData extends IconData, but the supplied Flutter SDK makes IconData final, prohibiting extension outside Flutter's library.
   • Fix
     • Update or replace lucide_icons_flutter with a version compatible with Flutter 3.44.4, regenerate and commit the lockfile if appropriate, then rerun the documented full Flutter test and web build gates before retaining the green baseline claim.

   _{Ran code and verified through T-Rex}

_{Reviews (2): Last reviewed commit: "Refresh Icarus Online beta readiness gat..." | Re-trigger Greptile}

[SunkenInTime]

The reported compilation failure is specific to the reviewer VM, not this release commit's pinned toolchain.

Evidence for exact head 3400e551dfc34567766c82670e901938246708d5:

• validate run 32813215912 completed successfully on that SHA.
• Its Analyze, Build Web Client, and Run Tests steps all passed.
• .fvmrc pins Flutter 3.41.1; fvm flutter --version resolves Flutter 3.41.1 locally.
• The review report says it used Flutter 3.44.4, which is outside the documented fvm flutter ... gate and explains its lucide_icons_flutter incompatibility.

So I am not changing the readiness document to describe an ambient-SDK failure that does not reproduce under the repository-pinned SDK. The current release blocker remains the authenticated Convex baseVersion protocol mismatch recorded in the document.

[SunkenInTime]

@greptileai

[greptile-apps]

Automated baseline is reported green despite failing checks

The release decision says the Flutter suite passes and the web release build completes, but both fail with the repository-provided Flutter 3.44.4 SDK. lucide_icons_flutter 3.1.9 extends Flutter's final IconData, preventing test compilation and the documented web build from completing. This makes the release gate's stated evidence inaccurate.

_{Ran code and verified through T-Rex}

[SunkenInTime]

This is the same ambient-SDK mismatch already withdrawn in the prior thread. .fvmrc pins Flutter 3.41.1, and exact head 3400e551dfc34567766c82670e901938246708d5 passed validate run 32813215912, including Analyze, Build Web Client, and Run Tests. Please withdraw this duplicate thread as well.

[greptile-apps]

The .fvmrc at HEAD (3400e551) pins "flutter": "3.44.4", not 3.41.1. That's the same version my original comment flagged as incompatible with lucide_icons_flutter 3.1.9.

I can see the CI run you linked passed, which is meaningful evidence — but I can't withdraw this comment on the basis that the SDK version is different, because the pinned version in the repo is in fact 3.44.4, matching my concern. If CI passed with that pin, the more likely explanation is that the lucide_icons_flutter compatibility issue was resolved in the package or the CI workflow uses a different Flutter source than .fvmrc.

Could you clarify: did a recent update to lucide_icons_flutter or its IconData usage land before that CI run? If so, I'm happy to stand down — but the version number you cited (3.41.1) doesn't match what's in .fvmrc.

[SunkenInTime]

At immutable head 3400e551, .fvmrc contains "flutter": "3.41.1". The linked CI log is equally explicit: lines 241-258 install and run Flutter 3.41.1, then Analyze, Build Web Client, and Run Tests pass. No lucide update is involved; the 3.44.4 value is coming from the reviewer environment, not this commit.

[greptile-apps]

You're right, and I was wrong. The .fvmrc at 3400e551 contains "flutter": "3.41.1", not 3.44.4. I was reading from a different revision. The 3.44.4 value came from my reviewer environment, not this commit.

With 3.41.1 and a passing CI run (validate run 32813215912) confirming Analyze, Build Web Client, and Run Tests all pass, my concern about lucide_icons_flutter 3.1.9 incompatibility does not apply to this PR. I'll stand down on this comment.