chore(deps): track the published sibling versions

[anilcancakir]

Advances every sibling caret to what is now on pub.dev.

Required rather than cosmetic: under 0.0.z caret semantics ^0.0.5 means >=0.0.5 <0.0.6, so the previous constraints EXCLUDED the versions just released. A fork resolving from pub.dev would have pulled framework versions that predate MagicStarter.bootstrap() and SessionScopeSync, which this app calls in its service provider.

Verified in two directions. In-workspace with the local path overrides: analyze clean, 7 tests. And against pub.dev directly, via a scratch package depending only on hosted magic ^0.0.6 and magic_starter ^0.0.1-alpha.17, which resolves both from hosted and analyzes clean while touching bootstrap(), SessionScopeSync.attach/detach, PlanUpgradeRequirement, UpgradePrompt, MSUpgradeNudge and both middlewares. So the published packages genuinely carry the release-train work.

magic_devtools: ^0.0.2 points at a version that is tagged and merged but NOT yet on pub.dev: its publish fails with "publishing from github is not enabled", a one-time pub.dev admin setting on that package. Until that is enabled a fork cannot resolve, which the fork probe in this PR's discussion isolates precisely.

[anilcancakir]

Fork verified against pub.dev, and it isolates the one remaining blocker exactly.

Built a fresh clone from tracked files only, with no pubspec_overrides.yaml, so
every dependency had to come from pub.dev. Two runs:

With the constraints in this PR, resolution fails on exactly one package, and
pub names it itself:

Consider downgrading your constraint on magic_devtools: flutter pub add magic_devtools:^0.0.1

Nothing else is contested.

With magic_devtools temporarily downgraded to ^0.0.1 (probe only, not
committed), everything resolves from hosted:

magic                0.0.6            (hosted)
magic_starter        0.0.1-alpha.17   (hosted)
fluttersdk_dusk      0.0.9            (hosted)
fluttersdk_artisan   0.0.9            (hosted)

and the build's remaining errors all trace to a single cause, the published 0.0.1
missing its barrels:

Error reading '.../magic_devtools-0.0.1/lib/magic_devtools.dart' (No such file or directory)
Error reading '.../magic_devtools-0.0.1/lib/preview.dart'        (No such file or directory)
Error: 'PreviewEntry' isn't a type.
Error: The getter 'MagicPreview' isn't defined ...

Not one error mentions MagicStarter.bootstrap, SessionScopeSync, or
MSUpgradeNudge. Those resolved cleanly from the published packages, which is the
thing worth proving: the release train works from pub.dev, not just from local
paths.

Independently confirmed with a scratch package depending only on hosted
magic ^0.0.6 and magic_starter ^0.0.1-alpha.17: resolves both from hosted and
analyzes clean while touching bootstrap(), SessionScopeSync.attach/detach,
PlanUpgradeRequirement, UpgradePrompt.startUpgrade, MSUpgradeNudge,
EnsureAuthenticated and RedirectIfAuthenticated.

So the fork is one publish away. magic_devtools 0.0.2 is merged and tagged, and
its workflow validates the package with 0 warnings, but pub.dev rejects it with
"publishing from github is not enabled": a one-time Automated-publishing setting on
that package (repository fluttersdk/magic_devtools, tag pattern {{version}},
matching the plain tags the sibling packages already use). Re-running the workflow
cannot fix it.

Also confirms the .env fix from #2: the tracked file is present in the clone and
no missing-asset error appears anywhere.

[Copilot]

Pull request overview

Updates this app’s hosted (pub.dev) dependency constraints to track newly released sibling package versions, ensuring external forks resolve to versions that include APIs the app now uses.

Changes:

• Bumped magic and magic_starter to newer published release-train versions.
• Bumped dev tooling dependencies (magic_devtools, fluttersdk_dusk, fluttersdk_artisan) to newer versions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.