Repair triage artifact scope and evidence contracts
This commit is contained in:
@@ -284,6 +284,12 @@ type FirstSignalLoadState = 'idle' | 'loading' | 'streaming' | 'error' | 'done';
|
||||
| `--motion-easing-decelerate` | cubic-bezier(0, 0, 0.2, 1) | Entries |
|
||||
| `--motion-easing-accelerate` | cubic-bezier(0.4, 0, 1, 1) | Exits |
|
||||
|
||||
### 8.4 Browser TTFS Emission
|
||||
|
||||
- Web TTFS surfaces emit via the shared frontend `TelemetryClient`; they do not post directly to a page-local TTFS endpoint.
|
||||
- This keeps browser-side TTFS aligned with global sampling, queue persistence, and offline/no-ingest behavior.
|
||||
- When no telemetry ingest endpoint is configured in a local or scratch setup, TTFS emission must fail closed as a no-op and must never block the user flow or surface runtime errors.
|
||||
|
||||
## 9) Failure Signatures
|
||||
|
||||
Failure signatures enable predictive "last known outcome" by pattern-matching historical failures.
|
||||
|
||||
Reference in New Issue
Block a user