Archive sentry-improvements, sync specs

Sync Sentry error tracking requirement (5 scenarios) to main
infrastructure spec. Archive completed change.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

openspec/specs/infrastructure/spec.md

@@ -63,3 +63,26 @@ The infrastructure SHALL configure DNS and TLS for trails.cool and planner.trail
 #### Scenario: HTTPS access
 - **WHEN** a user navigates to https://trails.cool
 - **THEN** the connection is secured with a valid TLS certificate
+
+### Requirement: Sentry error tracking
+The system SHALL enrich Sentry events with user and session context, use route-aware tracing, and prevent source maps from being served to clients.
+
+#### Scenario: Journal error includes user context
+- **WHEN** an authenticated Journal user triggers an error
+- **THEN** the Sentry event SHALL include the user's ID and username
+
+#### Scenario: Journal error without user context
+- **WHEN** an unauthenticated visitor triggers an error
+- **THEN** the Sentry event SHALL have no user context (Sentry.setUser(null))
+
+#### Scenario: Planner error includes session ID
+- **WHEN** an error occurs during a Planner session
+- **THEN** the Sentry event SHALL include a `session_id` tag with the active session ID
+
+#### Scenario: Route-level performance traces
+- **WHEN** a user navigates between routes in either app
+- **THEN** Sentry SHALL create a transaction span named after the route pattern (e.g., `/routes/:id`)
+
+#### Scenario: Source maps not served to clients
+- **WHEN** a client requests a `.map` file from the production server
+- **THEN** the server SHALL return 404 (source maps are uploaded to Sentry during build, not shipped in the bundle)