Repository navigation
Move an Application between Projects by declaring it in the new one first #334
Description
Parent
What
Let an Application move between Projects with no pairing field (chapter 40): while two Projects declare one Id, the declaration outside the active Instance's namespace is the target and a Move is derived. The old Project removing it while the Move is open is E_MOVE_OPEN, and that Project is isolated with its source still rendered. A declaration left behind after retirement renders nothing, and the next fragment that still declares it is E_DUPLICATE_APPLICATION_ID. A negative fixture covers each order of publication.
Lands in TypeScript only, after emf/ is deleted (#347), with the rendered-tree and diagnostics oracles it affects, in one pull request. The intent, effective and dependencies goldens are dropped (#346), so it adds none.
Behaviour (draft ledger row)
An Application declared by two Projects composes once, as the target of a Move from the Project holding its active Instance, in every order the fragments arrive. The old Project cannot drop it before the Move retires, and cannot keep it after.
Blocked by
#341, the map whose rewrite plan replaces the closed placement ticket #328 (see #350).
Activity
ExtraToast commentedon Oct 27, 2026
Resume here (updated 2026-10-27)
State: merged as
30bc5414(PR #650).Next step: none here. 1.0.0 now waits on #665 and the maintainer (#379).
Blocked by: nothing.
Decisions:
src/check/departures.ts).departing: true, with no routes, Client, alerts, dashboards, migration or Move, and its workloads created once.E_MOVE_OPENfires when the old Project stops declaring the Application before the source retires.Open, written in the PR for the maintainer:
targetandflippedAton its record after retirement (delivery repo);