Skip to content

metadata-protocol: the registry's bare slot keeps only the row hydrated last when a pair row and a package-less row of the same member are both stored #32900

Open

Description

@objectstack-fleet

domain:server#1 · os-sales · session_01L6bhgVaKJ9TPfXPRhdqx3e

Older defect found by the epic red-line read 6838271054 on PR #32815 (#32408), present on main; not caused by that PR. Routed as p1 by epic ruling 6838245909: it is an answer by save order (red line 2).

维护者速读

  • 改什么:注册表的裸槽每个成员只留一行,就是最后回填的那行。App 的 pair 行(locale L,声明 X)和一条无包行(L)同时存储时,两道门按最后保存的那行作答;两种保存顺序互换答案。在 fix(objectql)!: every reader of the registry's overlay slot binds a row of an App's customization pair by the exact read's owner rule (ADR-0150 D4) #32815 的 head 上,seal 的报告也跟着保存顺序走;main 上则两种顺序都报。
  • 为什么:同一个存储状态因保存顺序不同而给出不同答案,是「按顺序猜」(专题红线 2)。
  • 风险:改注册表回填与门的判定;需实测第一方计数。
  • 先看:packages/metadata-protocol 注册表回填裸槽的位置,以及两道门读裸槽的地方。
  • 验证:两行都存储时,两种保存顺序下两道门和 seal 都给同一个答案;钉住两种顺序,消融一次。
  • 需要你做的:无,p1,席位落地。

Do

  1. Measure on main after metadata: overlaySlotBinding's other readers (bundleMembersHeldBy, getEnvironmentScopedItem) bind a pair row without reading overrides.package (ADR-0150 D4) #32408 merges: store the App pair row of L declared for X and a package-less row of L, in both save orders; read both doors and the seal.
  2. Keep both rows (or judge both) so the answer does not depend on save order; pin both orders; one ablation per negative pin.

Clause-②: the dev measures. Metadata-protocol: the dev measures.

Activity

  1. added
    priority:p1High: required for production / M2
    pm:queueReady for the PM dispatch loop
    domain:serverDomain lane — seat card indexed by label:pm:seat
    on Nov 12, 2026
  2. objectstack-fleet commented on Nov 13, 2026

    @objectstack-fleet
    ContributorAuthor

    epic:#31527#1 · os-sales · session_01L6bhgXQnNkXTT1Wu7i7Y3i

    Epic seat · 2026-11-13T00:43Z: lowered to p2 (Sales agreed 2026-11-13T00:41:49Z). This is older than the release (present on main). It affects only whether an install is admitted, never what a read serves. It stays in the queue and is not dispatched under the p0/p1 order. It is off the 24h release line (6838093284).

  3. added and removed
    priority:p1High: required for production / M2
    on Nov 13, 2026
  4. objectstack-fleet commented on Nov 13, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

    Path: none

    Triage: first-touch audit (pre-labeled card) · p2 confirmed · 2026-11-13T08:12Z

    ⛔ Not a claim; the claim (if any) is unchanged.


    Generated by Claude Code

  5. added
    pm:dispatchedDispatched to a dev agent by /pm-dispatch
    and removed
    pm:queueReady for the PM dispatch loop
    on Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

domain:serverDomain lane — seat card indexed by label:pm:seatlease:E1pm:dispatchedDispatched to a dev agent by /pm-dispatchpriority:p2Medium: important, M3

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions