Description

This PR removes four unused header components from app/component-library/components-temp/: HeaderCollapsible, HeaderCollapsibleStandard, HeaderCollapsibleSubpage, and HeaderStackedSubpage.

Reason for change: These components are not used anywhere in the app. Removing them reduces maintenance surface and dead code.

What changed:

1. Deleted component directories (21 files total)

   • HeaderCollapsible/ – component, types, useHeaderCollapsible hook, test, stories, index
   • HeaderCollapsibleStandard/ – component, types, test, stories, index (wrapped HeaderCollapsible with TitleStandard)
   • HeaderCollapsibleSubpage/ – component, types, test, stories, index (wrapped HeaderCollapsible with TitleSubpage)
   • HeaderStackedSubpage/ – component, types, test, stories, index (standalone stacked subpage header)

2. Storybook

   • Removed the four story require() entries from .storybook/storybook.requires.js for the removed components.

No app code imported these components; removal is self-contained to components-temp and Storybook registration.

Changelog

This PR is not end-user-facing; it removes unused internal header components.

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/DSYS-495

Manual testing steps

Feature: Removed unused header components

  Scenario: Lint and type check pass
    Given the branch is checked out
    When the author runs yarn lint and yarn lint:tsc
    Then both complete without errors

  Scenario: No references to removed components
    Given the codebase is searched for HeaderCollapsible, HeaderCollapsibleStandard, HeaderCollapsibleSubpage, HeaderStackedSubpage
    Then no imports or usages remain (only this PR description)

Screenshots/Recordings

Before

N/A – code removal; components were unused.

After

N/A – same app behavior; removed components were not referenced.

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.