---
description: Compare legacy Angular and React implementation parity
argument-hint: "<feature>"
---

Use pi-crew with the `flights-web` team and the `angular-react-parity` workflow for this feature:

$@

Execution safety:

- Call the Pi Crew `team` tool for this workflow; do not implement the task directly in the parent Pi session.
- Do not call unavailable abstract tools such as `glob`; use `rg --files`, `rg -n`, `find`, `sed`, `nl`, and `git grep`.
- Never repeat the same failed tool call or shell command more than once.
- If a command exits non-zero with no useful output, do not retry it unchanged; inspect source/tests or change the hypothesis first.
- If a focused test fails, use the failure location to inspect and fix code/tests; do not repeatedly grep test output for unrelated terms.
- After two failed verification attempts without new evidence, stop and report the blocker, current hypothesis, and next concrete fix.
- If five consecutive tool calls add no new information, stop and summarize what is known.

Treat `ClientApp/` as the Angular reference and `src/` as the React implementation. Produce or update the business-logic spec, parity matrix, and verification report under `docs/parity/`. Use existing compare scripts and Playwright MCP where useful. Do not edit production code unless I explicitly ask for an implementation follow-up.
