chore(release): 0.0.5

[anilcancakir]

Wave three of an eight-package batch: dusk 0.0.15 and magic 0.0.15 are published, and this re-pins against them.

What ships

Floors only, no code in lib/ moves.

Dependency	From	To
magic	^0.0.7	^0.0.15
fluttersdk_dusk	^0.0.12	^0.0.15
fluttersdk_telescope	^0.0.5	^0.0.6
fluttersdk_wind	^1.5.0	^1.6.2

One test was red against magic 0.0.14 and later, unnoticed because master has not run CI since 3 September. "emits string-alias middleware names verbatim" routed through an unregistered 'guest' alias, and magic 0.0.14 refuses to build a router whose route names one (Bad state: Unresolvable route middleware on 1 route). The test's premise, an unregistered alias reaching a snapshot, can no longer happen, so the alias is registered now (and flushed after), and the assertion is exact: magicMiddleware: guest, which proves the enricher reports the alias rather than the middleware it resolves to. Test-only; the enricher is unchanged.

Stamps: pubspec.yaml and the README.md install snippet. magic:install --with-devtools in magic 0.0.15 already writes magic_devtools: ^0.0.5, so this is the release that request resolves to.

The old ranges already admitted the new versions, so a fresh pub get resolves nothing differently; the floors now name the releases this package is verified against. magic 0.0.15 is breaking in its database layer (a migration may no longer manage its own transaction, and DB.transaction refuses a callback that closes the transaction itself). Nothing here calls either, so an app below magic 0.0.15 no longer resolves this release but nothing in its behaviour changes.

Gates

Run locally against magic 0.0.15 (published since): flutter analyze --no-fatal-infos no issues, dart format --set-exit-if-changed . 0 changed, flutter test 110 passed.

After this merges

git tag 0.0.5 && git push origin 0.0.5, no v prefix.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!