chore: update Accounts CO

[gantunesr]

Description

Update Accounts CO

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MUL-1260

Manual testing steps

Not applicable

Screenshots/Recordings

Not applicable

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.

---

Note

Low Risk
Low risk because changes are limited to CODEOWNERS updates and import-path adjustments after reorganizing controller init modules, with no functional logic changes.

Overview
Updates .github/CODEOWNERS to assign the Accounts team ownership of additional Engine controller directories (e.g., multichain-account-service, snap-keyring, keyring-controller, storage-service) and expands multichain account path patterns.

Adjusts Engine.ts and related controller init tests to import snap-keyring, keyring-controller, and storage-service init modules from their new subdirectories.

^{Written by Cursor Bugbot for commit e3e1512. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[github-actions]

🔍 Smart E2E Test Selection

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

click to see 🤖 AI reasoning details

E2E Test Selection:
This PR is a pure file reorganization/refactoring with no functional code changes. The changes involve:

1. Engine.ts: Only import path updates - moving from flat controller files to subdirectory structure
2. keyring-controller-init.ts: Moved to keyring-controller/ subdirectory with updated relative imports
3. snap-keyring-builder-init.ts: Moved to snap-keyring/ subdirectory with updated relative imports
4. storage-service-init.ts: Moved to storage-service/ subdirectory with updated relative imports
5. Test files: Same reorganization with updated imports
6. CODEOWNERS: Added ownership entries for the new directories

No functional changes were made - no initialization order changes, no messenger configuration changes, no state schema changes, and no dependency changes. The controllers still work exactly the same way, just organized into subdirectories.

However, since these involve critical Phase 2 controllers (KeyringController is foundational for all account/transaction operations), I'm selecting SmokeAccounts as a minimal sanity check to verify the app still initializes correctly and basic account functionality works after the refactoring. This provides confidence that the import path changes don't break anything at runtime.

Performance Test Selection:
This PR contains only file reorganization and import path updates with no functional code changes. There are no changes to UI rendering, data loading, state management, or any code paths that could impact app performance. The controllers function identically, just from different file locations. No performance tests are needed.

View GitHub Actions results

[github-actions]

⚠️ E2E Fixture Validation — Structural changes detected

Category	Count
New keys	68
Missing keys	11
Type mismatches	0
Value mismatches	7 (informational)

The committed fixture schema is out of date. To update, comment:

@metamaskbot update-mobile-fixture

View full details | Download diff report

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud