## MODIFIED Requirements

### Requirement: Selected legacy pages SHALL be integrated via wrapper-first strategy
The migration SHALL integrate `job-query`, `excel-query`, `query-tool`, and `tmtt-defect` through wrapper-based routing before full rewrites, and SHALL keep this mode temporary and explicitly tracked.

#### Scenario: Wrapper route availability for selected pages
- **WHEN** users navigate to each selected legacy page from the new shell
- **THEN** the route SHALL remain reachable and functionally usable through the wrapper layer

#### Scenario: Wrapper inventory is explicit
- **WHEN** migration status is reviewed for shell cutover readiness
- **THEN** the list of pages still in wrapper mode SHALL be explicitly recorded and versioned

### Requirement: Wrapper mode SHALL preserve legacy functional parity
Wrapper integration SHALL preserve current API interactions, core user workflows, and error handling semantics for wrapped pages until rewrite cutover.

#### Scenario: Legacy workflow parity under wrapper
- **WHEN** users execute core operations on a wrapped page (query/filter/export where applicable)
- **THEN** operation results SHALL remain behaviorally equivalent to pre-wrapper baseline

#### Scenario: Wrapper fallback preserves operability
- **WHEN** a native rewrite is temporarily disabled through rollback controls
- **THEN** the corresponding wrapper path SHALL restore usable behavior within the rollback target

### Requirement: Wrapper phase SHALL define rewrite exit criteria
Each wrapped page SHALL have explicit readiness criteria that gate transition from wrapper mode to full Vue module rewrite.

#### Scenario: Rewrite readiness decision
- **WHEN** a wrapped page reaches agreed quality and parity thresholds
- **THEN** the page SHALL be eligible for rewrite scheduling
- **THEN** wrapper decommission SHALL only occur after rewrite parity validation passes

#### Scenario: Exit criteria are enforced before decommission
- **WHEN** a rewrite candidate page has incomplete smoke or parity evidence
- **THEN** wrapper decommission for that page SHALL be blocked

## ADDED Requirements

### Requirement: Wrapper mode SHALL be fully decommissioned at migration completion
The shell migration SHALL reach an end state where selected legacy pages are served through native route-view modules and wrapper mode is removed from runtime navigation.

#### Scenario: Wrapper count reaches zero
- **WHEN** final migration gates are evaluated
- **THEN** `job-query`, `excel-query`, `query-tool`, and `tmtt-defect` SHALL all resolve through native route-view integration
- **THEN** wrapper-only runtime routes for these pages SHALL no longer be active navigation targets
