chore(release): 0.0.5

CHANGELOG.md

@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.0.5] - 2026-09-21
+
+### Changed
+
+- **Every sibling floor names this batch's release.** `magic` moves `^0.0.7` to `^0.0.15`, `fluttersdk_dusk` `^0.0.12` to `^0.0.15`, `fluttersdk_telescope` `^0.0.5` to `^0.0.6` and `fluttersdk_wind` `^1.5.0` to `^1.6.2`. The old ranges already admitted the new versions, so a fresh `pub get` resolves nothing differently; what changes is that the floors 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 in this package calls either, so no code here changes, but an app below magic 0.0.15 no longer resolves this release. (`pubspec.yaml`)
+
 ## [0.0.4] - 2026-08-25
 
 ### Added

README.md

@@ -42,9 +42,9 @@ Four import barrels:
 
 ```yaml
 dependencies:
-  magic_devtools: ^0.0.4
-  fluttersdk_dusk: ^0.0.13       # add if you use dusk
-  fluttersdk_telescope: ^0.0.5   # add if you use telescope
+  magic_devtools: ^0.0.5
+  fluttersdk_dusk: ^0.0.15       # add if you use dusk
+  fluttersdk_telescope: ^0.0.6   # add if you use telescope
 ```
 
 `magic_devtools` depends on `magic`, `fluttersdk_dusk`, and `fluttersdk_telescope` directly, so transitive resolution does not happen through `magic` itself.

pubspec.yaml

@@ -1,6 +1,6 @@
 name: magic_devtools
 description: "Magic adapters for the fluttersdk dev-tooling ecosystem: wires MagicDuskIntegration and MagicTelescopeIntegration into dusk and telescope."
-version: 0.0.4
+version: 0.0.5
 homepage: https://magic.fluttersdk.com
 repository: https://github.com/fluttersdk/magic_devtools
 issue_tracker: https://github.com/fluttersdk/magic_devtools/issues
@@ -12,10 +12,10 @@ environment:
 dependencies:
   flutter:
     sdk: flutter
-  magic: ^0.0.7
-  fluttersdk_dusk: ^0.0.12
-  fluttersdk_telescope: ^0.0.5
-  fluttersdk_wind: ^1.5.0
+  magic: ^0.0.15
+  fluttersdk_dusk: ^0.0.15
+  fluttersdk_telescope: ^0.0.6
+  fluttersdk_wind: ^1.6.2
 
 dev_dependencies:
   flutter_test:

test/dusk_integration_test.dart

@@ -595,9 +595,13 @@ void main() {
     });
 
     testWidgets('emits string-alias middleware names verbatim', (tester) async {
-      // String aliases pass through without Kernel resolution — they're
-      // surfaced as-is so the snapshot stays useful even when the alias
-      // isn't registered.
+      // A string alias is surfaced as the route declared it, not as the
+      // middleware the Kernel resolves it to: the alias is what an agent can
+      // grep the route table for. It has to be registered, because magic
+      // 0.0.14 refuses to build a router whose route names an unregistered
+      // alias, so an unregistered one can no longer reach a snapshot.
+      Kernel.register('guest', () => _NamedMiddleware('redirect-if-authed'));
+      addTearDown(Kernel.flush);
       MagicRoute.page('/', () => const SizedBox()).middleware(['guest']);
 
       await tester.pumpWidget(
@@ -607,7 +611,7 @@ void main() {
       final element = _findElement(tester, SizedBox);
 
       final emitted = magicMiddlewareEnricher(element, RefRegistry.instance);
-      expect(emitted, contains('guest'));
+      expect(emitted, 'magicMiddleware: guest');
     });
   });