feat(website-builder): Content Entry input type

[SvenAlHamad]

Content Entry Input for the Website Builder

Adds a new Content Entry input type (createContentEntryInput) that lets a page editor either hand-pick CMS entries from an author-fixed model, or configure a dynamic query (sort / limit / search / pagination) against that model. The framework resolves the input into CMS entries server-side for SEO, and query mode adds cursor-based loadMore via a client hook.

Full design + as-built notes: plans/wb-content-entry-input.md.

What's in this PR

SDK primitive & resolver (website-builder-sdk)

• createContentEntryInput({ name, models, list, mode, query }) → { type: "contentEntry", renderer: "Webiny/ContentEntry", ... }.
• resolveContentEntryInput(input, value, loader) — resolves manual single/list references and query specs into entries; injectable ContentEntryLoader keeps it decoupled from @webiny/cms-sdk.
• Types: ContentEntryInput, ContentEntryReference, ContentEntryQueryConfig, ContentEntryQueryValue, ResolvedContentEntryQuery.

Server-side resolution & pagination (website-builder-react, -nextjs)

• resolveAutoLoad(document, manifests) — RSC pre-pass that resolves every contentEntry input against the CMS SDK; threaded through DocumentRenderer → context → LiveElementRenderer.onResolved. No useEffect for SSR data.
• useContentEntryList — client hook seeded from the server's first page; loadMore fetches subsequent cursor pages.
• Reactive editor-preview cache (contentEntryEditorCache) mirroring the CMS ref cache.

Editor renderer (app-website-builder)

• Webiny/ContentEntry sidebar renderer: manual mode (search-and-add autocomplete + reorderable rows, reusing the Headless CMS reference presenters via DI); query mode (sort field + segmented direction, limit with validation, search). One sort field → picker hidden, sorts by default.

Plumbing

• sdk-nextjs barrel exports the factory, resolveAutoLoad, useContentEntryList + types.
• cms-sdk: search param on listEntries.

Notes / decisions

• No autoLoad:false — the framework always resolves server-side; a component that wants to fetch for itself just uses plain inputs. (Flag was prototyped then removed.)
• Sort keys are read-API-verbatim — value fields as values_<fieldId>, meta fields bare (no values. dot-path magic). The read-API dot/underscore inconsistency is a known core item, parked.
• Known limitations: repeated-element resolution key collision; loadMore pages aren't in server HTML (not crawlable); a single declared sort field is mandatory to sort by default.

Testing

• resolveContentEntryInput unit-tested (15 cases: manual single/list, deleted-ref filtering, query params, values_ sort keys, default limit, single-field default sort, pagination embed). 145/145 website-builder-sdk tests pass.
• Preflight clean: adio ✅, lint ✅, generateTsConfigsInPackages (no changes), format ✅.
• Compile-verified against the next-theming-content-entry sample app; full live multi-mode smoke test still recommended.

🤖 Generated with Claude Code

[github-actions]

🚓 Slop Cop

⚠️ 4 thing(s) worth a look before merging.

Coherent, well-scoped PR implementing the Content Entry input feature as described; no integrity red flags found, only a couple of minor style nits.

📏 Code-style rule checks

🟡 Low — Multi-named import on one line

packages/app-website-builder/src/inputRenderers/ContentEntryInput.tsx imports { AutoComplete, Select, Input, SegmentedControl, Text } from "@webiny/admin-ui" and { ContentEntryInput, ContentEntryReference, ContentEntryQueryValue } from "@webiny/website-builder-sdk" on single lines, violating one-import-per-line.md.

🟡 Low — Multi-named import in resolveContentEntry.ts

packages/website-builder-sdk/src/contentEntry/resolveContentEntry.ts imports { ContentEntryInput, ContentEntryReference, ContentEntryQueryValue } from "~/types.js" on one line, violating one-import-per-line.md.

🟡 Low — Multi-named import in useContentEntryList re-export

packages/website-builder-react/src/contentEntry/useContentEntryList.ts re-exports { ResolvedContentEntryQuery, ContentEntryQuerySpec } on one line from "@webiny/website-builder-sdk", violating one-import-per-line.md.

🟡 Low — String concatenation-like conditional spread for query result

packages/website-builder-sdk/src/contentEntry/resolveContentEntry.ts uses an inline conditional spread ...(input.query?.pagination ? { query: listParams } : {}) when building the return object, which is flagged by no-inline-conditional-spreads.md.

_{Automated, non-blocking heads-up from an LLM. It can be wrong — use your judgment. Regenerates on every push.}