Analyze Codebase

When to use

• At the start of a Playwright testing session (before ingest-spec or plan-tests)
• When running as part of run-testing-session pipeline (Stage 1)
• When project context is stale and needs refresh

Important: Always Prompt, Never Skip

When invoked as part of the run-testing-session orchestrator (Stage 0):

• If project-context.md does NOT exist: Show user "No global project context found. Run analyze-codebase? (required to proceed)" → User must choose Yes or the orchestrator cancels
• If project-context.md EXISTS: Show user these options:
  • A) Use existing context (skip analyze-codebase)
  • B) Re-run analyze-codebase (project has grown or changed)
  • C) Cancel session

This ensures the user always controls when the codebase analysis happens, especially important when the repository has grown and context needs refresh.