[krisnye]

@adobe/ecs 0.3.0, @adobe/ecs-persistence 0.1.1, @adobe/ecs-gpu 0.0.3

Syncs ecs/ from the ecs repository at 41399c5 (Adobe-Firefly/ecs#9).

Closes #242, closes #243, closes #244, closes #245, closes #246, closes #247, closes #248, closes #249. 0.3.0 because despawnWhere changes meaning (#244); persistence and gpu republish against it.

New API, for review:

// #243: a system orders itself against every other leaf of its composite that accesses a resource
readonly before?: readonly (System<unknown> | Resource.Key)[];
readonly after?:  readonly (System<unknown> | Resource.Key)[];

// #242: Finalizer.changes watches by trait, and every component with chosen resources
watch?: readonly (Essential | Resource.Key | OwnTrait)[]
      | { readonly components: true | readonly (Essential | OwnTrait)[]; readonly resources: readonly (Resource.Key | OwnTrait)[] };

// #249: a matched row's saved components are written onto the entity it matches
commands.spawnTables(tables, { resources?, existing?, update?: boolean })
spawn({ world, snapshot, match?, update?: boolean, entities? })   // @adobe/ecs-persistence

Behaviour:

• ecs: despawn only what existed before the sync point, or at the end of the run #244: despawnWhere despawns only what was alive before its sync point, as the commands issued before it leave it; what that sync point spawns lives. Chapter 06 shows one-frame events: the producer clears its last events and spawns this frame's, or an endFrame system runs after everything else.
• ecs compiler: an archetype declared below the system that names it fails with a bare ReferenceError #248: a system's commands may name an archetype declared below it; an import cycle names the system and the declaration.
• ecs: systems with disjoint archetype filters should not conflict on a shared component key #246: two systems don't conflict on a key both reach through their rows when one requires a component the other's not lists; the error says so where it would help.
• ecs: a system that writes a resource should not require ordering every reader by hand #243: a resource in before/after skips a leaf an explicit constraint already orders, and two systems naming one resource stay unordered, so two writers still conflict.
• ecs: an idle sync point (no command issued) should cost nothing #245: a sync point with nothing to apply is skipped, and tiers that run on the world's thread run as one pass through such sync points.
• ecs: allow Map and Set resources with a default, and symbol-keyed maps #247: a ReadonlyMap or ReadonlySet of what isn't data (a symbol, a key, a class) starts empty in each world; one given a default is told to leave it out.

Performance: eight chained systems, 100 runs per sample:

	Before	After
one tier	538 ns	538 ns
8 tiers, no commands	717 ns	636 ns
8 tiers, 7 idle sync points	859 ns	713 ns

A tier boundary costs 14 ns (26 before), an idle sync point 11 ns (20). A 3-pass comparison of every node benchmark: loop tick add remove −8.5%; read run +3.7% and loop tick add remove again +3.9%, after removing allocations from building a schedule; the rest within noise on 10–12 alternating reruns.

Checks: from a clean state, check:workspace, build, typecheck and every package's full suite pass locally, with a GPU and CI unset: ecs 1766, ecs-persistence 77, ecs-guide 131, ecs-gpu 38, ecs-todo-vanillajs 65, ecs-sample-browser 13, ecs-particles-webgpu 2, ecs-gpu-views 1, ecs-transfers-canvas 1; and every other package here.

The next pnpm run publish <otp> here publishes @adobe/ecs 0.3.0, @adobe/ecs-persistence 0.1.1 and @adobe/ecs-gpu 0.0.3.

🤖 Generated with Claude Code