finding(plugin-grid): object-grid 的 operations 与 rowActions 取并集 —— operations: { update: false } 关不掉 rowActions: ['edit'] 打开的行内编辑

由 domain:spec @ objectui 执行席立卡（session session_01UanLVj6xvbS6puBCewLr8L）。出处：objectui#8071 slice 12（PR objectui#9817）。⭐ 该 slice 已把这个行为钉成 pin，本卡问的是「它该不该是这样」——⛔ pin 是记录不是背书。

事实（实测于 `origin/main`，`packages/plugin-grid/src/rowCrudAffordances.ts:182`）

!!((opts.operationsUpdate || opts.wantEditAction) && opts.hasOnEdit) && objectCanEdit;

operations 与 rowActions 两个独立声明的键在这里用 || 合并 ⇒ 并集,⛔ 不是交集。

⇒ 作者写下

{ "type": "object-grid", "operations": { "update": false }, "rowActions": ["edit"] }

期望的是「关掉行内编辑」，拿到的是编辑照样在。⛔ operations: { update: false } 关不掉 rowActions: ['edit'] 打开的东西。

判据

类 (c) —— AI 写元数据会撞的陷阱：

两侧声明面都接受这个组合，⛔ 无报错、⛔ 无警告、⛔ 无降级；
operations 这个名字本身读起来就是「这张表允许哪些操作」，⭐ 一个名叫 operations 的块关不掉一个操作，是反直觉的方向；
作者唯一能观察到的，是自己以为关掉的按钮还在 —— 而那通常要到有人误点之后才被发现。

⛔ 本卡不裁修法

A 改成交集(&&)：operations 成为上限，rowActions 只能在其内选择。⚠️ 改已发布运行时语义，可能让现有页面少渲染按钮。
B 保持并集，但把口径写进 operations 与 rowActions 两侧的 description：「二者取并集；operations 不是上限」。零行为改动。
C 保持并集，但对矛盾组合加一条具名 console.warn。

⚠️ A 是行为改动且方向是「收紧」⇒ 走决策箱，⛔ 不由执行席自裁。B / C 不动语义。

⚠️ 已被钉住

PR objectui#9817 的 object-grid.operations 成员 pin 钉的正是并集这一格，消融腿是「explicit ?? defaults → {...defaults, ...explicit}」。⇒ 无论选哪条,若改了行为,那条 pin 会变红并强制重读。⭐ 这是故意的，⛔ 不是要修绿的东西。

查重词：operations rowActions union · resolveRowCrudAffordances · operations update false ignored · row affordance gate · object-grid operations not a ceiling

Refs: objectui#8071 · objectui#9817

Generated by Claude Code

Ruling: batch #162 item 1 · letter A (object-grid's operations is the CEILING: the edit gate and the delete gate in rowCrudAffordances.ts:182 / :184 become intersections — rowActions can only select an action operations allows; operations: { update: false } turns row editing off whatever rowActions says) · maintainer 「同意」 2026-09-18T12:18Z

Director seat, summon #24, session_01Wj1HUjzyeiBQ8atRf1ZhaL. Presented in detail with the recommendation A; the maintainer agreed. Facts (this card; triage 5726509657): both gates read (opts.operationsX || opts.wantXAction) && opts.hasOnX — a union of two independently declared keys; both declaration surfaces accept { operations: { update: false }, rowActions: ['edit'] } and the edit affordance stays; the delete gate at :184 is the same shape; PR objectui#9817 pinned the union on purpose.

Ruling — A

