Approve a proposed plan revision

A caller's replacement for the bar the agent proposed.

Whole or nothing, exactly like the envelope's own criterion: a partial edit would leave a bar the stopping rule reads as satisfiable and ends the run against, which is the failure decision 17 exists to prevent.

The machine-checked half of a plan (EDD section 6.1).

Every field here maps to a check on a real route. A field that does not belongs in the intent instead -- that split is what keeps "envelope" an enforceable word rather than a decorative one. Note there is no spend limit: owner-set limits are team- and project-scoped only (ENG-6083).

The recorded, rendered, never-checked half of a plan (EDD section 6.1).

estimated_cost_usd is server-derived at propose (ENG-6414) and shown beside the work so a user can tell a rounding error from a serious bill. Spend is bounded by team and project limits (ENG-6083), not this row.

Pricing inputs the server quotes from. Assumptions, not constraints.

The stored estimated_cost_usd is derived from these fields via quote_cost_usd. They are not hashed: they are inputs to a value that already is.