Write Integration Tests for Admin Portal and Unit Assignment

The hierarchy tree view is likely a recursive or virtualized widget — ensure tests pump with realistic data (at least 20 nodes across 3 levels) to catch rendering edge cases. For the 'move node' test, capture the node's initial parent ID, perform the move, and assert the new parent ID in the state — don't rely solely on visual rendering. The role guard test is best implemented as a golden-path negative test: pump the screen, assert that it never reaches the admin content, and assert the no-access widget is visible. For scope propagation, you may need a fake/spy implementation of AccessScopeService that records calls and returns controlled values — avoid relying on timing or real async gaps.

Document the test data setup (what hierarchy structure and user assignments are pre-seeded) in a `setUp` block comment so future maintainers can reproduce failures without digging through state.

Combine widget tests (flutter_test + WidgetTester) for UI interaction coverage and integration tests (integration_test package) for end-to-end role guard and scope propagation flows. Mock Supabase at the repository layer for widget tests to keep them fast. For the role guard test, use a test helper that injects a non-admin auth token into the BLoC/Riverpod state before pumping the screen. Use `pumpAndSettle` after any tree mutation to allow animations to complete before asserting.

For the scope propagation test, listen to the AccessScopeService stream after the unit assignment and assert the new unit appears within 2 state emissions. Group tests by feature area (tree management, search, unit assignment, role guard, scope propagation) and run each group independently.