[shiny-code-app]

Why

The Supervisor steers each account to its reset with a check every 30 minutes. The exported burn is the higher of the last day's and last six hours' pace, so it kept reading 1.25%/h for two hours after an account stopped. That is right for the panel's "am I safe" warnings, and wrong for "what is the pace now".

What changed

• Each agent snapshot window gains recentBurn, a sibling of burn with the same shape: {unitsPerHour, observedDurationHours, sampleCount}, or null. It measures only the last two hours.
• burn is unchanged. Use next, warnings and the pace forecast still read it.
• Window length: 2 hours. At 5-minute readings, two hours gives about 24 intervals and close to 2 hours of observation. That clears the estimator's minimums (30 minutes of observation, two usable intervals) many times over. The same minimums apply, so it is null when the last two hours have too few readings, for example after the Mac slept. Like burn, it is never a whole-window average.
• It is the existing estimator with a shorter lookback (AccountBurnRateEstimator.observedBurnRates(..., recentOnly:)), not a new estimator. It is filled on both the local and the shared-presentation export paths. It uses the same last-day history the reader already loads.
• The two burn constructions now share one Burn(_:) initializer that drops unmeasured rates.
• Documented in the agent snapshot section of docs/provider-usage-access.md.

Verification

• swift build: clean.
• swift test --filter ContextPanelCoreTests: 1359 passed.
• New test, local and shared paths: a batch at 3 points an hour that stopped two hours ago exports burn 2/h (unchanged) and recentBurn 0/h over 2 hours with 25 samples. With no readings in the last two hours, burn stands and recentBurn is null. It fails if the recent pass uses the long lookback, if the shared path drops it, or if burn reads the recent rate (3 mutations, all caught).
• JetBrains inspection: UNKNOWN. This repository's worker is PyCharm and has no Swift or Markdown coverage.

Removed: the two inline Burn(unitsPerHour:...) constructions, now one initializer.
Net lines: Sources +29, Tests +39, docs +8.

Closes #1085

[shiny-code-app]

Ready for the merge train

Head: 303d887

[shiny-code-app]

Launchplane completed the merge-train step for this pull request.

• Repository: cbusillo/context-panel
• Base branch: main
• Pull request: Export the recent two-hour pace beside the conservative burn #1090
• Controller action: land_batch
• Controller record: merge-train-batch-landing-plan-20261108T230212Z-97c1ec7e93033560

Launchplane landed this pull request through protected batch PR #1091.

Launchplane manages this comment and will update it as the train moves.

[shiny-code-app]

Ready for the merge train

Head: 303d887