# S01: Browser Agent Site Audit — UAT

**Milestone:** M018
**Written:** 2026-04-03T19:50:18.908Z

## UAT: S01 — Browser Agent Site Audit

### Preconditions
- Chrysopedia site running at http://ub01:8096
- Files exist: `SITE-AUDIT-REPORT.md`, `AUDIT-FINDINGS.md`, `S01-RESEARCH.md`

### Test Cases

**TC-1: Site Audit Report completeness**
1. Open `.gsd/milestones/M018/slices/S01/SITE-AUDIT-REPORT.md`
2. Verify it contains all 9 required H2 sections: Executive Summary, Route Map, Component Inventory, API Surface Map, Data Model, CSS Architecture, Infrastructure Stack, Phase 2 Integration Recommendations, Appendix
3. Verify report is ≥300 lines (actual: 467)
4. Verify no placeholder text ("TBD", "TODO", "coming soon")
Expected: All sections present, substantive, no placeholders

**TC-2: Route Map accuracy**
1. In Route Map section, count documented routes
2. For each route listed, navigate to `http://ub01:8096{path}` in browser
3. Confirm the route renders and the component name matches
Expected: All 12 routes documented, all render successfully

**TC-3: API Surface Map accuracy**
1. In API Surface Map section, pick 5 endpoints across different domains (public, browse, admin)
2. Run `curl -s http://ub01:8096{endpoint}` for each
3. Compare response shape to what the report documents
Expected: Status codes and response keys match report documentation

**TC-4: Discrepancy documentation**
1. Open AUDIT-FINDINGS.md, locate "Discrepancies" or equivalent section
2. Verify at least 5 discrepancies are documented with specific details
3. Cross-check that SITE-AUDIT-REPORT.md reflects the corrected information (not the stale research)
Expected: 7 discrepancies documented; report uses live-verified data

**TC-5: Phase 2 Integration Recommendations**
1. In SITE-AUDIT-REPORT.md, find Phase 2 Integration Recommendations section
2. Verify it documents at least 5 risks with mitigations
3. Verify cross-references to existing DECISIONS.md entries
Expected: 8 risks with mitigations, references to D-numbered decisions

**TC-6: CSS Architecture documentation**
1. Find CSS Architecture section in report
2. Verify it documents custom property count, breakpoints, and naming conventions
3. Verify it notes the 77 custom properties and dark-theme-only approach
Expected: CSS architecture substantively documented with specific numbers

### Edge Cases

**EC-1: Report handles missing/auth-gated endpoints gracefully**
1. Check that admin endpoints which returned 422 or required auth are noted as such
2. Verify the report doesn't claim endpoints work when they returned errors
Expected: Auth/error status clearly noted per endpoint
