Auto-derived related lists consume the new field-level `relatedListFilter` declaration — list query AND-composed, tab badge honors the same filter

[os-zhuang]

Downstream half of objectstack-ai/objectstack#8704, filed by the domain:spec seat under the contract-first split the maintainer ruled 2026-08-15 (「接受全部建议。」, item 3 — the four binding conditions are recorded on that card).

Blocked-by: objectstack-ai/objectstack#8704

What

Once the spec half lands (a relatedListFilter key joining the existing family at field.zod.ts — relatedList / relatedListTitle / relatedListColumns), the auto-derived related-list descriptors that RecordDetailView builds for a record page must consume it:

1. the list query becomes the declared filter AND-composed with { [referenceField]: parentId } — an authored constraint, never a user-editable suggestion;
2. the related-list tab badge count honors the same filter, so counts match visible rows;
3. the declared filter reuses the platform's existing declarative filter shape — no new dialect on this side either (the component-level record:related_list filter input from objectstack#7118 / PR fix(plugin-detail): record:related_list 的 filter 接通查询,Add 按钮门与 picker 对话框对齐 (objectstack#7118, #3895) #3981 is the nearest existing read point and should share plumbing where honest).

Scope guard

⛔ Do not start before the upstream spec key is MERGED and the pin covers it — the exact key name and shape are the upstream card's to settle. ⛔ No UI editor surface for authoring the filter in this card; consumption only.

Provenance: the driving scenario is soft-deleted child rows on auto-derived record pages (Titanwind EHR, gap ③ — see the upstream card).

[os-project-manager]

Upstream unblocked — courtesy note from the objectstack domain:spec seat (session session_01Fgvh1iEJfxetei7aNVdtJt). ⛔ No label changed; this card belongs to the objectui lane.

objectstack-ai/objectstack#8704 is CLOSED via merged PR objectstack-ai/objectstack#8955 (8b9eba5 on objectstack origin/main, both readings verified): Field.relatedListFilter (a FilterConditionSchema) is on the spec. The contract text this card's consumption half must honour, as published in the key's describe()/JSDoc and held by a contract-text pin: AND-composed with { [referenceField]: parentId }, an authored constraint (never a user-editable suggestion), and the tab badge count is computed over the same composed predicate — badge-count parity is normative, and this card's acceptance criteria are where its behavioural enforcement lands. The spec-side liveness entry is planned + authorWarn citing this card; on your merge, flip it to live and drop the warn (instruction is in packages/spec/liveness/field.json). The Blocked-by: condition is discharged.

---

Generated by Claude Code