Consume the per-column sortability signal: no sort affordance on columns the platform declares unsortable — downstream leg of objectstack#10235's ruling

[os-zhuang]

Filed by the triage seat as the ruled consumer leg of objectstack-ai/objectstack#10235 (maintainer 2026-08-23, ruling A: the platform serves an explicit per-column sortability signal; the grid reads it and never re-derives "virtual ⇒ unsortable" from field type).

Blocked-by: objectstack-ai/objectstack#10235

Scope (after the upstream signal lands and the spec pin covers it)

1. Grid/table headers drop the sort affordance on any column the served metadata marks unsortable — the click ceases to exist, so neither the silent-unordered behavior (today) nor the 422 refusal (post-#9313) is reachable from the UI.
2. The personalization PUT is never issued for such a column.
3. ⛔ No local "formula ⇒ unsortable" fallback derivation — if the signal is absent on the pinned spec version, this card is not ready (that is what the Blocked-by: is for), not a license to shadow-derive.

Oracle: the three measured refusal cells from the upstream card (crm_opportunity.expected_revenue ×2 views, showcase_project.budget_remaining) must become unofferable clicks; a sortable control column on the same grids keeps its affordance (both directions pinned).

Refs: objectstack-ai/objectstack#10235 (ruling + spec leg) · objectstack#9313 / PR #10234 (the widening that makes today's click loud).

[os-sam]

Upstream note from the objectstack spec seat (session_01RadETjNRLALFLhFA3xehZP): the spec/rest leg (objectstack-ai/objectstack#10235, PR objectstack-ai/objectstack#11214) is ACCEPTED and heading for the merge queue. The served contract this card consumes is an envelope-level sortability key on GET /api/v1/meta/object/:name — { fields: { [fieldName]: { sortable, reason?, caveat? } } }. Consumer contract as shipped: offer a sort affordance iff an entry exists AND says sortable: true; absence means "no platform sort behind this name", never "assume sortable"; do not re-derive anything from field type.

One affordance question is deliberately left to THIS card, recorded here so it is not lost: entries with sortable: true, caveat: 'unprovisioned-anchor' (platform-injected anchors on ADR-0015 external objects) are ACCEPTED by the runtime but silently degrade (asc === desc under a 200) when the remote table lacks the column — unprovable either way at serve time. Options: A keep the click (status-quo enforcement semantics; caveat available for badging) · B drop the affordance on caveated columns · C click + degraded-order warning. Default is A until ruled here — refusing what the platform does not refuse would recreate declared≠enforced drift in mirror image.

Blocked-by: clears when the upstream PR reaches MERGED; verify on the merged ref before dispatching, per the unlock discipline.

---

Generated by Claude Code

[os-zhuang]

Unlock scan (triage seat, 2026-08-23 round): pm:blocked → pm:queue. Release double-check passed — the most recent stated condition (objectstack#10235, its spec/rest leg PR objectstack#11214) is discharged: #10235 is CLOSED (04:38Z, after the spec seat's 04:12Z ACCEPT note), and no newer merged PR sits on this card.

Requeue obligations for the ui seat, per the unlock discipline:

1. Verify on the merged ref before dispatching — read the landed sortability envelope shape from objectstack#11214's merged diff, not from this thread's description of it.
2. The consumer contract as shipped binds: affordance iff an entry exists AND sortable: true; absence never means "assume sortable"; ⛔ no local "formula ⇒ unsortable" shadow derivation (scope item 3 stands).
3. The caveat: 'unprovisioned-anchor' affordance question stays with this card, default A (keep the click) until ruled here — refusing what the platform does not refuse would recreate declared≠enforced drift in mirror image. If the implementer wants B or C, that is a ruling to request, not a choice to make.
4. Runtime dependency, not only a pin: the oracle cells need a served backend that carries the #11214 change — confirm the dev-stack framework version before reading the three refusal cells as red.

---

Generated by Claude Code

[yinlianghui]

Claim: PM loop round 38 (refill slot)
Session: session_01CSoz9uGhaaSgiq3hshtN7L
Branch: claude/issue-5729-column-sortability-signal
Worktree: objectui-issue-5729
Domain: domain:ui
File surface: the grid/table header sort affordance and the personalization PUT path — start in packages/plugin-grid. ⚠️ packages/components is CONDITIONAL: #6014 is in flight and fenced to report before writing there, so ⛔ if your fix needs packages/components, say so in the report before you write it, so the two cards cannot collide silently.
Container & model: M, mode:subagent, model: opus
Clause-②: likely yes — this consumes a served contract and changes what the UI offers. Declared; Opus under this seat's recorded Fable-quota exemption.
⚠️ Serial: siblings in flight — #5725 (app-shell/.../metadata-admin/previews/), #6014 (packages/plugin-tree), #5876 (packages/plugin-dashboard), #5828 (app-shell/src/console/__tests__/). Landing this round and touching adjacent sort logic: #6088 (#5795, related-list inherited sort — app-shell/src/utils/deriveRelatedLists.ts, views/RecordDetailView.tsx, plugin-detail/src/synth/). ⛔ Do not touch plugin-detail.

裁决 — the ruling, and the four requeue obligations

Ruled upstream (maintainer 2026-08-23, objectstack#10235 ruling A): the platform serves an explicit per-column sortability signal; the grid reads it and never re-derives "virtual ⇒ unsortable" from field type. The unlock scan released this card with four obligations, all binding:

1. ⛔ Verify the landed envelope shape from objectstack#11214's MERGED DIFF, ⛔ not from this thread's description of it. The thread says it is an envelope-level sortability key on GET /api/v1/meta/object/:name — { fields: { [fieldName]: { sortable, reason?, caveat? } } }. ⚠️ Treat that as a claim to check, not a fact. You have the objectstack checkout; read the merged diff. If the shape differs in any way, report the delta before coding against it.
2. The consumer contract as shipped binds: offer a sort affordance iff an entry exists AND says sortable: true. ⛔ Absence means "no platform sort behind this name" — never "assume sortable". ⛔ No local "formula ⇒ unsortable" shadow derivation; scope item 3 of the card stands. ⚠️ Note the asymmetry: absent ⇒ no affordance is not the same rule as sortable: false ⇒ no affordance, and a naive !== false check gets the absent case exactly backwards.
3. ⛔ The caveat: 'unprovisioned-anchor' question is NOT yours to decide. Platform-injected anchors on ADR-0015 external objects come back sortable: true, caveat: 'unprovisioned-anchor': accepted by the runtime but silently degrading (asc === desc under a 200) when the remote table lacks the column, and unprovable either way at serve time. Options were A (keep the click) · B (drop the affordance) · C (click + degraded-order warning). Default is A — keep the click — until ruled on this card. The recorded reason: refusing what the platform does not refuse would recreate declared≠enforced drift in mirror image. ✅ If you think B or C is right, request a ruling in your report; ⛔ do not implement it.
4. ⚠️ Runtime dependency, not just a pin. The oracle cells need a served backend carrying #11214. Confirm the dev-stack framework version before reading any refusal cell as red — a "correctly unofferable" click and "the backend never sent a sortability key" look identical from the UI. ⛔ If the served stack predates #11214, say so and pin against the contract with unit-level fixtures instead of claiming an oracle you could not run.

Oracle (from the upstream card, both directions required): crm_opportunity.expected_revenue (×2 views) and showcase_project.budget_remaining must become unofferable clicks; a sortable control column on the same grids keeps its affordance.

Scope — three items, and the third is a prohibition

1. Grid/table headers drop the sort affordance on any column the served metadata marks unsortable — the click ceases to exist, so neither today's silent-unordered behaviour nor the post-#9313 422 refusal is reachable from the UI.
2. The personalization PUT is never issued for such a column. ⚠️ This is a separate leg from the affordance and needs its own assertion — a hidden affordance whose PUT still fires on a restored/persisted state is exactly the half-fix this item exists to prevent. Check the restore path, not only the click path.
3. ⛔ No shadow derivation, as above.

PM mechanism assumptions — measure, do not inherit

1. ⚠️ Where the affordance actually lives is unmeasured from this seat. packages/plugin-grid/src/ObjectGrid.tsx is my candidate for the header sort and the $orderby path, but the table may render its own header. Establish the real read point with a counter-probe before editing, and report it.
2. ⚠️ The signal has to reach the renderer, and that path may not exist yet. The envelope is on the metadata response; whatever holds the object schema client-side must carry sortability through to the column. ⛔ If it is dropped in transit (a narrowing type, a hand-built projection), that is the real work of this card — say so rather than reading the drop as "the platform sent nothing".
3. ⚠️ A "no affordance" assertion is trivially satisfiable by rendering no header at all. Every negative leg needs the positive control in the same render: a sortable sibling column on the same grid, still clickable, still issuing its $orderby. Without it, "the click is gone" is also true of a broken grid.
4. ⚠️ Adjacent, in flight, do not collide: feat(app-shell,plugin-detail): derived related lists inherit the child object's default list view sort #6088 lands related-list inherited sort this round, and it normalises sort through @object-ui/core's convertSortToQueryParams — the repo's single definition of both sort dialects. ✅ If you touch sort-string handling, reach that helper rather than adding a parallel reader.

Verification

Predict the direction before running. Prove every mutation on disk by grepping the injected text and, separately, the removed text; ⚠️ print the landing site; ⚠️ assert anchor uniqueness before writing; ⚠️ restore under trap … EXIT INT TERM with a cwd-independent command and confirm git diff HEAD --stat is empty. Every zero-hit grep needs a known-present control; every negative assertion needs a green counter-probe.

Gates by name, with exit codes: pnpm --filter @object-ui/plugin-grid type-check (⚠️ hyphenated; echo the script name; distinguish the unbuilt-closure red — Cannot find module @object-ui/... — from the missing-node_modules red), root-form vitest over each package you touch quoting per-test names, the downstream prefix-form sweep with the contract direction stated (⚠️ known gotcha, not a finding: it fails at apps/site and packages/components until @object-ui/react-runtime is built separately), and eslint with merge-base delta (⚠️ plain eslint .; ⛔ no --no-inline-config). Run node scripts/check-changeset-presence.mjs rather than guessing — ⚠️ #6073 landed today and widened that gate's notion of a package's source beyond /src/. Changeset: patch for behaviour, minor if a public type changes; ⛔ never major.

⚠️ Standing rule from #5874 this round: derive your gate set by enumerating each CI job's own step list, ⛔ not from top-level script names — check:esm-specifiers runs as a step inside the Type Check job under a name that does not read like one, and that class of miss turned a PR red today.

Deliverable

Draft PR, body with Fixes #5729. ⛔ Do not mark ready, ⛔ do not enqueue, ⛔ no auto-merge — the PM lands it. Post the terminal report here (plain-text first-line marker os-dev-report; ⛔ avoid short angle-bracket placeholders in prose — they render as HTML and vanish) and return it. State, per gate: command, exit code, what a red would have meant; the measured envelope shape from the merged diff versus the shape described above; the served framework version and whether the oracle was actually runnable; the measured answer to each of assumptions 1–4; whether you needed packages/components; and any ruling you are requesting rather than taking.

---

Generated by Claude Code