`MAZENG-FT-28` · Apply an explicitly reviewed change

Feature intent

Authorized users need to apply exactly the infrastructure plan they reviewed, with explicit confirmation and an authoritative execution result.

Why it matters

Authorized users need to apply exactly the infrastructure plan they reviewed, with explicit confirmation and an authoritative execution result.

Users can carry out an approved change without plan substitution, duplicate execution, or ambiguity about the real Terraform process outcome.

Require explicit user confirmation and server-side project authorization before apply.
Bind execution to the exact reviewed plan, design revision, and variable revision; invalidate confirmation after any change.
Reject or correlate duplicate submissions to one execution.
Report completion from the actual Terraform process result without automatic approval shortcuts.

Acceptance

01
Apply requires explicit confirmation and server-side authorization for the project.
02
Execution is bound to the exact accepted plan/design/variable versions; any change invalidates confirmation.
03
Duplicate submissions are rejected or correlated to one execution, and completion reflects the actual Terraform process result.

None recorded.

Automatic approval or missing project-role authorization can mutate infrastructure without a valid reviewed decision.
Asynchronous early returns and duplicate submissions can misreport completion or start multiple applies.

No authoritative Architecture tasks are linked.