Tags are not reactive, anywhere side from Inspector

[jamiepine]

Check for other issues

• I've checked for other issues, and none exist.

Issue description

When I add a new tag, I have to refresh the app in order for that tag to show up in the sidebar.

Steps to reproduce

1. Create a new tag (either in the Inspector or sidebar)
2. Observe nothing happens
3. Refresh the app, the tag will be there

Platform and versions

• OS: macOS (also on Linux and Windows)
• Spacedrive: v2.0.0-alpha.1

Stack trace

Additional context

No response

Code of Conduct

• I agree to follow the Code of Conduct.

[tembo]

Issue Validation

This is a valid bug. The tag creation action in the backend does not emit a ResourceChanged event for the newly created tag, so the frontend's normalized cache (which subscribes to resourceType: 'tag' events) never gets notified. The sidebar and TagSelector both use useNormalizedQuery to fetch tags and rely on WebSocket events for real-time updates.

Relevant Code

Frontend (subscriptions):

• packages/interface/src/components/SpacesSidebar/TagsGroup.tsx:101-105 - Uses useNormalizedQuery with resourceType: 'tag'
• packages/interface/src/components/Tags/TagSelector.tsx:39-43 - Same pattern for Inspector

Backend (the bug):

• core/src/ops/tags/create/action.rs - The CreateTagAction::execute method
• Line 74-76: Calls sync_model(&tag_entity, ChangeType::Insert) for cross-device sync
• Line 198: Only emits emit_resource_events("file", ...) for affected files when apply_to is provided
• Missing: No call to emit_resource_events("tag", vec![tag_entity.uuid]) for the tag itself

For comparison (correct pattern):

• core/src/ops/spaces/create/action.rs:87 - emit_resource_events("space", vec![result.uuid])
• core/src/ops/spaces/add_group/action.rs:90 - emit_resource_events("space_group", vec![result.uuid])

What's Happening

1. User creates a tag via sidebar or Inspector
2. Backend creates the tag in the database and syncs it for cross-device sync
3. Backend returns the created tag in the response
4. Bug: Backend does NOT emit a ResourceChanged event for the new tag
5. Frontend's useNormalizedQuery subscription for resourceType: 'tag' receives nothing
6. The TanStack Query cache is never updated with the new tag
7. User must refresh to trigger a fresh query

The Tag resource is correctly registered (core/src/domain/tag.rs:528) and implements Identifiable, so the infrastructure is in place. It's just the action that's missing the event emission.

Potential Approaches

1. Add emit_resource_events in CreateTagAction - After sync_model, add:

   let resource_manager = crate::domain::ResourceManager::new(
       Arc::new(library.db().conn().clone()),
       _context.events.clone(),
   );
   resource_manager
       .emit_resource_events("tag", vec![tag_entity.uuid])
       .await
       .map_err(|e| ActionError::Internal(format!("Failed to emit resource events: {}", e)))?;

   This matches the pattern used in spaces/create/action.rs.

2. Also update tags.apply action - core/src/ops/tags/apply/action.rs might need the same treatment if tags can be created inline during apply (though from the code it looks like it only applies existing tags, so this may not be needed).

3. Consider update/delete actions - If there are tag update or delete actions, they should also emit events. A quick grep shows only create, apply, and search are registered as tag operations.

Investigation Notes

• The frontend subscription setup is correct. Looking at useNormalizedQuery.ts:162-164, there's a skip condition for file resources without pathScope, but tags don't have this restriction.
• The sync_model call handles cross-device sync (HLC-based CRDT sync), which is separate from the WebSocket event system for frontend reactivity.
• This bug affects all places that create tags: both the sidebar "New Tag" button and the Inspector's TagSelector "Create tag" option.
• No recent commits touching this area that could have caused a regression - this appears to be a missing implementation from when the normalized cache system was built.