Skip to content

metadata-protocol: nits from the epic red-line read of PR #32815 (semantic entry remedy order, unpinned owner rule, seal direction) #32903

Open

Description

@objectstack-fleet

domain:server#1 · os-sales · session_01L6bhgVaKJ9TPfXPRhdqx3e

Nits from the epic red-line read 6838271054 and the contract reviews of PR #32815 (#32408). None blocks that PR; filed under the maintainer's rule (nits go to one follow-up card, no extra round).

Blocked-by: #32408

维护者速读

Items

  1. The semantic entry's first remedy (ship a locale the App ships too) holds at the package door, and at the item door only when the shared locale registers first. Say so in the entry, or close it with the item-door card under metadata: overlaySlotBinding's other readers (bundleMembersHeldBy, getEnvironmentScopedItem) bind a pair row without reading overrides.package (ADR-0150 D4) #32408.
  2. The rule that an addition shipping the row's own member stays an owner is not pinned at the package door (its ablation leaves the package-door UNCHANGED pin green). Add the pin.
  3. The seal names the later-registered package as the incoming one, so its report's direction follows registration order. Consider an order-free report.
  4. Contract review N2 of 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: a package reaching two Apps whose namespace picks another is no owner of the pair; measure that shape and pin it.

Activity

  1. objectstack-fleet commented on Nov 13, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:server#1 · os-sales · session_01L6bhgVaKJ9TPfXPRhdqx3e

    Item 5 (from the delta contract review 6840278165 of PR #32815 at acc680227): a pair row declaring a package outside the App also stops lending the App its locale at the gate, and row 1's wording on PR #32815 covers only the declared-X case. Word row 1 (or the semantic entry) to cover it, or pin it. Also: item 4 (N2 shape) now goes through the same gate read and is refused as on main, so it only needs a pin.

  2. objectstack-fleet commented on Nov 13, 2026

    @objectstack-fleet
    ContributorAuthor

    domain:server#1 · os-sales · session_01L6bhgVaKJ9TPfXPRhdqx3e

    Items 6 to 11, from the epic red-line delta read 6841098779 of PR #32815 (its "Nits" list, numbered here after the earlier five):
    6. Row 1 is pinned at the item door only; the package door and the seal's report were measured by probe, not pinned.
    7. A pair row declaring a package outside the App moves as row 1 does at both doors, outside row 1's wording "another package of the App" (same as item 5); by reading only, a row of a legacy per-package pair declaring a package other than its base does too.
    8. The spec changeset still says "the one registration", and the entry file's header comment "a narrowing of one registration"; the entry now names two.
    9. The PR title and the changeset headline say every reader binds a pair row by the exact read's owner rule; under option B the gate reads it its own way.
    10. Row 13's FROM says X's address no longer served the row; that is the registry's item at X, while the protocol's exact read at X still served it on BASE, attributed to the arriving package.
    11. The six REVERSE ORDER pins at the doors are controls; their titles read as pins of the fix.

  3. objectstack-fleet commented on Nov 13, 2026

    @objectstack-fleet
    ContributorAuthor

    triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

    Path: none

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

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


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    domain:serverDomain lane — seat card indexed by label:pm:seatpm:queueReady for the PM dispatch looppriority:p3

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions