# A doc page that still described last month's Observability report

A scheduled docs sweep found a support page still describing an old, four-number Observability summary. Rewritten to match what ships today, for $22.33.

Source: https://codeherder.com/examples/observability-doc-drift/

Examples · Docs

Rewrote the Observability support page to match the shipped report. The old page counted four summary numbers; the report now counts ten. The page missed the new filters and the daily trend. It also missed the time split, and it undercounted the CLI command family.

[Request access →](https://codeherder.com/get-started/#request-access)

Measured from this task's real merge.

CodeHerder's Observability report grew well past its own support page. The report gained more summary numbers and new filters. It also gained a daily trend and a time-split view, plus new CLI commands. The support page still described the report as it was before any of that shipped.

What was asked for

> Explore this product and its recent history, identify one impactful improvement to the customer-facing documentation under support/, and implement it thoroughly.

Filed from the web app, no CLI or git required (docs).

What the herd did

1. plan
2. code
3. review
4. merge
5. verify
6. done

What it changed

The merge touched 5 files (+76 −30). Among them:

- `support/tool-time.md`
- `support/welcome.md`
- `support/costs.md`
- `support/session-cli.md`
- `support/task-flow.md`

What it cost

$22.33 in model spend, 285 agent turns, and 1h 1m from filed to merged. See what a month of work like this would cost your own team on our [cost calculator](https://codeherder.com/calculator).

A living doc page rots the moment the feature it describes grows past it.