refactor(mute)!: use muted stream as source of truth instead of relationships model

[Taewa]

NOTE: NEXT_PUBLIC_DB_VERSION is required in deployment

• Removed the muted field from UserRelationshipsModel, its schema, and the NexusUserRelationship type
• Refactored LocalMuteService to use the muted user stream (UserStreamTypes.MUTED) as the single source of truth instead of storing mute state on the relationships model
• Bumped DB version from 2 to 3 (schema migration for removed column)
• Updated all tests across 13 files to reflect the new stream-based mute approach

#1382

[greptile-apps]

Greptile Summary

Refactored the muting system to use the muted user stream (UserStreamTypes.MUTED) as the single source of truth instead of storing mute state in the user_relationships table.

Key Changes:

• Removed muted field from UserRelationshipsModel, schema, and NexusUserRelationship type
• Simplified LocalMuteService logic - removed database transaction complexity and now directly checks/updates the muted stream
• Bumped DB version from 2 to 3 to trigger schema migration (database recreation handles column removal)
• Updated 13 test files to verify stream-based mute state instead of relationship model

Architecture Alignment:
This change aligns with the project's data patterns by using streams as the cache layer (per ADR-0003). The muted stream was already being maintained alongside the relationship field, creating redundancy. This refactor eliminates that duplication and simplifies the codebase.

Confidence Score: 5/5

• safe to merge - clean refactoring with comprehensive test coverage
• The refactoring is well-executed with proper test updates across all affected areas. DB version bump ensures safe migration via database recreation. The simplified logic removes transaction complexity while maintaining idempotency. The muted stream was already being used by the UI (useMutedUsers hook), so this change eliminates redundancy rather than introducing new behavior.
• No files require special attention

Important Files Changed

Filename	Overview
.env.example	bumped DB version from 2 to 3 for schema migration
src/libs/env/env.ts	updated default DB version from 2 to 3
src/core/models/user/relationships/userRelationships.schema.ts	removed muted field from schema and Dexie index definition
src/core/models/user/relationships/userRelationships.ts	removed muted property from model class
src/core/services/nexus/nexus.types.ts	removed muted field from NexusUserRelationship type
src/core/services/local/mute/mute.ts	refactored to use muted user stream as source of truth instead of relationships model; simplified logic removing transaction complexity

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Mute/Unmute Request] --> B{LocalMuteService}
    B --> C[Check Current Stream State]
    C --> D{Already in desired state?}
    D -->|Yes| E[Return Early - Idempotent]
    D -->|No| F[Update Muted User Stream]
    F --> G[UserStreamTypes.MUTED]
    G -->|Mute| H[prependToStream]
    G -->|Unmute| I[removeFromStream]
    H --> J[Clear Post Stream Queue]
    I --> J
    J --> K[Complete]
    
    style G fill:#e1f5ff
    style B fill:#fff4e6
    style D fill:#f0f0f0

Loading

_{Last reviewed commit: 5305396}

[github-actions]

🚀 Preview Deployment

URL: https://franky-preview-pr-1391-fzxmjul7ya-oa.a.run.app

franky-preview-pr-1391 • dbd956b

[tipogi]

nice, few comments

[aintnostressin]

Hi @Taewa , do you plan to remove dependency on nexus muted user stream ?
We got mute removal in nexus prepared.

[secondl1ght]

@Taewa it looks like this didn't get reviewed again after you added more commits/force pushed?