fix: land the deferred @Joined resolution in main (01B)

[MrSociety404]

Consolidates tmp/fixes-batch into main: the @Joined regression fix from #21 (merged 2026-07-28) — Query.List now resolves its own deferred joined fields, so consumers (the cms members list among them) get populated results again without any change on their side.

The branch was never consolidated, so main (and the v0.1.7 release currently on npm) still ships the regression. This must land before the npm publish: publishing from today's main would ship without the fix. Publish plan after merge: release @antelopejs/interface-data-api. (Republish the shell @antelopejs/data-api — stale instruction: nothing consumes the shell module anymore, every consumer imports interface-data-api directly with a range that picks the new version up on install.)

Greptile Summary

The PR makes Query.List return a self-resolving stream for deferred @Joined fields while preserving page-scoped lookups and count efficiency.

• Adds operation-aware deferred join materialization for stream consumers.
• Keeps the default list route in explicit deferred-field mode so joins occur after pagination and respect plucking.
• Documents the deferred-resolution behavior and adds coverage for paging, filtering, sorting, aggregation, embedding, casting, and iteration.

Confidence Score: 5/5

The PR appears safe to merge with no concrete blocking or independently actionable non-blocking issue identified.

The deferred join wrapper preserves joined-field visibility across the tested stream operations while keeping lookups out of count pipelines and after page boundaries where intended.

Important Files Changed

Filename	Overview
src/components.ts	Introduces the self-resolving deferred-join stream, operation forwarding, and the Query.List option for exposing unresolved joined fields.
src/index.ts	Updates the default list route to retain explicit deferred resolution after pagination and field selection.
src/tests/components/deferred_joined.test.ts	Adds broad integration coverage for deferred joined fields across stream execution and transformation paths.
docs/10.joined.md	Documents when deferred joins materialize and how callers can explicitly manage them.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Query.List] --> B{Joined field needed by filter or sort?}
  B -->|Yes| C[Materialize before count or sort]
  B -->|No| D{Expose deferred fields?}
  D -->|Yes| E[Return raw stream and deferred field set]
  D -->|No| F[Return DeferredJoinedStream]
  F --> G{First operation}
  G -->|slice or nth| H[Page first, then resolve joins]
  G -->|count or eligible aggregate| I[Use raw pipeline]
  G -->|other row-observing operation| J[Resolve joins before operation]

Loading

_{Reviews (1): Last reviewed commit: "fix: resolve deferred joined fields from..." | Re-trigger Greptile}