[cmdr-chara]

Fix failed v0.9.6 publication validation

The manually dispatched release run #38966191713 passed exact-main-SHA checks, then failed during Validate, package, and prepare release evidence because four dated ecosystem documents had overdue Next review deadlines. The publish job was correctly skipped.

Changes

• Recheck and refresh Next.js October 14 critical/high security fixes, newer active 16.4 baseline, and the relevant September 30 release history.
• Recheck Expo SDK 58, newer React Native compatibility, and resolved SDK 57 Hermes memory/development startup regressions.
• Update the mobile platform matrix for Flutter 3.47, Expo SDK 58, and the August React Native 0.87 changes.
• Recheck selected Flutter package versions and migration warnings using pub.dev.
• Preserve historical Information checked dates while adding explicit 2026-10-16 source-check notes and finite next-review deadlines.
• Fix CI/release drift: .github/workflows/ci.yml now runs both validation and smoke checks with the current UTC date instead of hard-coded 2026-09-25.
• Note the evidence refresh in the existing 0.9.6 changelog and research ledger.

Evidence and verification

• Primary sources include Next.js advisories, Expo SDK 58, Flutter 3.47, and official pub.dev version pages. Individual evidence links are in the changed reference docs.
• Verified final Git tree contains only seven intended changed files, zero removed.
• Read back all four staged references and verified their next-review dates are strictly later than October 16 and their evidence/source sections are present.
• GitHub CI and CodeQL on the candidate are pending. The complete, real-date repository validation must pass before merging.

Release handoff

After this PR passes, merge into main, wait for all required GitHub Actions checks on the new exact main SHA, and manually dispatch Release (approved) using that SHA. Do not rerun the old SHA, since the workflow deliberately refuses a stale candidate. Human release-approval environment protections remain unchanged.

No automatic release, merge, or weakening of freshness validation is included.

Summary by CodeRabbit

• Documentation

  • Updated web, mobile, and Flutter ecosystem guidance with recent framework releases, compatibility details, security advisories, and review dates.
  • Clarified Expo SDK compatibility and documented resolved startup and memory regressions, along with migration considerations for selected Flutter packages.

• Bug Fixes

  • CI freshness checks now use the current UTC date, aligning them with release verification.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: d3dda17f-69d2-4b9b-a907-f760645344b1

📥 Commits

Reviewing files that changed from the base of the PR and between a064aa9 and 74a9e0a.

📒 Files selected for processing: 7

• .github/workflows/ci.yml
• CHANGELOG.md
• docs/research-ledger.md
• skills/expo-react-native-builder/references/expo-react-native-ecosystem-2026-07-17.md
• skills/flutter-production-builder/references/flutter-ecosystem-2026-07-17.md
• skills/mobile-architecture-director/references/platform-decision-matrix-2026-07-17.md
• skills/production-web-builder/references/web-ecosystem-2026-09-24.md

+----------------------------+
| Bunny-grade bug detection. |
+----------------------------+
  \
   \     /)/)
        ( '')
        /  |
      o(___)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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