feat(data): Set/Map data model, type-driven conformance ordering, Services injection

[krisnye]

Description

Makes Set/Map first-class in the data model, pushes ordered-vs-unordered semantics into the type system, formalizes how services are injected into transitions, and names the two feature-authoring modes.

Data.stringify / Data.parse

A lower-level JSON serializer extended to round-trip Map and Set in both directions (plain JSON.stringify renders them as {}), surfaced on the Data namespace. The store's serialize/deserialize now route through it, so Set/Map values persist.

Set/Map as first-class Data

Data, IsData, DeepReadonly, and equals all handle ReadonlySet/ReadonlyMap. equals compares them order-independently (elements/values recurse). mutableClone already worked via structuredClone. Verified end-to-end that a stored typed-buffer column of Maps/Sets round-trips.

Type-driven conformance ordering

The comparator now derives ordering from the value's type — ReadonlyArray positional, ReadonlySet/ReadonlyMap order-independent — so the match.unordered option is removed. A numeric id is auto-ignored unless a case pins it, and Match.ref correspondence now holds across a Set boundary (backtracking pairing). Space-rock, hopper, and pixie model their unordered entity bags as ReadonlySet.

Formalized service injection

Each feature's services/ root exports one Services map; transitions inject with Pick<Services, ...> instead of ad-hoc inline types. Each service-database carries a compile-time drift-guard pinning db.services to Services. Migrated data-lit-todo and data-lit-space-rock-game.

Two feature modes: state-based vs. ECS-based

Names the two authoring modes, discriminated by the presence of data/state/. State-based (the mode for all new features): a Functional State Specification is the source of truth and the ECS is conformance-verified against it. ECS-based (legacy — features predating the state-based approach): the ECS is the source of truth, no data/state/, no conformance, so every transaction and action carries its own unit test. Documented in the data-ai rules (features/index.md plus gates in conformance.md / transactions.md / actions.md / data/state.md).

Docs

Updated @adobe/data README/AGENTS and the data-ai rules (data-modelling.md, data/state.md, data/index.md, services/index.md, conformance.md, service.md, features/index.md, transactions.md, actions.md).

Testing

• Full recursive lint and typecheck clean across all 18 packages
• @adobe/data 3011 tests, data-testing 12, data-lit-todo 102, data-lit-space-rock-game 135, data-gpu-hopper 90, data-react-pixie 42 — all passing (Node 24)

🤖 Generated with Claude Code

[krisnye]

This logic seems duplicated elsewhere. Let's leave it here and just reference it from the other rules instead of duplicating it.

[krisnye]

Done in 34ae293 — kept the ordering-by-type rule canonical here in data-modelling.md; data/state.md and conformance.md now reference it instead of restating it.