resolveRowCrudAffordances: canEdit = operationsUpdate && (wantEditAction || <default when rowActions absent>) && hasOnEdit && objectCanEdit; the delete gate the same way. operations absent ⇒ today's defaults; operations.<op>: false ⇒ that affordance is off, full stop. rowActions chooses among what operations allows and can only narrow.
The object-grid.operations member pin in PR test(plugin-grid,console): pin the member shapes object-grid reads for its four per-row keys (objectui#8071 slice 12) #9817's suite flips to the intersection, one case per direction (ceiling refuses, rowActions narrows, absent operations keeps defaults). The operations / rowActions describes state 「operations is the ceiling」.
Changeset @object-ui/plugin-grid minor with the behaviour note: a page that wrote operations.<op>: false together with a rowActions entry for it now hides that button.
⛔ B writes the surprise into the docs; ⛔ C warns in dev only.

Four-facet reading: ① a block named operations is the ceiling; ② an author turning an operation off must succeed; ③ operations: { update: false } is the AI's natural spelling and becomes correct; ④ no member added — same principle as #9837 (an explicit off always wins), one rule for the block.

Execution

needs-user-decision → pm:queue; domain:spec, priority:p2 stay (lands in objectui's plugin-grid). Same round / same PR as objectui#9837 by the seat's choice. Clause-②: no.

Generated by Claude Code

Claim: PM loop round R+304
Session: session_01QVJUngS9FKfuyQ9NFR2Nbn
Branch: claude/issue-9819-operations-ceiling
Worktree: objectui-issue-9819
Domain: domain:spec
Seat: domain:spec#1
File surface: packages/plugin-grid/src/rowCrudAffordances.ts (the :182 edit gate AND the :184 delete gate) + its pins under packages/plugin-grid/src/__tests__/ (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: TIER_DEFAULT``
Clause-②: no
Thread-read: 5729875720
Serial constraints cleared: PR objectui#9924, which held the whole packages/plugin-grid/src/__tests__/ dir, MERGED 2026-09-20T09:32:35Z — re-read on GitHub in this act, ⛔ not inherited from the seat post, which still showed it parked

Seat continuity. This seat changed hands this round: the predecessor (hotlong, session_01UanLVj6xvbS6puBCewLr8L) ran out of tokens and the maintainer handed the seat over with 「前任没有token了,你接手」. Batch ceiling is 5 per 「并发加到5」.

Why this tier. a ruled behaviour narrowing on a published runtime; no declaration surface is widened, so the predicate reads no

⚠️ dispatch-gates.mjs --tier REFUSES for objectui (it derives families from the objectstack tree it runs in and says so outright), so this tier is hand-derived and that is declared rather than dressed up as a tool reading — ⛔ NOT MEASURED by --tier.

Scope exclusion. ⛔ NOT packages/plugin-grid/src/ObjectGrid.tsx — that is objectui#9837's surface (ruled A′), which is LINKED to this card and therefore ⛔ never in the same batch

Generated by Claude Code

os-dev-report

{
  "issue": 9819,
  "status": "done",
  "branch": "claude/issue-9819-operations-ceiling",
  "pr": "https://github.com/objectstack-ai/objectui/pull/10081",
  "session": "session_01QVJUngS9FKfuyQ9NFR2Nbn",
  "premise_still_valid": true,
  "head": "3e7993e6",
  "summary": "Ruling A landed: object-grid's `operations` is now the CEILING over `rowActions`. Both gates in resolveRowCrudAffordances went from `(operationsX || wantXAction) && hasOnX && objectCanX` to `operationsX && hasOnX && objectCanX` — the delete gate too, not only the edit one the card title names (re-derived by symbol on today's origin/main, confirmed textually isomorphic). A truthy operations member is now required, so an explicit `false` AND a member a present block does not name both withhold the affordance. Direction is a NARROWING of published runtime behaviour and no tolerant `??` fallback was added. Card carried assignee os-steve on arrival; I did not touch the assignee field. The newest claim (5749283900) names this branch.",
  "clause_2_measured": "no — confirmed by measurement, not inherited. The intersection only refuses more than the union did; no combination refused today becomes accepted, and no declaration surface was widened (no member added, no schema change).",
  "files_changed": [
    "packages/plugin-grid/src/rowCrudAffordances.ts (both gates + module docblock section '`operations` is the ceiling')",
    "packages/plugin-grid/src/__tests__/gridOperationsMembers-8071.test.tsx (the PR objectui#9817 slice-12 member pin, re-pointed; that describe block went 2 cases -> 5)",
    "packages/plugin-grid/src/__tests__/rowCrudAffordances.test.ts (unit pin, 1 case -> 2)",
    ".changeset/issue-9819-operations-ceiling.md (@object-ui/plugin-grid minor, behaviour note, as the ruling directs)"
  ],
  "pin_that_flipped": "gridOperationsMembers-8071.test.tsx fact 3 and its case 'a UNION with rowActions: update: false does not survive rowActions: [edit]' (asserted { trigger: true, edit: true, delete: false }), plus rowCrudAffordances.test.ts 'honors explicit rowActions (edit/delete strings) when callbacks exist'. Both were pinning the union on purpose. Re-pointed at the intersection, NOT deleted and NOT weakened: the union's own inputs are kept with the opposite expectation as the case that goes red if the `||` returns, and the control now does MORE work than before (added: the unnamed-member case that a `update !== false` ceiling would pass; a control proving rowActions with no operations block still gets the wired-callback default; and the not-implemented narrowing case).",
  "gates": [
    {
      "gate": "affected package suite",
      "cmd": "pnpm exec vitest run packages/plugin-grid/",
      "exit": 0,
      "reading": "Test Files 145 passed (145) / Tests 1380 passed (1380); RUN v4.1.10 at repo root"
    },
    {
      "gate": "cross-package blast radius (16 derived consumer files)",
      "cmd": "pnpm exec vitest run THE-16-DERIVED-PATHS (components, i18n, plugin-designer, plugin-detail, plugin-list, plugin-view, types, apps/console)",
      "exit": 0,
      "reading": "Test Files 16 passed (16) / Tests 392 passed (392) — 16 requested, 16 ran, no zero-match"
    },
    {
      "gate": "real type-check (NOT scripts-type-check.test.ts)",
      "cmd": "pnpm --filter @object-ui/plugin-grid type-check",
      "exit": 0,
      "reading": "echoed `tsc --noEmit && tsc -p tsconfig.test.json` — both passes ran, so tests are covered too"
    },
    {
      "gate": "dependency closure build (prerequisite for the type-check)",
      "cmd": "pnpm --workspace-concurrency=2 --filter '@object-ui/plugin-grid^...' build (via os-verify-lock.sh)",
      "exit": 0,
      "reading": "VERDICT command-exit 0"
    },
    {
      "gate": "control bytes",
      "cmd": "node scripts/check-control-bytes.mjs",
      "exit": 0,
      "reading": "OK (8117 tracked text files)"
    },
    {
      "gate": "line citations (differential)",
      "cmd": "node scripts/check-new-cross-file-line-citations.mjs",
      "exit": 0,
      "reading": "VERDICT 0 new citation(s), enforcement report-only"
    },
    {
      "gate": "changeset presence",
      "cmd": "node scripts/check-changeset-presence.mjs",
      "exit": 0,
      "reading": "3 source files of 1 released package changed, 1 changeset declared"
    },
    {
      "gate": "changeset no-major",
      "cmd": "node scripts/check-changeset-no-major.mjs",
      "exit": 0,
      "reading": "No changeset declares a major bump"
    },
    {
      "gate": "changeset fixed group",
      "cmd": "node scripts/check-changeset-fixed.mjs",
      "exit": 0,
      "reading": "all workspace packages in the fixed group"
    },
    {
      "gate": "changeset overwrite",
      "cmd": "node scripts/check-changeset-overwrite.mjs",
      "exit": 0,
      "reading": "1 added, 0 modified, 0 deleted"
    },
    {
      "gate": "pending changeset literals",
      "cmd": "node scripts/check-pending-changeset-literals.mjs",
      "exit": 0,
      "reading": "no test source names a pending changeset"
    },
    {
      "gate": "test path roots",
      "cmd": "node scripts/check-test-path-roots.mjs",
      "exit": 0,
      "reading": "OK"
    },
    {
      "gate": "vi.mock override shape",
      "cmd": "node scripts/check-vi-mock-override-shape.mjs",
      "exit": 0,
      "reading": "OK"
    },
    {
      "gate": "vi.mock specifiers",
      "cmd": "node scripts/check-vi-mock-specifiers.mjs",
      "exit": 0,
      "reading": "OK"
    },
    {
      "gate": "eslint (declared narrowing, see eslint_narrowing)",
      "cmd": "pnpm exec eslint --no-inline-config --format json THE-3-CHANGED-FILES",
      "exit": 0,
      "reading": "3 files linted, 0 errors, 2 warnings — both warnings pre-existing on the base blob"
    },
    {
      "gate": "governed surface",
      "cmd": "node scripts/check-governed-queue-guard.mjs --test THE-4-PATHS",
      "exit": 0,
      "reading": "NOT GOVERNED — 4 paths against 5 governed surfaces, none matched"
    }
  ],
  "gate_list_provenance": "HAND-DERIVED, declared as such. dispatch-gates.mjs lives in ../objectstack and refuses for objectui, so the list comes from objectui's own package.json scripts plus the workflows enumerated with `git ls-tree -r --name-only origin/main .github/workflows/` (39, equal to the working-tree count, with `git cat-file -e origin/main:.github/workflows/ci.yml` as the positive control). Enumeration and reads come from the SAME ref.",
  "gate_first_red_reported": "The type-check first read exit=2 with TS2307 'Cannot find module @object-ui/types' — a fresh worktree with no dependency dist/*.d.ts, i.e. a stale-dist lie, not a finding. The 0 above is the re-run after building the closure. Reported rather than silently replaced by the green.",
  "eslint_narrowing": {
    "declared": "Repository-wide `eslint . --no-inline-config` is CI's run and was NOT run here. The narrowing is measured, with all three required readings present.",
    "population_from_eslint_own_config": "eslint.config.js declares its blocks over **/*.{ts,tsx} with a top-level ignores; every block reachable by these files is a path-glob block. Read from the config, not guessed.",
    "file_count_from_format_json": "3 files linted, 0 errors, 2 warnings (both @typescript-eslint/no-explicit-any, both pre-existing: the same two appear at shifted lines when the BASE blob of the same file is linted).",
    "invariance_over_untouched_files": "eslint.config.js declares NO type-aware linting — no parserOptions.project, no projectService, no tsconfigRootDir, no recommended-type-checked preset. Every rule judges one file from that file's own text, so no edit in this diff can move any untouched file's verdict.",
    "head_referenced": "3e7993e6"
  },
  "tests": "Targeted pins: `pnpm exec vitest run packages/plugin-grid/src/__tests__/rowCrudAffordances.test.ts packages/plugin-grid/src/__tests__/gridOperationsMembers-8071.test.tsx` -> exit 0, 'Test Files 2 passed (2) / Tests 55 passed (55)'. Package suite exit 0, 145 files / 1380 tests. Cross-package 16 files / 392 tests, exit 0. ABLATION (direction predicted BEFORE running: the re-pointed pins go red — and that is what happened): fix committed first; intersection replaced on disk by the original union with the anchor asserted to hit exactly once and the substitution verified on disk in both directions (injected union present=1, intersection absent=0), never trusted from an editor exit code. MUTATION LEG exit 1, 'Tests 4 failed | 51 passed (55)' — the four are exactly the ceiling assertions and span both pins and both vitest projects (|unit| two in rowCrudAffordances.test.ts; |dom| 'the CEILING refuses: update: false SURVIVES rowActions: [edit]' and 'the ceiling refuses a member the block does not NAME'); controls and the not-implemented case stayed green in both worlds. RESTORE LEG used `git checkout HEAD -- PATH` (never the bare form, which takes the mutation back out of a polluted index) and is proven BY BYTES not by an exit code: git hash-object on disk == HEAD blob c37fbbe437a10b567b0217d6957e010d0c7545fa, `git diff HEAD` empty; re-run exit 0, 55 passed. Nothing from the ablation remains; tree clean at 3e7993e6. All exit codes captured to disk BEFORE any pipe.",
  "line_budget": "NOT APPLICABLE — the diff touches no skills/** path, so the published-skill line budget is not owed. Actual diff for the record: 4 files, +148 / -18 against base 0c2eb5ee.",
  "deviations": [
    "DECLARED, and the important one: the ruling's narrowing half is NOT implemented. Its formula is `canEdit = operationsUpdate AND (wantEditAction OR DEFAULT-WHEN-ROWACTIONS-ABSENT) AND hasOnEdit AND objectCanEdit`, with the prose 'rowActions chooses among what operations allows and can only narrow'. The CEILING half is implemented in full. The narrowing half cannot be implemented within this card's file surface: the gate cannot distinguish 'rowActions absent' from 'rowActions present without this name' — ObjectGrid.tsx passes rowActionsList.includes('edit') and an absent rowActions becomes an empty array, so both arrive as the same `false`. Narrowing on that false would close the generic Edit/Delete on EVERY grid declaring no rowActions, the exact outcome the same ruling forbids one sentence earlier ('operations absent => today's defaults'). So the only value of the DEFAULT-WHEN-ROWACTIONS-ABSENT hole that preserves the ruling's own invariant at this call site is `true`, which collapses that conjunct away — that is what landed. Telling the two apart needs a caller-side signal only packages/plugin-grid/src/ObjectGrid.tsx can produce, and that file is objectui#9837's surface, fenced out of this batch. I did NOT widen. The gap is PINNED rather than left silent: a case named 'NOT IMPLEMENTED — rowActions does not NARROW inside the ceiling' records today's answer, so implementing the narrowing turns it red.",
    "DECLARED: the ruling also asks the `operations` / `rowActions` describe texts to state that operations is the ceiling. Those live in packages/types/src/zod/objectql.zod.ts (operations carries 'Enabled operations'; rowActions carries no describe at all) — another package, outside the declared file surface. Nothing published becomes false without it, since neither description asserted the union. The rule itself is stated in the rowCrudAffordances.ts module docblock. Not widened; filed below.",
    "DECLARED: the PR body quotes the ruling's operative clause VERBATIM as the dispatch requires, and that quote carries the ruling's own `rowCrudAffordances.ts:182` / `:184` addresses. check-changeset-claims.mjs's born-false reading may report them (it is report-only, exit 0 either way). I added a sentence immediately after the quote naming the tree they were read from (42234b1) and re-citing the two gates by content. Altering a verbatim maintainer quote would be worse than the report.",
    "DECLARED: commit trailers are model-free (`Co-Authored-By: Claude noreply-at-anthropic.com` + `Claude-Session:`), per the dispatch's trailer clause, which the harness attribution reminder yields to by its own precedence sentence. The harness-suggested trailer named a model; reported, not imitated, and no history was rewritten.",
    "DECLARED: 2 git pushes on the branch (the empty routing probe required by the dispatch, then the implementation commit). Zero label writes — objectui path labels come from labeler.yml per push, no gate reads a label I would set, and the dispatch named none.",
    "SELF-REPORTED ERROR: my first closure-build invocation passed `--concurrency=2` AFTER `--filter`, so pnpm forwarded it to the package's own tsup, which rejected it (exit 1, 225s of lock wait burned). Re-run correctly as `pnpm --workspace-concurrency=2 --filter ... build` -> exit 0. Recorded because the wasted lock time was charged to a shared box."
  ],
  "mcp_calls": "0 — no MCP GitHub tool was called at all, neither read nor write. All GitHub access went through the REST proxy with curl.",
  "api_writes": "2 REST writes: POST /repos/objectstack-ai/objectui/pulls (the draft PR, 1 call, HTTP 201) and POST /repos/objectstack-ai/objectui/issues/9819/comments (this report). 0 PATCH calls — the PR body was written once, at creation. 0 label writes. Plus 2 git pushes on the feature branch. Read-back after each write: the stored PR body STARTS WITH the sent body byte-for-byte (nothing eaten); the only delta is the platform appending its own 90-byte session-URL attribution footer, the documented add-family mutation.",
  "open_questions": [],
  "out_of_scope_findings": [
    "to file (class b, violates a declared contract — the ruling itself; dedupe words: `rowActions narrowing inside ceiling` · `resolveRowCrudAffordances rowActions declared signal` · `object-grid rowActions can only narrow` · `rowActions absent vs unnamed` · `operations ceiling second half`): the ruled narrowing half of batch #162 item 1 letter A is unimplemented and cannot land without a caller-side 'rowActions was declared' signal from packages/plugin-grid/src/ObjectGrid.tsx. Surface is that file plus resolveRowCrudAffordances' signature. Blocked-by / overlaps objectui#9837's surface, so it should be sequenced after it. This is the card that keeps the ruling's remainder from losing its carrier — the same continuity concern triage raised on this card.",
    "to file (class c, a trap that makes AI write metadata the runtime silently drops; dedupe words: `object-grid operations rowActions describe` · `Enabled operations describe ceiling` · `rowActions no describe objectql.zod` · `operations ceiling declaration surface` · `grid operations description silent`): neither `object-grid.operations` nor `object-grid.rowActions` says anything in its declaration about how the two combine. `operations` reads 'Enabled operations' and `rowActions` carries no describe at all, so the ceiling rule that now governs them is invisible at the only surface an author or a model reads before writing the document. Surface: packages/types/src/zod/objectql.zod.ts. The ruling explicitly asks for it; it is a different package and was outside this card's declared file surface.",
    "noted, not filed: ObjectGrid.tsx's `hasRowActions` still counts wantEditAction/wantDeleteAction when deciding whether to render the actions COLUMN, so `operations: { update: false }` plus `rowActions: ['edit']` now renders an empty `_actions` cell rather than no column. The kebab itself correctly does not appear (the menu plan's own empty guard). Carrier: objectui#9837's seat is the next one in that file. Not repaired here — out of surface, and the empty-cell shape is pre-existing behaviour that file documents deliberately.",
    "noted, not filed: rowCrudEffectiveOps.test.tsx and rowOperationsPerRow-8674.test.tsx cover the layers ANDed on top of this gate and were unaffected by the change. Recorded so a later reader need not re-derive the blast radius. Carrier: none."
  ]
}

Generated by Claude Code

ACCEPT — PR objectui#10081, reviewed against GitHub

domain:spec @ objectui execution seat, session_01QVJUngS9FKfuyQ9NFR2Nbn, R+304, 2026-09-20T11:2xZ.

Spot-checks taken by this seat on the diff itself

item	reading
form	`draft: true` · base `main` · first line `Fixes #9819` · head `3e7993e6af` · 4 files, +148 / -18
⭐ BOTH gates, ⛔ not only the one the title names	removed: `!!((opts.operationsUpdate \|\| opts.wantEditAction) && opts.hasOnEdit)` and `!!((opts.operationsDelete \|\| opts.wantDeleteAction) && opts.hasOnDelete)`; added: `!!(opts.operationsUpdate && opts.hasOnEdit)` and `!!(opts.operationsDelete && opts.hasOnDelete)` ⇒ the union is gone on both limbs
the pinned gap is real	`+ it('⚠️ NOT IMPLEMENTED — \`rowActions` does not NARROW inside the ceiling'` present in the diff
clause ② (`no`)	an intersection only refuses MORE; no member added, no schema change, no declaration surface widened
governed / size	`packages/plugin-grid/` is outside the governed definition; 166 changed lines ⇒ ordinary queue route
`mcp_calls`	0; 2 REST writes; 0 label writes (`labeler.yml` applied `plugin,tests` on push, which is its production, ⛔ not the dev's)

⭐ The judgement that makes this a good PR: half the ruling was NOT implemented, and that was right

Ruling A's prose also asks that 「rowActions chooses among what operations allows and can only narrow」. That half did not land, and the reason is an obstacle rather than a shortcut: the gate cannot distinguish 「rowActions absent」 from 「rowActions present without this name」, because ObjectGrid.tsx passes rowActionsList.includes('edit') and an absent rowActions arrives as an empty array ⇒ both are the same false. Narrowing on it would close the generic Edit/Delete on every grid declaring no rowActions — which the same ruling forbids one sentence earlier (「operations absent ⇒ today's defaults」).

⭐ So the dev took the only value preserving the ruling's own invariant, ⛔ did not widen into ObjectGrid.tsx (objectui#9837's fenced surface), and ⛔ did not leave the hole silent — it is pinned so that implementing the narrowing turns the pin red. That is the correct shape for a fork found mid-implementation.

⇒ The remainder is now carried, so Fixes does not orphan it: filed as objectui#10083 (the unimplemented narrowing half, sequenced AFTER #9837 since it needs ObjectGrid.tsx) and objectui#10084 (the operations / rowActions describe texts the ruling also asks for, sequenced after #9511 which currently holds that file).

⭐ The pin flip is a re-point, ⛔ not a weakening

PR objectui#9817 pinned the UNION on purpose. It was re-pointed at the intersection, ⛔ not deleted and ⛔ not relaxed: the union's own inputs are kept with the opposite expectation, so the case goes red if the || ever returns, and the block grew 2 cases → 5 — it now does strictly MORE work (the unnamed-member case, a control proving rowActions with no operations block still gets the wired-callback default, and the not-implemented case).

⭐ The ablation predicted its direction BEFORE running

Fix committed first; the intersection then replaced on disk by the original union, with the substitution verified on disk in both directions (injected union present=1, intersection absent=0) rather than trusted from an editor's exit code. Mutation leg: exit 1, 4 failed / 51 passed, and the four are exactly the ceiling assertions, spanning both pins and both vitest projects; controls and the not-implemented case stayed green in both worlds. Restore proven by bytes — git hash-object == HEAD blob c37fbbe437a1, git diff HEAD empty — and via git checkout HEAD -- PATH, ⛔ never the bare form.

⚠️ One interpretation named explicitly, because the ruling's example did not cover it

The landed gate makes a present operations block that does not NAME a member withhold that affordance, not only an explicit false. The ruling's worked example is operations: { update: false }; the word 「ceiling」 supports the broader reading and the dev pinned it, but it is a behaviour decision the example did not state. ⇒ recorded here and raised to the maintainer as a reversible item under the objection window — it is one PR to reverse, and the PR is still draft.

Deviations — accepted, all declared by the dev

The describe-text half and the narrowing half both fell outside the declared surface; ⛔ not widened, both filed. Correct.
A first type-check read exit 2 (TS2307, missing @object-ui/types) on a fresh worktree with no dependency dist — a stale-dist lie, ⛔ not a finding; the 0 is the re-run after building the closure. ⭐ Reported rather than quietly replaced by the green.
eslint narrowed to the 3 changed files, declared with all three readings (population from eslint's own config, count from --format json, invariance because no type-aware program is configured). 2 warnings, both pre-existing on the base blob.
⭐ Self-reported error: a first closure build put --concurrency=2 after --filter, so pnpm forwarded it to the package's own tsup, which rejected it — 225s of shared verify-lock time burned. Recorded because the cost landed on a shared box. ⛔ No action owed; the honesty is the right behaviour.
Commit trailers are model-free, which is correct here — this session's own instruction forbids a model identifier in any commit message, PR title or body, and that outranks the harness's suggested trailer. ⛔ No history was rewritten.

⚠️ CI — honest `in_progress`, ⛔ NOT a pass

Head 3e7993e6af: 36 runs — 27 success, 3 skipped, 0 not-green, 6 running (Type Check, Doc Snippet Type Check, Test shards 1–4/4). ⇒ ACCEPT is the review verdict; the landing is HELD — ⛔ not flipped ready, ⛔ not enqueued, done at the next patrol once those six converge.

Generated by Claude Code

✅ LANDED — verified by CONTENT on `origin/main`, ⛔ not from the `merged` field

domain:spec @ objectui execution seat, session_01QVJUngS9FKfuyQ9NFR2Nbn, R+304, 2026-09-20T14:3xZ. Merged in one merge-queue batch at 14:12:36Z; origin/main read at 6980904793.

Squash commit: c269ed9e fix(plugin-grid): make object-grid operations the ceiling over rowActions (objectui#9819) (#10081)

⭐ The decisive reading — the union is GONE from BOTH gates

probe on `origin/main`	reading
OLD union `operationsUpdate
OLD union `operationsDelete
NEW intersection `operationsUpdate &&`	1
NEW intersection `operationsDelete &&`	1
[LIT CTRL] `objectCanEdit` in the same file	2 ⇒ the ruler reads this file, so the two zeros are real absences

⇒ ruling batch #162 item 1 letter A is live: operations is the ceiling, on the delete gate as well as the edit gate. An author writing operations: { update: false } beside rowActions: ['edit'] now gets row editing OFF.

⚠️ Reminder carried forward: the ruling's narrowing half is still unimplemented and is filed as objectui#10083 (needs a caller-side signal from ObjectGrid.tsx, so it is sequenced after objectui#9837). The describe texts the ruling also asks for are objectui#10084.

Half-state cleared in the same act

Keyword closing (Fixes) closes the card but leaves pm:dispatched and the assignee behind — a documented trap on this board. Both were cleared and read back: labels now domain:spec + priority:* only, assignees none. ⛔ domain:* and the priority label stay — ownership is not state.

Generated by Claude Code

fix(plugin-grid): make `object-grid` `operations` the ceiling over `r…

Navigation Menu

Repository navigation

finding(plugin-grid): `object-grid` 的 `operations` 与 `rowActions` 取并集 —— `operations: { update: false }` 关不掉 `rowActions: ['edit']` 打开的行内编辑 #9819

事实（实测于 `origin/main`，`packages/plugin-grid/src/rowCrudAffordances.ts:182`）

判据

⛔ 本卡不裁修法

⚠️ 已被钉住

Ruling — A

Execution

ACCEPT — PR objectui#10081, reviewed against GitHub

Spot-checks taken by this seat on the diff itself

⭐ The judgement that makes this a good PR: half the ruling was NOT implemented, and that was right

⭐ The pin flip is a re-point, ⛔ not a weakening

⭐ The ablation predicted its direction BEFORE running

⚠️ One interpretation named explicitly, because the ruling's example did not cover it

Deviations — accepted, all declared by the dev

⚠️ CI — honest `in_progress`, ⛔ NOT a pass

✅ LANDED — verified by CONTENT on `origin/main`, ⛔ not from the `merged` field

⭐ The decisive reading — the union is GONE from BOTH gates

Half-state cleared in the same act

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

finding(plugin-grid): object-grid 的 operations 与 rowActions 取并集 —— operations: { update: false } 关不掉 rowActions: ['edit'] 打开的行内编辑 #9819

Description

事实（实测于 origin/main，packages/plugin-grid/src/rowCrudAffordances.ts:182）

判据

⛔ 本卡不裁修法

⚠️ 已被钉住

Activity

hotlong commented on Sep 18, 2026

Ruling — A

Execution

os-steve commented on Sep 20, 2026

os-steve commented on Sep 20, 2026

os-steve commented on Sep 20, 2026

ACCEPT — PR objectui#10081, reviewed against GitHub

Spot-checks taken by this seat on the diff itself

⭐ The judgement that makes this a good PR: half the ruling was NOT implemented, and that was right

⭐ The pin flip is a re-point, ⛔ not a weakening

⭐ The ablation predicted its direction BEFORE running

⚠️ One interpretation named explicitly, because the ruling's example did not cover it

Deviations — accepted, all declared by the dev

⚠️ CI — honest in_progress, ⛔ NOT a pass

os-steve commented on Sep 20, 2026

✅ LANDED — verified by CONTENT on origin/main, ⛔ not from the merged field

⭐ The decisive reading — the union is GONE from BOTH gates

Half-state cleared in the same act

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

finding(plugin-grid): `object-grid` 的 `operations` 与 `rowActions` 取并集 —— `operations: { update: false }` 关不掉 `rowActions: ['edit']` 打开的行内编辑 #9819

事实（实测于 `origin/main`，`packages/plugin-grid/src/rowCrudAffordances.ts:182`）

⚠️ CI — honest `in_progress`, ⛔ NOT a pass

✅ LANDED — verified by CONTENT on `origin/main`, ⛔ not from the `merged` field