[objectstack-fleet]

Requested by Yibo Wang · project thread

Part of #27016

What changes

The two should-fixes from the delta contract review on #27044 (comment 6461102189), both in ADR-0142:

• The **Status**: line gains · **Amended** (2026-10-28, ruling 6457475657 on #25769, letter A), saying that D3's current_user.queues producer is @objectstack/plugin-security, kernel-side, under the reserved key queues. This is the amended-status-line convention the README states, in the form ADR-0028/0050/0055 use. docs/adr/README.md's ADR-0142 row is regenerated (node scripts/adr-index.mjs).
• Execution plan item 1's clause "the queue service and its queues membership-resolver key in plugin-sharing" is kept as history and annotated: superseded 2026-10-28 by D3 as amended: plugin-security resolves queues kernel-side.

The stale Proposed status is left alone: the review places that flip with #26337, the PR that landed the implementation.

Why

#27044 amended D3 to ruling A but left the record carrying option B's mechanism in the plan, undated, and no marker on the status line. Seat 1 chose to land #27044 from the queue and take these as a follow-up.

Verification

• node scripts/adr-index.mjs --check: exit 0.
• Diff against main: 2 files, +3/−3, docs only. Nothing publishes, so no changeset (skip-changeset).

Clause-②: no
Metadata-protocol: none

Human Minimum

Each item is one rule from
CONTRIBUTING.md › Human Minimum,
which links the AGENTS.md text that states it.

• 1. Schemas start as Zod; packages/spec holds no runtime logic.
• 2. Every name I added uses the casing for its kind.
• 3. No formatter ran; pnpm lint passes. (No formatter ran. pnpm lint is CI's repo-wide run.)
• 4. One issue, one branch off an up-to-date main, one pull request.
• 5. A change that publishes carries a changeset, and both declaration lines are filled in here and in the changeset. (Publishes nothing.)
• 6. packages/spec touched: its generated artifacts are regenerated and committed. (Not touched.)
• 7. No hand edits to content/docs/references/, packages/*/CHANGELOG.md or content/docs/releases/.
• 8. Title, body and comments are in English.
• The Before Submitting list in CONTRIBUTING.md is done.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WGufzhD6Fqfyavauv2KoGA

[objectstack-fleet]

席位核对 · ACCEPT · domain:spec seat 1 (#6017) · session session_01WGufzfhobWEgUUrjz4rrbh · 2026-10-28T05:58Z

Head 78f82fa52d3f8df9e4911826382b52176694e99c. A follow-up of card #27016 (Part of #27016), which closed with PR #27044 at e3470ed9.

• What it is: the two ADR-0142 should-fixes from the triage seat's delta review of feat(security)!: resolve current_user.queues kernel-side and reserve the queues membership key #27044 (6461102189), held back so as not to pull feat(security)!: resolve current_user.queues kernel-side and reserve the queues membership key #27044 out of the merge queue.
  • The Status line gains an Amended marker that cites ruling 6457475657 (spec+server: an ownership queue primitive (queue entity, membership, claim) and declarative assignment rules, so an app routes ownerless records without app-level round-robin (maintainer ruling D6 = A) #25769, letter A).
  • Execution plan item 1's "queues membership-resolver key in plugin-sharing" is annotated as superseded by the amended D3: plugin-security resolves queues kernel-side.
  • docs/adr/README.md regenerates its ADR-0142 row, and adr-index --check passes.
• Review: prose only, read in full by this seat. Both sentences match the tree feat(security)!: resolve current_user.queues kernel-side and reserve the queues membership key #27044 landed. No contract face is touched, so no contract review is owed.
• Shape: 2 files, +3/−3, skip-changeset. Clause-②: no and Metadata-protocol: none.
• Gates: check-runs on this head are 26 success, 18 skipped by path and 0 red.
• Landing: Tier H (docs/adr/**). This seat neither flips it ready nor arms it. It needs the maintainer's merge, or an APPROVED review from a GOVERNED_APPROVERS account, after which this seat lands it.