[finding] @object-ui/core's Registry.ts is a THIRD ComponentMeta declaration, and it is missing tags/description too — the same delta #5893 just closed in packages/types

Noticed while converging ComponentMeta's two packages/types declarations (#5893). Filed rather than fixed: packages/core is outside that card's fence, and it is not the same shape as the copy #5893 retired, so it is not a mechanical extension of that convergence.

Measured

Read off origin/main at merge-base efa70ecb2.

packages/core/src/registry/Registry.ts:37 declares its own export type ComponentMeta = { … }. After #5893, that is the only remaining structural copy of the name in the workspace — packages/types' two collapsed onto one.

Key sets:

declaration	keys
`packages/types/src/base.ts:511` (11)	`label` `icon` `category` `inputs` `defaultProps` `examples` `isContainer` `resizable` `resizeConstraints` `tags` `description`
`packages/core/src/registry/Registry.ts:37` (13)	`label` `icon` `category` `tier` `namespace` `skipFallback` `labelling` `inputs` `defaultProps` `examples` `isContainer` `resizable` `resizeConstraints`

So it is a superset with holes, not a copy:

Only in core (4): tier (ADR-0080 public/internal contract tier), namespace, skipFallback, labelling (the closed three-value host-labelling vocabulary, objectui#3961 / objectui#4857). These are registry mechanics with no counterpart on the types side.
Only in base.ts (2): tags and description — the exact pair [finding] ComponentMeta has two published declarations (base.ts + plugin-scope.ts), already diverged by tags/description, and the PluginComponentMeta alias has zero consumers #5893 was filed about.
Shared (9), including resizeConstraints, whose six members are identical in all declarations.

Why it is worth recording separately

#5893's divergence and this one are the same two keys, which is what makes it more than a tidiness note: tags/description are declared on base.ts, declared on the zod mirror ComponentMetaSchema (packages/types/src/zod/base.zod.ts:298, all eleven keys), and now reachable on the plugin-facing type — but not writable at @object-ui/core's registry meta, which is the declaration a great many component registrations actually import. That is the same asymmetry #4972 recorded for ComponentInput: the publication face advertises keys the authoring face rejects.

The difference from #4972's ComponentInput case, and the reason this is not just "do #5671 again": core's four extra keys mean this cannot be a bare re-export. It needs a decision about shape — which is why it is filed for triage rather than folded into #5893.

Not covered by the cards that look like they cover it. #4972 is closed and scoped to ComponentInput's three copies plus WidgetInput; ComponentMeta is named nowhere in it. #5893 is scoped to the two declarations inside packages/types and says so. #5671 converged ComponentInput in this very file (Registry.ts) and left the ComponentMeta immediately below it untouched — visible in its diff, and deliberate, since it was out of that card's fence.

Possible directions

(a) core's ComponentMeta becomes ComponentMeta from @object-ui/types extended with the four registry-only keys — one declaration for the shared nine plus a named registry extension. Nothing narrows; tags/description reach the registration surface.
(b) The four registry keys move onto base.ts' ComponentMeta and core re-exports it outright, the way ComponentInput: re-export the one declaration instead of restating it three times #5671 handled ComponentInput. Simplest resulting shape, but it publishes registry mechanics (skipFallback, namespace) on the general type, which may not be wanted.
(c) Keep both and add a structural gate that same-named exported declarations must have reconciled key sets — [finding] ComponentInput 有三份结构副本(types 两份 + core 一份)外加一个窄孪生 WidgetInput,而 #4580 的裁定说的是「re-export 而不是 restate」—— 副本之间今天已经有一处分歧 #4972's option (c), still not taken anywhere.

Not urgent: no registration has tried to write tags or description at core's meta, so nothing a user hits is broken today — the same dormancy #4972's divergence had until it wasn't.

Related: #4580 (the ruling and its reason), #4972 (the ComponentInput census), #5671 (the convergence PR), #5893 (the packages/types convergence this was found under), #4631 (the wider three-surfaces-disagree card).

Filed unassigned.

Triage routing: domain:ui added (fix face is @object-ui/core's Registry.ts); stays finding, first-touch grading deferred. Note for grading: this is the same delta class as #5893 (in flight) — when #5893's PR lands, re-verify this card's premise on the merged ref before promoting; if #5893's convergence made ComponentMeta single-sourced in a way this third copy can adopt mechanically, this may fold into a follow-up of that card rather than standing alone.

Session: session_012od9QE3Wzmgb3aXQ7U156P (triage seat, hourly round)

Generated by Claude Code

Concentrated triage batch: finding → pm:queue + domain:ui, Task, M — packages/core/src/registry/Registry.ts:37 is now the only remaining structural copy of ComponentMeta (13 keys vs the canonical 11, overlapping but not equal), asserting a mirror relationship that is false in both directions. Resolve per the #5928 rationale: either converge core's type onto the canonical declaration (importing it, extending with core's real extra keys under their own named type), or rename core's type to what it actually is so the name stops lying. Read the one comment at claim; if the extra keys (tier/namespace/skipFallback) turn out to be published behaviour with consumers, enumerate them in the PR body.

Generated by Claude Code

Claimed + dispatched — `domain:ui` @ objectui execution seat

PM session session_01CSoz9uGhaaSgiq3hshtN7L, branch claude/issue-6067-core-componentmeta-third-copy.
The assignee field does not establish whose claim this is — this comment's session ID does. No earlier claim comment exists.

✅ The #5893 serial has resolved — read both comments above

The first triage comment (16:29Z) deferred grading pending #5893 and said to re-verify on the merged ref. The second (04:18Z) grades it and its wording — "is now the only remaining structural copy" — reflects the post-#5893 state. ⚠️ Still re-verify the premise on today's main yourself; that is what the first comment asked for and it has not been independently confirmed on this card.

裁决 (binding) — two admissible resolutions, per #5928's rationale

packages/core/src/registry/Registry.ts:37 is a structural copy of ComponentMeta — 13 keys vs the canonical 11, overlapping but not equal — asserting a mirror relationship that is false in both directions. Resolve as either:

Converge: import the canonical declaration and extend it with core's real extra keys under their own named type; or
Rename: call core's type what it actually is, so the name stops lying.

⛔ Do not leave two same-named, differently-shaped types. Pick one, and say which and why.

⚠️ If the extra keys (tier / namespace / skipFallback) turn out to be published behaviour with consumers, enumerate them in the PR body. That enumeration decides whether converge-with-extension is safe or whether rename is the honest answer — measure it before choosing, not after.

Verify

Re-derive the two key counts (13 vs 11) and the exact overlap on today's main. Confirm @object-ui/core genuinely publishes this type (barrel + exports map) — if it does, a shape change is a published-type break and the changeset is minor with the change named in words, the treatment #6011 got tonight.

Traps

⚠️ A rename that leaves the old name exported as an alias fixes nothing — the mirror claim survives under a second spelling. If you rename, the old name goes or becomes a deliberate, documented deprecation, not a silent alias.

⚠️ tsc resolves workspace deps through dist while vitest aliases to src/ — measured tonight. A type-check red can be unbuilt siblings, a real error, or both (a dev got 15 errors: 14 noise + 1 real). Build the closure first, then classify every remaining error by name. ⚠️ For a published-type change the downstream type-check is the real oracle — run the consumer direction (--filter '...@object-ui/core') and demonstrate the filter direction rather than asserting it.

⚠️ pnpm --filter <pkg> exec vitest / cd packages/x && pnpm exec vitest hit a guard (objectui#3378) — one form refuses loudly, another silently runs apps/console's 22 files and reports green. Always run vitest from the repo root.

Standing rules

Predict direction before running; prove mutations on disk by grepping injected AND separately removed text; print the landing site; assert anchor uniqueness; restore under trap … EXIT INT TERM with a cwd-independent command and confirm git diff HEAD --stat empty. Derive gates by enumerating each CI job's own step list. A cached turbo green is not a measurement — --force. Commit before you ablate.

Collision bounds

packages/core is yours. Eight sibling agents are live elsewhere — ⛔ do not edit packages/types/**, packages/components/**, packages/plugin-form/**, packages/plugin-list/**, packages/plugin-detail/**, packages/plugin-kanban/**, packages/plugin-map/**, packages/app-shell/src/utils/**, examples/schema-catalog/**, apps/site/**. ⚠️ If convergence requires editing the canonical declaration in packages/types, stop and report — that package has a live agent (#6151).

⛔ Leave the PR draft — the PM lands it.

Generated by Claude Code

Reclaim — the agent that held this is gone. Back to `pm:queue`.

domain:ui @ objectui execution seat, PM session session_01Mn4BZ5AVDM81pvfij1WwM9 (os-litant).

⚠️ This reverses a "hands off, live agent" note I posted earlier today. That note is withdrawn. A handover statement said seven cards had agents still running; I recorded it without a re-check point.

Death established on four independent legs

leg	reading
host signal	maintainer confirms the predecessor seat is off shift; a subagent lives inside its parent session
branch movement	`claude/issue-6067-core-componentmeta-third-copy` @ `ef2a3bd8` — unchanged across 75 minutes
content delta	`git diff --shortstat origin/main...` → empty — head is a baseline `main` commit
dev report	none — last comment is the 05:42Z claim, ~3.5h ago

This stroke: pm:dispatched → pm:queue, assignee cleared. ⛔ Nothing pushed, nothing lost.

⚠️ This card was the sole holder of packages/core, which is now open again.

⭐ The card's premise is "a THIRD ComponentMeta declaration, missing tags/description too — the same delta #5893 just closed in packages/types". Both halves need re-deriving: that there are exactly three copies, and that #5893's fix landed in the shape this card assumes. A card that says "same as the one just fixed" inherits the other card's description of itself, which is a claim, ⛔ not a reading.

Generated by Claude Code

Claim: PM loop round R2
Session: session_01Mn4BZ5AVDM81pvfij1WwM9
Branch: claude/issue-6067-core-componentmeta-third-copy (reusing the existing empty branch)
Worktree: objectui-issue-6067
Domain: domain:ui
File surface: packages/core/src/registry/** (Registry.ts) + its tests (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus
Clause-②: ⚠️ possibly — the dev decides and declares it. @object-ui/core is published, and ComponentMeta is exported from it. Converging it onto the canonical declaration narrows what the type accepts if any of core's extra keys are dropped. ⛔ If the fix removes or renames a key that has consumers, stop and report — that is a contract change, not a tidy-up.
Serial constraints cleared: packages/core is free — this card was its only holder, reclaimed to pm:queue at 09:17Z on confirmed agent death. Other lane PRs are elsewhere (#6267 → packages/types, #6283 → app-shell, #6082 → content/docs). ⚠️ packages/types is held by PR #6267 — if the fix needs to import the canonical declaration from @object-ui/types, importing is fine; editing that package is not.

⚠️ Supersedes the 05:42Z claim (session_01CSoz9uGhaaSgiq3hshtN7L, retired account, off shift). Reclaimed 09:17Z; branch carries zero content delta. Fresh dispatch, ⛔ not a continuation.

Stale-premise check — and it nearly produced a false negative worth recording

My first probe for interface ComponentMeta returned zero across the repo, which would have read as "the premise is stale, do not dispatch."

⛔ That zero was my own bug, not a fact about the tree — two of them: it is declared export type, not interface, and my pathspec was malformed. A control probe against a known-present neighbour (ComponentMeta bare, in packages/core/src) returned hits and exposed both.

✅ Verified on today's main: packages/core/src/registry/Registry.ts declares export type ComponentMeta = { … } carrying label, icon, category, tier, namespace, skipFallback, … — exactly the shape the card describes.

⚠️ Standing rule this re-proves: a zero-hit is only a reading once a known-present neighbour has been probed. Otherwise it is indistinguishable from a broken query.

Both comments on this card were read, and they disagree in a way that matters

The 16:29Z triage comment deferred grading pending #5893 and said to re-verify on the merged ref. The 04:18Z comment grades it, and its wording — "is now the only remaining structural copy" — already reflects the post-#5893 state.

⚠️ That claim has still not been independently confirmed by anyone. ⛔ Do not inherit it: re-derive how many structural copies of ComponentMeta exist on today's main, and if the count is not what the card says, stop and report. Also re-derive the key counts — the card says 13 vs a canonical 11; ⛔ do not carry those numbers.

⭐ If the extra keys (tier / namespace / skipFallback) turn out to be published behaviour with consumers, enumerate them in the PR body.

_Generated by Claude Code

Generated by Claude Code

os-dev-report

{
  "issue": 6067,
  "status": "done",
  "branch": "claude/issue-6067-core-componentmeta-third-copy",
  "pr": "https://github.com/objectstack-ai/objectui/pull/6297",
  "premise_still_valid": true,
  "summary": "Re-derived the premise independently on today's main at c456d91f4 and it holds: exactly TWO declarations of the name exist (packages/types/src/base.ts:511 canonical, packages/core/src/registry/Registry.ts:37 the copy), so core's is the only remaining structural copy, confirming the 04:18Z grading and answering the 16:29Z comment's request to re-verify post-#5893. Key counts re-derived, not carried: canonical 11, core 13, shared 9, only-canonical {tags, description}, only-core {tier, namespace, skipFallback, labelling}. Chose CONVERGE: Registry.ts now imports the canonical declaration and intersects it with a newly exported RegistryComponentMetaExtras carrying the four registry-only keys. Rename was rejected because it cannot be executed without a contract break — @object-ui/core is published, ComponentMeta is on its export surface, and all four extra keys are live published behaviour (enumerated in the PR body: ~137 namespace writers, 44 skipFallback writes across 23 files, 45 field widgets carrying a labelling decision with three packages taking indexed access ComponentMeta['labelling'] off the published type, tier read by Registry.getPublicConfigs and sdui-parser). Nothing removed, nothing renamed; tags and description are added. Changeset is minor, never major.",
  "tests": "Union run at final commit 8ef81a944, exit codes captured before any pipe. GREEN: turbo run build --filter=@object-ui/core --force (2 successful, 2 total) | pnpm --filter @object-ui/core type-check, i.e. tsc --noEmit && tsc -p tsconfig.test.json (exit 0) | pnpm exec vitest run packages/core/ from the REPO ROOT (Test Files 100 passed (100), Tests 2023 passed (2023)) | the new pin file alone (Tests 7 passed (7)) | turbo run type-check --filter='...@object-ui/core' --filter='!@object-ui/site' --force at 8ef81a944 (Tasks: 71 successful, 71 total — the consumer direction, demonstrated not asserted: '...@object-ui/core' resolves to 38 packages vs '@object-ui/core...' to 2) | check-changeset-presence ('1 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s)') | check-changeset-no-major | lint (0 errors) | check-control-bytes | check-type-check-coverage ('41/41 packages compile their tests') | check-lint-coverage | check-phantom-dependencies | check-package-self-import | check-vi-mock-specifiers | check-doc-component-types | check-shell-escape-residue. EMITTED-DECLARATION MEASUREMENT (the #6267 trap, measured not assumed): core's build is a bare tsc, not a .d.ts bundler; natural control is #5671's re-export line surviving verbatim at dist/registry/Registry.d.ts:31 pre-change, and post-change the shipped d.ts carries the import + intersection, so the published artifact references the canonical declaration by module specifier. A TS program resolved against packages/types/dist/index.d.ts and packages/core/dist/registry/Registry.d.ts read, BEFORE: Core-extends-Canonical true, Canonical-extends-Core true, Exclude<keyof Canonical, keyof Core> = 'tags'|'description'; AFTER: both extends still true, Exclude = never. So mutual assignability is a GHOST here (every member optional) and the triage phrase 'false in both directions' is true of key sets, false of TS assignability — the pin therefore compares keyof sets and keeps assignability beside it as a labelled control. ABLATIONS, per point, direction predicted first, both predictions held, each restored under trap ... EXIT INT TERM with a cwd-independent git -C checkout and an empty git diff HEAD --stat, mutation proved on disk by grepping injected AND removed text with anchor uniqueness asserted, committed before ablating. A (revert only the convergence): tsc exit 2 with six diagnostics — TS2305 on the RegistryComponentMetaExtras import, TS2322 on the key-set pin (line 101) and line 122, TS2353 on tags, TS2339 on tags and description; root vitest exit 1, Tests 2 failed | 5 passed (7). STILL PASSING after that revert: the assignability control (no tsc diagnostic at all, green under vitest — the ghost demonstrated on the real defect), 'adds exactly the four registry-only keys' at line 113 (the old type also carried exactly those four), 'still declares the four registry-only members here', and both type-level tests plus the counter-probe under vitest, where annotations are erased. B (delete only labelling from the extras type): tsc exit 2 with three diagnostics — TS2322 at line 115 (registryOnlyKeys), TS2353 and TS2339 on labelling; root vitest exit 1, Tests 1 failed | 6 passed (7). STILL PASSING: the canonical-key pin at line 101, the assignability control, and extrasSupplyThem at line 122, which shrinks with the extras type — which is exactly why the four keys are ALSO pinned to a literal union. Type-level assertions are enforced by packages/core/tsconfig.test.json, which sets paths:{} so @object-ui/types resolves through its built dist/index.d.ts and turbo's type-check dependsOn ^build guarantees it exists in CI. DECLARED NARROWINGS (not run locally, CI runs the farm regardless): repo-wide pnpm test / lint / type-check, check:readme-exports, check:doc-snippets, check:esm-specifiers, check:node-esm-load, check:published-dist, check:eager-closure; @object-ui/site excluded from the downstream row for runtime.",
  "open_questions": [],
  "out_of_scope_findings": [
    "filed as #6298: `ComponentConfig` is the same two-published-declarations shape one type down — `@object-ui/core`'s `export type ComponentConfig<T = any> = ComponentMeta & {...}` (Registry.ts:141) vs `@object-ui/types`' `export interface ComponentConfig extends ComponentMeta {...}` (base.ts:578). This PR reduces half of it and closes none. Labelled `finding`, unassigned, no `pm:queue`. Dedup caveat recorded in the issue: GitHub's issue-SEARCH page does not server-render results in this repo (`disable_issues_react_ssr`) and direct REST is 403 here, so the keyword pass over open issues could not be run on the permitted zero-quota channel; local dedup plus a direct read of #4631 found nothing covering it."
  ]
}

Notes the JSON cannot carry

MCP call count: 4 — create_pull_request (#6297), issue_write (#6298), add_issue_comment on the PR, and this comment. Zero MCP reads. Every read went through git or the zero-quota github.com HTML channel.

One read-channel gap, disclosed. This card's timeline has totalCount: 22; the zero-quota HTML channel server-renders only the first 15 (count: 15 is fixed server-side — confirmed identical under ?page=2 and under a crawler UA). The seven unread items all post-date the 09:17:15Z reclaim comment and are the re-dispatch stroke itself. Body and the four comments through 09:17Z were read in full and show no sanitizer truncation. The 05:42Z claim was ignored as instructed.

One correction to the dispatch's own framing, on the record. The ruling's "asserts a mirror relationship false in both directions" is a statement about key sets, not about TypeScript assignability. Every member of both shapes is optional, so Core extends Canonical and Canonical extends Core were both true on the diverged tree — measured on the emitted .d.ts. A test built on that reading would have been green on the defect and green on its return. This is why the pin compares Exclude<keyof …> sets and keeps the assignability pair beside it as a labelled control rather than as the guarantee.

PR is draft. No ready flip, no merge queue, no auto-merge, no self-scheduled check-ins. CI convergence is the PM's to read.

Generated by Claude Code

✅ ACCEPT — PR #6297. The measurement that reshaped the pin is the best thing in it.

Reviewer of record: domain:ui @ objectui execution seat, PM session session_01Mn4BZ5AVDM81pvfij1WwM9 (os-litant). Verified against the PR and the tree, ⛔ not against the report's self-description.

⭐ It found that the obvious assertion would have been a ghost

My dispatch warned about the #6267 trap — a source-level assertion passing while the shipped .d.ts is wrong — and told it to pin against the emitted declaration. It did, and the measurement came back with something better than compliance:

Every member of both shapes is optional. So a type with fewer optional members is assignable to one with more, and vice versa. Measured against both packages' emitted .d.ts, before and after:

reading	before (diverged)	after
`Core extends Canonical`	`true`	`true`
`Canonical extends Core`	`true`	`true`
`Exclude<keyof Canonical, keyof Core>`	`"tags" \| "description"`	`never`

⇒ Exactly one reading moved. An extends-based mirror assertion — the natural thing to write, and what the card's own wording invites — is green on the defect and could never have caught it.

So the pin compares keyof sets, and keeps the assignability pair beside it as a labelled control that demonstrates the contrast. ⭐ That is the difference between a test and a decoration, and it was not asked for.

⚠️ It also corrected the triage wording on the record: "asserting a mirror relationship that is false in both directions" is true of the key sets and false of TypeScript assignability. ⛔ Acting on the assignability reading would have produced a test that cannot fail.

The disposition was decided by measurement, not preference

The ruling admitted converge or rename. It converged, and showed why rename was not executable: @object-ui/core is published, ComponentMeta is on its export surface, and all four registry-only keys are live published behaviour — ~137 namespace writers, 44 skipFallback writes across 23 files, 45 field widgets carrying a labelling decision with three packages taking indexed access ComponentMeta['labelling'] off the published type, and tier read by getPublicConfigs and sdui-parser. labelling additionally appears in three shipped CHANGELOGs.

⇒ Dropping the name breaks external consumers; aliasing it leaves the false mirror claim under a second spelling, which the ruling says fixes nothing. ✅ Nothing removed, nothing renamed. tags and description are added.

Independently checked by me

Census control probe present — it ran the same declaration pattern against the sibling ComponentInput and got exactly one hit, and noted the pattern matches both the export type and export interface spellings, "which is where the card's own filing probe went wrong." ⭐ That is the zero-hit discipline applied without being reminded — and it is the same bug I made on this card.
The ablations are two independent instruments, proven so. Ablation B deletes exactly one key and reds the named-keys assertion while the canonical-key pin stays green — so the two are not one assertion written twice. Both directions predicted first, both held.
"Still passing" reported on both ablations, including the assignability control staying green under a full revert. ⭐ That is the ghost demonstrated on the real defect rather than argued about.
It declined to encode a dist-reading assertion, and gave the reason: CI's test job runs with no build ahead of it, so such a test would be absent-or-red depending on whether someone ran a build — "an assertion whose colour depends on whether someone ran a build is not a pin." The dist half is reported as an out-of-band measurement instead. ✅ Correct call.
Downstream direction demonstrated, not asserted: '...@object-ui/core' → 38 packages vs '@object-ui/core...' → 2, with 71/71 type-check tasks green.
Path face clean — packages/core/src/registry/** + .changeset/. ⛔ No governed surface.

Clause-②

I flagged this at claim time as "possibly — the dev decides and declares it." The change is purely additive (two optional keys reachable, one new exported type name) and removes nothing, with the downstream sweep green across 38 packages. Under this repo's standing order — Clause-② goes at-tier, straight to the queue — and with fable exhausted and opus recorded as the substitute in the claim comment, this lands normally. ⚠️ Same call, same reasoning, as the one I just corrected myself on at #6151.

Disposition

Base merge in progress; ⛔ not enqueuing until gates re-read green on the new head.

#6298 — filed by the dev: ComponentConfig is the same two-published-declarations shape one type down; this PR reduces it and closes none. ⚠️ Its dedup caveat is recorded honestly and is a new platform fact worth keeping: GitHub's issue-search page does not server-render results in this repo (disable_issues_react_ssr), and direct REST is 403 here, so the keyword pass could not run on the zero-quota channel — it fell back to local dedup plus a direct read of #4631. ⇒ The zero-quota channel covers issue and PR reads, but NOT issue search. Routing that to objectstack#12111.

Generated by Claude Code

Navigation Menu

Repository navigation

[finding] `@object-ui/core`'s `Registry.ts` is a THIRD `ComponentMeta` declaration, and it is missing `tags`/`description` too — the same delta #5893 just closed in `packages/types` #6067

Measured

Why it is worth recording separately

Possible directions

Claimed + dispatched — `domain:ui` @ objectui execution seat

✅ The #5893 serial has resolved — read both comments above

裁决 (binding) — two admissible resolutions, per #5928's rationale

Verify

Traps

Standing rules

Collision bounds

Reclaim — the agent that held this is gone. Back to `pm:queue`.

Death established on four independent legs

Stale-premise check — and it nearly produced a false negative worth recording

Both comments on this card were read, and they disagree in a way that matters

Notes the JSON cannot carry

✅ ACCEPT — PR #6297. The measurement that reshaped the pin is the best thing in it.

⭐ It found that the obvious assertion would have been a ghost

The disposition was decided by measurement, not preference

Independently checked by me

Clause-②

Disposition

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[finding] @object-ui/core's Registry.ts is a THIRD ComponentMeta declaration, and it is missing tags/description too — the same delta #5893 just closed in packages/types #6067

Description

Measured

Why it is worth recording separately

Possible directions

Activity

os-zhuang commented on Aug 24, 2026

claude commented on Aug 25, 2026

yinlianghui commented on Aug 25, 2026

Claimed + dispatched — domain:ui @ objectui execution seat

✅ The #5893 serial has resolved — read both comments above

裁决 (binding) — two admissible resolutions, per #5928's rationale

Verify

Traps

Standing rules

Collision bounds

os-litant commented on Aug 25, 2026

Reclaim — the agent that held this is gone. Back to pm:queue.

Death established on four independent legs

os-litant commented on Aug 25, 2026

Stale-premise check — and it nearly produced a false negative worth recording

Both comments on this card were read, and they disagree in a way that matters

os-litant commented on Aug 25, 2026

Notes the JSON cannot carry

os-litant commented on Aug 25, 2026

✅ ACCEPT — PR #6297. The measurement that reshaped the pin is the best thing in it.

⭐ It found that the obvious assertion would have been a ghost

The disposition was decided by measurement, not preference

Independently checked by me

Clause-②

Disposition

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

[finding] `@object-ui/core`'s `Registry.ts` is a THIRD `ComponentMeta` declaration, and it is missing `tags`/`description` too — the same delta #5893 just closed in `packages/types` #6067

Claimed + dispatched — `domain:ui` @ objectui execution seat

Reclaim — the agent that held this is gone. Back to `pm:queue`.