1.13Step 7 — Write `docs/specs/product-under-test.md`

This file is the highest-level description of the system under test.

Required sections

Use this exact structure as a starting point (or update environments names if internally company calls them differently):

# Product Under Test

## Overview
Short description of the product.

## Environments
- local:
- qa:
- staging:
- production:

## User Roles
- guest
- authenticated user
- admin
- support
- other app-specific roles

## Feature Areas
- Authentication
- Search
- Catalog
- Checkout
- Account
- Reporting
- Admin
- app-specific modules

## Routing / URL Patterns
List important routes or patterns.

## Authentication Model
Describe login, session model, saved state strategy, and automation concerns.

## Major Risks for Automation
List risk areas that can cause flakiness or complexity.

## Notes
Anything else important for future agents.

Writing guidance

This file should be concise, but not vague.
Write for a future agent who lands in the repo with no chat history.