Re-ask this page's question against current knowledge; replace it in place.

AGENTDESK-P2(PR-K) / AGENTDESK-K(regenerate) — step 4 of the correction loop and the half that did not exist. Approving a Knowledge Document correction fixes every FUTURE answer, but a stored answer page keeps serving its bytes to every later fetcher forever (the GET lane has no staleness check, by design: a cached page must stay byte-stable for the agents citing it). So the customer's approved fix was invisible on exactly the URLs an agent had already found. This is the button that closes that.

OWNER-AUTHED and SYNCHRONOUS. get_user because this spends model tokens. Synchronous because it is one ask and the customer is watching the page they just fixed — the fast-path/slow-path split in the ask itself already bounds how long that takes, and a poll endpoint for a single ask would be machinery for its own sake.

NOT BILLED, NOT BUDGETED, STILL METERED — the orchestrator's direction, argued parameter by parameter in agent_desk/corrections.regenerate_answer_page. What lives HERE rather than there is the per-desk/day allowance: claimed BEFORE the ask (a check that runs after the spend is not a budget) and REFUNDED on every path that does not store a new answer, so a refusal never consumes quota.

429 when the day's allowance is spent, 403 when the dial is 0 (the button is switched off for this deployment), 409 when there is nothing to regenerate.