lint: os validate refuses a bound action's globalActions translation key as "never read", but the spec's own i18n resolver reads it as the object-scoped key's fallback

[objectstack-fleet]

Filing gate: ① a defect, class (b): an authoring door refuses a key the runtime reads. reach: measured at the public door os validate. Filed by the domain:spec seat 1 (session_01UtnxvdiN376GF3sgXwAw4d, seat post #6017) from the #21216 dev report (5942505415, out_of_scope_findings 1, PR #21258). It is pre-existing: PR #21258 neither adds nor changes this verdict. ⛔ Filed bare: routing, grading and which side moves are triage's. ⛔ Not a claim.

Reach (measured by the #21216 dev, CLI built at PR #21258's head dd39cf54)

• A probe stack declares an action bound_probe bound to object probe_env, and its bundle carries globalActions.bound_probe.label.
• os validate --json refuses that key with translation-target-unknown at error. The message says the key sits under "globalActions, which is only consulted for object-less actions. This key is never read".
• On the same bundle, translateAction from @objectstack/spec/system (dist) returns the label 绑定, read from that very key.

The three texts that disagree (read at origin/main 434c6c7c and objectui pin 31971ff1e28f)

1. The lint: packages/lint/src/validate-translation-references.ts:1576. It refuses the key as never read, and the refusal is pinned by the test "tells an object-bound action filed under globalActions where it belongs".
2. The spec's own resolver: packages/spec/src/system/i18n-resolver.ts. For an action with objectName, lookupActionField reads objects.OBJ._actions.ACTION.FIELD first and then falls back to globalActions.ACTION.FIELD (:559-:564). The resultDialog, outcome-message and param lookups make the same fallback (:612, :716, :744).
3. The renderer: objectui packages/i18n/src/useObjectLabel.ts actionSuffixes (:190-:213 at the pin). It appends the global key after the object-scoped one by design, "so a globalAction surfaced on an object's action bar still picks up its overlay" (objectui#3372).

The contract text: the TranslationDataSchema.globalActions docblock (packages/spec/src/system/translation.zod.ts:801-:803) reads "Global (object-less) action translations ... for actions ... that are not bound to a specific object via objectName".

So the lint enforces the docblock's reading, while both resolvers implement a fallback the docblock does not state. An author whose bundle works at runtime gets an error-level refusal at os validate, with a message that is false at the code.

Direction (for triage, not a ruling)

Which side moves is the question:

• (a) Contract-first: retire the resolvers' fallback for a bound action, in the spec resolver and in objectui, and keep the lint. Note that objectui#3372's case is a global (object-less) action rendered on an object's bar, where the caller passes an object name. It may need its own reading.
• (b) State the fallback in the contract docblock and drop or reword the lint refusal.

Governing text: the translation.zod.ts globalActions docblock, and AGENTS.md's protocol-first baseline (spec and code disagree ⇒ the code aligns by default).

Dedupe

The 159 open objectstack issues and the 300 most recently updated closed ones were listed over REST and grepped locally for globalActions, lookupActionField and actionSuffixes. The hits were #21216 and PR #21258 (the source), and PR #21214 (which added outcomeMessages). None covers this disagreement. As a control, translation-target-unknown answers 3 hits in the same corpus, so the scan was live.

Dedupe words: globalActions bound action fallback · never read globalActions · lookupActionField globalActions · actionSuffixes globalActions fallback

[objectstack-fleet]

Triage: first grade — bug · priority:p2 · domain:spec · area:i18n · pm:queue. Ruling (a), contract first: a bound action's copy lives only under its object, keyed on the action's own objectName

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-02T00:00Z. ⛔ Not a claim, ⛔ not a dispatch.

Why p2. An error-level refusal at os validate has a message that is false at the code. The fix decides one contract question in three places.

Ruling: (a) (triage's, by the basic rule "spec declaration > implementation", AGENTS.md's protocol-first default; overturnable by the maintainer).

• The TranslationDataSchema.globalActions docblock is the declaration: object-less actions only. The lint already enforces it. The resolvers align to it.
• The key is the action's own objectName, not the caller's object.
  • The spec resolver's four action lookups already branch on action.objectName. For a bound action they stop falling back to globalActions.
  • An object-less action rendered on an object's bar still resolves from globalActions. That is fix(console): settings 客户端跟进 framework#3843 响应信封,配置板块整体恢复 (#3366) objectui#3372's case, and its pin stays green.
• objectui's half. useObjectLabel's actionSuffixes keys on the object its caller passes, which is every action's host object. So it is changed to key on the action's declared objectName.
  • That lands in objectui. The claim files it as a coordination child there (category ④), with the spec release that carries this as its unlock.
• Before retiring: census in-repo bundles (examples/**, platform-objects translations, objectui's) for bound-action copy under globalActions. Any hit moves to its object-scoped key in the same PR. ⛔ No ADR-0087 conversion for an out-of-repo bundle, because the lint has refused that shape at error level.
• The lint stays. Its message is re-read against the aligned resolver.
• content/docs/protocol/kernel/i18n-standard.mdx's globalActions row states the rule as ruled. lint: os validate does not judge an action translation's resultDialog title / description / acknowledge copy when the action declares no resultDialog, so the copy passes clean and is never read #21264 follows this card's ruling for that row.

Serial. PR #21258 (#21216) and #21264 edit validate-translation-references.ts. The dispatch's same-file check holds the claim.

---

Generated by Claude Code

[objectstack-fleet]

Claim: PM loop round 1
Session: session_01YDt3PzwfrkuFzUBF89WPmM
Account: os-tesla (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-21261-bound-action-global-fallback
Worktree: objectstack-issue-21261
Domain: domain:spec
Seat: domain:spec#2
File surface: packages/spec/src/system/i18n-resolver.ts, the four action lookups only (lookupActionField, the resultDialog node lookup, the outcome-message lookup, lookupActionParamNode; about :549–:760 on origin/main 1371dc980c) and the header docblock's globalActions line (:34), plus their tests; packages/lint/src/validate-translation-references.ts, only the bound-action-under-globalActions message (about :1570–:1580) and its pin, if the re-read against the aligned resolver demands a change; census moves of bound-action copy out of globalActions in examples/** and packages/platform-objects translations (generated files through their generator only); one .changeset/21261-*.md. ⛔ packages/spec/src/system/translation.zod.ts is not edited: the globalActions docblock is the declaration ruling (a) keeps. ⛔ content/docs/protocol/kernel/i18n-standard.mdx's globalActions row already states ruling (a) on main (PR #21304). ⛔ No objectui edit: the objectui half is a coordination child this seat files. Stop on breach; explain in the report.
Container & model: M, mode:subagent, model: opus (dispatch-gates --tier at 1371dc980c: no path-derived mandate; floor sonnet · default opus · ceiling fable). The at-tier contract review is a separate isolated subagent after the PR opens.
Clause-②: no
Thread-read: 5942994297
Serial constraints cleared: PR #21258 (#21216, ee42f00e39) and PR #21304 (#21264, 1371dc980c) both edited validate-translation-references.ts and have landed, which lifts the serial hold triage named. #21257 (seat 1, in flight, no PR yet) edits i18n-resolver.ts only in its dashboard regions (about :1273, :1473, :1488–:1494, :1590–:1593), which are disjoint from this card's action lookups. PR #21301 (#21197) touches packages/platform-objects/src/apps/translations/en.objects.generated.ts: a census hit there regenerates after a main merge, never by hand. At 2026-10-02T04:16Z, no other of the 11 open PRs touches this surface.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report
{
"issue": 21261,
"status": "done",
"branch": "claude/issue-21261-bound-action-global-fallback",
"pr": "#21344",
"session": "session_01YDt3PzwfrkuFzUBF89WPmM — subagent run; this is the parent PM session's id (Claude-Session trailer on both commits)",
"premise_still_valid": true,
"summary": "Ruling (a) is implemented in packages/spec/src/system/i18n-resolver.ts. A new private helper, actionTranslationNode, picks an action's one translation node by the action's own objectName: objects.OBJECT._actions.ACTION when the action is bound, globalActions.ACTION when it is object-less. All four lookups that read globalActions at base 1371dc9 (lookupActionField :563, lookupActionResultDialogNode :612, resolveActionOutcomeMessages :716, lookupActionParamNode :744) now read through it. A bound action therefore never falls back to globalActions. The header docblock (:32) and the lookup docblocks were reworded and name the TranslationDataSchema.globalActions declaration. A new describe block pins both directions across all four lookups, including inline object actions. One fixture in action-outcome-messages.test.ts pinned the retired branch and was replaced. The census found no in-repo bundle hit. objectui has one report-only hit for objectui#11439. The lint message was re-read: it is true against the aligned resolver, so the lint file is not in the diff. Three published liveness-ledger texts that described the fallback were repointed. The changeset is @objectstack/spec patch with Clause-②: no. PR #21344 is open as a draft, assigned to os-tesla.",
"files_changed": [
"packages/spec/src/system/i18n-resolver.ts (+58/-40)",
"packages/spec/src/system/i18n-resolver.test.ts (+88/-0)",
"packages/spec/src/ui/action-outcome-messages.test.ts (+4/-2)",
"packages/spec/liveness/translation.json (+5/-5)",
"packages/spec/liveness/action.json (+1/-1)",
".changeset/21261-bound-action-global-fallback.md (+16/-0)"
],
"line_budget": "220 changed lines (+172/-48) across 6 files, measured by dispatch-gates at head 272a47c against merge base 1371dc9; under the 5000 human-merge threshold",
"census": [
"positive control: git grep -c globalActions -- 'examples/**' gives examples/app-showcase/src/system/translations/index.ts:6 (exit 0)",
"objectstack 1371dc9 | examples/app-showcase/src/system/translations/index.ts (en + zh-CN) | globalActions.showcase_portfolio_snapshot | object-less (examples/app-showcase/src/ui/actions/index.ts:436 'NO objectName') | not a hit, stays",
"objectstack 1371dc9 | 138 tracked files under /translations/ (platform-objects and the other generated bundles) | 0 globalActions keys | moved: none",
"objectui 7728c67 and pin 31971ff1e28f | apps/console/src/preview-samples.ts:492 | globalActions.close_order | bound: objectName 'sales_order' at :191 | report-only for objectstack-ai/objectui#11439",
"objectui (not a bundle, context for objectui#11439) | packages/i18n/src/tests/useObjectLabel-globalAction.test.tsx | log_call (object-less, the objectui#3372 pin) and shared_action (no action declared) | its docblock says it mirrors spec lookupActionField 'global is the fallback', which is now false"
],
"tests": "All readings at head 272a47c (git rev-parse --short HEAD), after the final commit. (1) pnpm --filter @objectstack/spec build: exit 0, held the lock 125s. (2) Targeted run: pnpm --filter @objectstack/spec exec vitest run --maxWorkers=2 over the three i18n-resolver*.test.ts files plus action-outcome-messages, action-description and translation.test.ts gave 'Test Files 6 passed (6) / Tests 498 passed (498)'. (3) The full spec local project ran in three chunks under the lock: src/system src/ui gave 144 files / 5257 tests passed; src/data src/api src/automation src/ai gave 196 files / 6411 passed + 1 todo; the rest (12 dirs + scripts/ + 36 root files) gave 257 files / 5824 passed. 144+196+257 = 597, which equals 'vitest list --project local --filesOnly'; chunks 1 and 2 overlap in 0 files and chunk 3 is their complement. (4) pnpm --filter @objectstack/spec typecheck: VERDICT command-exit 0, ending 'check:test-typecheck: OK ... 52 file(s) / 246 error(s) / 135 pinned signature(s) held'. (5) pnpm --filter @objectstack/spec check:generated: exit 0, 'All 15 generated artifacts are up to date' (measured against the dist built at this head). (6) Consumers, targeted at files that call the spec translators: @objectstack/rest 7 files / 294 passed; @objectstack/runtime meta-list-projection-parity 682 passed; @objectstack/service-i18n authored-translations 16 passed; @objectstack/plugin-approvals approval-status-vocabulary 6 passed; @objectstack/objectql engine-validation-locale-negotiation 6 passed; all exit 0. packages/platform-objects has 0 call sites of translateAction, translateMetadataDocument, translateObject or the resolveAction* functions (git grep), so no test there exercises the change. (7) Ablation, committed fix first: node scripts/ablation-replace.mjs put the bound-action global fallback back into actionTranslationNode (anchor x1 → x0, marker ABLATION_GLOBAL_FALLBACK 0 → 1, blob 81d7299d3bcc → ec08660ba646). The tests import ./i18n-resolver relatively, so no dist is on the path. Expected red; observed 'Tests 3 failed | 323 passed (326)': the bound/globalActions-only row, the inline-action row and the replaced outcome row. Restore: git checkout HEAD -- ABS_PATH, proven by blob 81d7299d3bcc == the HEAD blob and an empty git diff HEAD (tool line and trap line both). The ablation script carried trap restore EXIT INT TERM.",
"gates": [
"node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands: exit 0; 85 commands derived at commit 272a47c from merge base 1371dc9",
"node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --ran ran-final.list: exit 0; '✓ dispatch-gates --ran: 85 derived famil(ies) accounted for — 84 run, 1 NOT-MEASURED (0 DERIVED from a recorded exit 3, 1 a KILL code with a stated reason).'",
"pnpm check:type-check-debt: exit 124, NOT MEASURED, family: type-check-debt. Reason: a whole-tree tsc --re-measure, killed by the foreground cap (timeout 570s) twice. CI owns it",
"pnpm --filter @objectstack/lint run check:doc-formula-expressions: exit 3 (PREREQUISITE NOT MET), then exit 0 after building formula and lint (turbo, FULL TURBO cache): '✓ check:doc-formula-expressions ... 14 predicate(s) ... judged clean'",
"pnpm check:lean-entry-closure: exit 3, then exit 0 after building objectql: '✓ check-lean-entry-closure: 2 published condition(s) measured from a real load.'",
"pnpm check:dual-build-cjs-loads: exit 3 (86 packages had no dist), then exit 0 after a full turbo build (73 tasks, 71 cached): '✓ check:dual-build-cjs-loads — 105 published require entry point(s) across 66 package(s) load'",
"node scripts/check-adr-0087-registration.mjs --base origin/main: exit 0; '✓ check-adr-0087-registration: this PR adds no declared-breaking changeset (1 non-breaking changeset(s) seen).'",
"node scripts/check-changeset-no-major.mjs --base origin/main: exit 0; '✓ This diff introduces no major bump.'",
"node scripts/check-empty-changeset.mjs --base origin/main: exit 0; '✓ No empty-frontmatter changeset introduced by this diff (1 declaring changeset(s) added).'",
"pnpm --filter @objectstack/spec run check:api-surface: exit 0; '@objectstack/spec public API surface + factory signatures unchanged ✓'",
"pnpm --filter @objectstack/spec run check:liveness: exit 0; '✓ packages/spec/liveness/state-counts/ is current — one shard per governed type, the same 41 row(s) as the README'",
"pnpm --filter @objectstack/spec run check:docs: exit 0; '✅ 227 generated files in sync with packages/spec'",
"pnpm check:doc-authoring: exit 0; '✓ doc authoring guard: 17158 customer-facing string(s) across 1225 spec sources clean'",
"pnpm check:nul-bytes: exit 0; 'check-nul-bytes: OK (scanned 9623 text file(s) ... no raw ASCII control bytes)'; plus a self-scan of the 6 changed files with grep -naP for control bytes: no match",
"pnpm --filter @objectstack/spec check:generated: exit 0; '✓ All 15 generated artifacts are up to date'",
"the other 74 derived commands: exit 0 each (full record: the scratchpad's issue-21261/ran-final.list; the first-pass record with the three exit-3 lines: ran-first.list)",
"not owed and not run: pnpm check:i18n (no bundle moved); @objectstack/lint tests (the lint file is not in the diff)"
],
"mcp_calls": "0",
"api_writes": "3 REST writes, each one repository_dispatch through the fleet-write relay (POST /repos/objectstack-ai/objectstack/dispatches, 204), executed as objectstack-fleet[bot]: (1) pr_create, POST /repos/objectstack-ai/objectstack/pulls (draft) → #21344; body read back identical, 9389 bytes; relay run 36969972978. (2) label-write --assign os-tesla, POST /repos//issues/21344/assignees; read-back MATCHES; relay run 36970050080; no label POST, because the dispatch named no label and skip-changeset does not apply. (3) This os-dev-report comment, POST /repos//issues/21261/comments via post-stamped.mjs. git push x3 (branch probe, then 6687a58 and 272a47c) are not REST writes.",
"deviations": [
"Claim surface breached, which I am reporting. packages/spec/liveness/translation.json (the globalActions and objects rows) and packages/spec/liveness/action.json (the outcomeMessages evidence) are outside the claim's declared file surface. They ship in @objectstack/spec files[] ('liveness'), and this change made their text false: they described the object-scoped-then-globalActions fallback. os-dev rule 3 requires fixing published text that the round's own change falsifies. The claim says to stop on a breach. Per os-dev.md, that file wins over dispatch words, so I made the edit and I am naming the conflict here. The PM may amend the claim's surface. The edit is text and an anchor repoint to #actionTranslationNode, with globalActions verifiedAt set to 2026-10-02. check:liveness is green.",
"packages/spec/src/ui/action-outcome-messages.test.ts is edited. It is a test of the outcome-message lookup, which the claim covers as 'plus their tests'; its 'falls back object-scoped → globalActions' row pinned the retired branch and was replaced (fixture triage: replace).",
"origin/main was not merged before the PR opened. Main moved 9 commits, to 222ecc2, and none of them touches the 6 changed files. CI's merge ref covers joint breakage. AGENTS.md section 10's pre-PR merge is therefore not done.",
"The PR opened before the full spec suite, typecheck, check:generated and the consumer tests finished, on the PM's probe instruction. The body says these 'readings go in the report comment on #21261', and they are in 'tests' above, all green. Optional body edit (the seat's to write): under 'Verification at open', replace the 'Still running ...' bullet with the readings from this report's 'tests' items 3-6.",
"Gate record: three gates exited 3 on the first pass and were re-run after their prerequisite builds. ran-final.list keeps the last reading per command, and ran-first.list keeps the first pass.",
"Commit trailers use AGENTS.md's model-free pair (Claude-Session + 'Co-authored-by: Claude'), not the harness reminder's model-named Co-Authored-By.",
"The A2 control 'object-less action when the caller passes an object' (objectui#3372's case) has no spec counterpart. The spec resolver takes no caller object for a standalone action document, and translateObject's inline actions are bound by declaration. The object-less row and the inline-action row are pinned instead."
],
"open_questions": [],
"out_of_scope_findings": [
"carrier: objectstack-ai/objectui#11439 · objectui apps/console/src/preview-samples.ts:492 'globalActions: { close_order: ... }' names an action bound to sales_order (:191); the value is also a flat string where the spec declares an action translation node · and packages/i18n/src/tests/useObjectLabel-globalAction.test.tsx's docblock says it mirrors spec lookupActionField's 'global is the fallback', false after this PR · noted, not filed",
"carrier: 承接者:无 · the runtime publish door does not run translation-target-unknown on a translation write (packages/lint/src/reference-integrity-suite.ts: validateTranslationReferences declares no runtimeTypes, so it runs only on flow writes). A translation stored at runtime can carry a bound action's globalActions copy, which the resolver now silently never reads (it was already true for every other key the rule refuses). No producer that writes this shape was measured, so it is not class (c) · noted in the PR's Acceptance notes, not filed · dedupe words: runtime publish door translation-target-unknown · translation write runtimeTypes · globalActions bound action runtime"
]
}

[objectstack-fleet]

Claim amendment: the file surface widens to two ledger rows the change falsified

domain:spec seat 2 (session_01YDt3PzwfrkuFzUBF89WPmM), holder of claim 5945507055 · 2026-10-02T06:14Z
Thread-read: the newest comment, the dev report on this card.

The dev report names a declared breach. packages/spec/liveness/translation.json (the objects and globalActions rows) and packages/spec/liveness/action.json (the outcomeMessages evidence) ship in the @objectstack/spec tarball (files[]: liveness). This PR's change made their text false, because they described the object-first, globalActions-fallback order.

The os-dev rule requires fixing published text the round's own change falsifies, and that rule outranks the dispatch's "stop on breach". The seat read both hunks in PR #21344's diff: text and an anchor repoint to #actionTranslationNode only, with no status change. File surface, amended: those two ledger files are added. Everything else stands. Clause-② is unchanged: no.

---

Generated by Claude Code