docs(plans): record the reviewer-accepted step corrections

Hayley Swimelarrequested to merge
313/plan-amendments into main

Why

Step-MR reviewers asked for these plan corrections in-thread. Each was agreed in substance and declined in-MR, because step branches carry no plan-file edits (parallel plan edits conflict pairwise at merge), with the promise that the amendment lands through the plan's own MR. This MR is that promise:

  1. Step 34's Depends on gains Step 20 as a merge-order requirement, asked on chore(managementapi): apply maven bulk deletes ... (!1537 - merged) • Hayley Swimelar • 19.3.
  2. Step 33's upload-liveness inheritance sentence rewritten in condition-and-event form, with the reviewer's wording (same MR, round 4).
  3. Step 33's events wording states the applied-gated contract: acknowledged applied transitions emit after commit, none for skips, and an ambiguous acknowledgement can undercount (same MR, round 5).
  4. Step 16's Depends on records the OCI push-path race, its fail-closed closure, and the tracked two-writer residual, asked on feat(managementapi): serve the container image ... (!1541 - merged) • Hayley Swimelar • 19.3.
  5. Step 16's Files gains the persister and oci entries that closure names (same thread).

The Status table is untouched, its rows travel through their own follow-up MRs.

Related to #313 (closed)

Merge request reports