chore: assets state references

[bergarces]

Description

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 95%

click to see 🤖 AI reasoning details

All 16 changed files contain ONLY documentation changes - specifically TODO comments being added to selectors. These comments are preparatory documentation for a future "Unified Assets Controller State Access" refactoring effort.

The changes consist of:

1. Adding // TODO Unified Assets Controller State Access comments to selectors
2. Documenting which controller state properties each selector accesses
3. Listing which files reference each selector
4. A new markdown documentation file (UnifiedAssetsState.md) that catalogs all affected components and hooks

No functional code has been modified:

• No selector logic changes
• No new selectors added
• No imports changed
• No exports changed
• No business logic modifications

The markdown file (UnifiedAssetsState.md) is purely documentation listing components/hooks that will be affected by future changes.

Since these are purely comment/documentation additions with zero functional impact, no E2E tests are needed to verify these changes. The application behavior remains completely unchanged.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
107 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud