The distinction that was checked and ruled out: why these endpoints are the same API surface rather than separate workflows, states, projections, or actor-specific operations.
Existing endpoints absorbed into the survivor. Descendants under these path prefixes are moved to the survivor prefix when possible.
Why the survivor endpoint already represents the same user workflow, resource, actor scope, database mapping, and lifecycle as every absorbed endpoint. Decided first; the action type and target endpoints are its conclusion, never a backfilled justification.
Existing endpoint kept as the canonical survivor.
Action discriminator, chosen after the reason proves absorption is safe.
Finalize-stage absorption of duplicate endpoint surfaces into one survivor.
The survivor endpoint remains. Exact absorbed endpoints are removed, and descendant endpoints under an absorbed path prefix are rewritten under the survivor path prefix so nested API surfaces are preserved rather than cascade-deleted.
Author
Samchon