Built-In AI availability() Cold-Start Reproducer
Fires Wave 1 immediately on page load (t = 0ms) and Wave 2 after 4000ms. On unpatched Chrome 154 cold start, Wave 1 hangs in ManifestBrokerState::init_callbacks_ while Wave 2 resolves immediately.
Running cold-start probe...t = 0.0s
Wave 1 — Immediate on Load (t = 0ms)
0 / 0 settled| API | Status | Result | Latency |
|---|---|---|---|
| Summarizer.availability() | WAITING | — | — |
| LanguageModel.availability() | WAITING | — | — |
| Writer.availability() | WAITING | — | — |
| Rewriter.availability() | WAITING | — | — |
| Proofreader.availability() | WAITING | — | — |
| LanguageDetector.availability() [control] | WAITING | — | — |
| Translator.availability() [control] | WAITING | — | — |
Wave 2 — Delayed Call (t = +4000ms)
Scheduled in 4.0s| API | Status | Result | Latency |
|---|---|---|---|
| Summarizer.availability() | WAITING | — | — |
| LanguageModel.availability() | WAITING | — | — |
| Writer.availability() | WAITING | — | — |
| Rewriter.availability() | WAITING | — | — |
| Proofreader.availability() | WAITING | — | — |
| LanguageDetector.availability() [control] | WAITING | — | — |
| Translator.availability() [control] | WAITING | — | — |