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

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

One client retrying a blip is invisible; twenty clients retrying a
sustained outage is a traffic weapon unless retries are spread out and
capped. Adds mountHerd (composing Task 1's tour driver and Task 2's
simulateHerd/renderRateStrip) as a stacked "Now 20 clients" section
below the existing single-client retry demo, with a mini-tour
spotlighting the measured peak-load gap: naive ~70x (unbounded, still
growing) vs httpware ~3x (capped by each client's own max_attempts,
never a shared budget).

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

CSS-driven conic countdown ring on the timeout and circuit-breaker pages'
fixed lane-B elements (elapsedB / brkB), showing the multi-second deadline
and reset-timeout waits. Retry and bulkhead get no ring per the fidelity
decision (backoff is sub-tick at this demo's time compression). All pages
gain a jagged clip-path failure dot so outcomes read without color.

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

Reuse renderRateStrip on the full-stack page: a small backend call-rate
strip below the lanes, revealed each tick with the single-client run,
labeled with the active incident phase. Gated by config.macroStrip so
every other lane page is unaffected. Finalizes the change summary with
the realized herd multipliers (naive ~70x vs httpware ~3x).

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

The design body still carried the pre-measurement ~10x/~1.2x placeholders and
a stale retry-ring mention. Align with the shipped model: httpware is bounded
near its max_attempts cap (~3x) at demo scale, naive ~70x; ring is CB+timeout.

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

The herd's sustained outage produced a smooth rising ramp for
independent, un-synchronized naive clients, not the spikes-with-gaps
the tour copy claims. Switch the model input to a flapping backend
(down/recover x3) so unbounded retries genuinely surge on each dip
and clear on recovery -- real spikes-with-gaps, faithfully sourced
from backend recovery rather than client synchronization. The
existing simulateHerd algorithm already produces this shape once the
fault flaps; this is a scenario + rendering + copy change.

Add computeOutageBands so the rate strip shades each dip separately,
leaving recovery gaps visibly unshaded between them (falls back to
the single outage window for callers that don't pass bands, so the
full-stack macro strip is unaffected). Re-measure the naive
multiplier against the flapping scenario (~18x, down from the
sustained model's ~70x since each dip is shorter) and reconcile
retry.md's copy and the change-file's motivation/design/payoff
language to match.

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

… intro

The only mountHerd caller now passes an explicit flapping-aware intro; the
shared default's "sustained" was dead but a latent trap for future callers.

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