console: StorageUsageBanner probes the cloud-only GET /api/v1/usage/storage on every shell mount, so every page load logs a 404 on a non-cloud deployment

[objectstack-fleet]

Ruled: 5890841811 · letter A — cloud declares features.storageUsage derived from mounting the endpoint plugin; objectui reads it default-off, one boolean for both banners · 2026-09-29T13:04Z
Blocked-by: objectstack-ai/cloud#2481

Symptom

On a self-hosted or open-source objectstack runtime, every console page load issues GET /api/v1/usage/storage and gets 404. The browser console shows Failed to load resource: the server responded with a status of 404 on every navigation that remounts the shell.

Mechanism

• StorageUsageBanner (objectui#10439, landed as feat(app-shell): the environment admin's storage-capacity banner, from the served verdict (objectui#10439) #10910) is rendered unconditionally in packages/app-shell/src/console/ConsoleShell.tsx.
• Its hook useStorageUsageReading defaults to enabled = true and calls readStorageUsage(), which fetches ${apiBase}/usage/storage.
• The endpoint is served only by cloud's StorageUsageEndpointPlugin, as objectui#10439 itself records.
• objectstack's own runtime mounts no such route, and /api/v1/discovery advertises none. The hook's .catch swallows the failure, so the banner correctly renders nothing, but the request is made and fails on every mount.

Reproduction

1. Boot objectstack's showcase at objectui pin dd3f7e1be356 (objectstack dev).
2. Sign in and open any console page.
3. The network log shows GET /api/v1/usage/storage → 404, repeated on each shell mount.

Expected

The banner only asks when the runtime serves the reading: gate the hook on something the server advertises (discovery or runtime config), the way a capability-gated surface does. A deployment without the endpoint then issues no request. Machine-readable surfaces here should neither lie nor be guessed at.

[objectstack-fleet]

Path: run it — the console on a non-cloud runtime | 缺项 (StorageUsageBanner's probe) | P3

Triage: first grade — bug · priority:p3 · domain:ui · pm:queue

Triage: lands in packages/app-shell (useStorageUsageReading, ConsoleShell.tsx) ⇒ domain:ui.

Rationale: on every non-cloud runtime, every shell mount requests the cloud-only GET /api/v1/usage/storage and logs a 404. The banner correctly renders nothing, so the only cost is a wasted request and a console error line on every navigation ⇒ p3.

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-28T17:05Z. ⛔ Not a claim, ⛔ not a dispatch.

Direction.

• Gate the hook on something the runtime advertises: the discovery document or the runtime config, the way capability-gated surfaces already are.
• ⛔ Don't hard-code "cloud or not".
• Pin: with no advertised endpoint, no request is made; with it advertised, the banner still reads.

[objectstack-fleet]

Claim: PM loop round 2 — domain:ui execution seat 2
Session: session_011p7ikEivgXefNDaE5S5Uec
Account: os-support-ai (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-11002-storage-usage-advertised
Worktree: objectui-issue-11002
Domain: domain:ui
Seat: domain:ui#2
File surface (triage 5874810594: gate the probe on something the runtime advertises):

• packages/app-shell/src/hooks/: useStorageUsageReading.ts, useReadRateReading.ts (it reads the same /usage/storage response through readStorageUsage), storageUsageEndpoint.ts, and their pins.
• packages/app-shell/src/console/ConsoleShell.tsx and packages/app-shell/src/layout/StorageUsageBanner.tsx / ReadRateBanner.tsx only where the gate is wired, and one .changeset/11002-…md ('@object-ui/app-shell': patch).
• ⛔ No hard-coded "cloud or not"; ⛔ no invented discovery key. If the runtime advertises no signal that the endpoint's provider sets, stop and report needs_decision (a cross-repo seam), and change nothing.
  Stop on breach; explain in the report.
  Container & model: S, mode:subagent, model: opus (TIER_DEFAULT; dispatch-gates --tier --repo objectstack-ai/objectui over this surface: no path-derived mandate, at objectstack 288611e3)
  Clause-②: no
  Why no: a request a runtime does not serve is no longer made; no accept set, schema or export moves.
  Thread-read: 5874810594
  Serial constraints cleared: read 2026-09-29T05:58Z at objectui origin/main. Open PRs: objectui#11052 (app-shell console auth), fix(plugin-form,plugin-view,types): object-form resolves its seven I18nLabel members (objectui#10993, batch 1) #11050 (plugin-form, plugin-view, types), fix(plugin-view): ObjectView fetches only for views that draw the rows, and a re-read keeps them on screen (objectui#10982) #11049 (plugin-view, queued), fix(plugin-detail,app-shell): offer reactions only on comment rows of a record's discussion feed (objectui#11035) #11048 (app-shell RecordDetailView.tsx, seat 1), docs(changeset): date-note nine pending entries whose repository count moved (objectui#10979) #11046 and docs(changeset): date-note three pending entries on the pivot node's drillDown that PR #10972 made false (objectui#10974) #11045 (changesets), fix(core,app-shell,i18n): the console strings objectui#10953 left English under zh-CN (objectui#10969) #11033 (core, app-shell layout / console ai, the locale packs), feat(plugin-grid): one display page size read from the spec, and a distinct fetch batch (objectui#9853) #10278 (plugin-grid); and this seat's in-flight branches of objectui#10866 (plugin-gantt, plugin-calendar) and finding(cli): objectui check never prints the key it refuses, and a nested typo or a root carrying a structural key never reaches its validation step, so a strict map refusal exits 0 as "All checks passed" #11007 (cli). None touches ConsoleShell.tsx, the storage-usage or read-rate hooks, or their banners.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report

{
  "issue": 11002,
  "status": "needs_decision",
  "branch": "claude/issue-11002-storage-usage-advertised",
  "pr": null,
  "session": "session_011p7ikEivgXefNDaE5S5Uec (subagent of the PM session; identity = the branch in claim 5884584772)",
  "premise_still_valid": true,
  "summary": "Stopped before any edit, as the order's Zone 2 item 3 requires: measured on objectstack origin/main e666636f, a plugin that mounts GET /api/v1/usage/storage appears in neither the discovery payload nor the runtime config by the runtime's own mechanism, so there is no advertised key to gate on and nothing was changed (zero commits; the pushed branch equals BASE bf7ab35ce and is only the claim marker, and this container cannot delete remote refs). Discovery: both producers (HttpDispatcher.getDiscoveryInfo in runtime, ObjectStackProtocolImplementation.getDiscovery in metadata-protocol, re-served by rest registerDiscoveryEndpoints) build `services` from fixed core-slot tables (a hard-coded resolve list; SERVICE_CONFIG), `routes` and `capabilities` are closed vocabularies held by the three discovery-schema-conformance gates, and the open `metadata` record is emitted by no producer. Runtime config: RuntimeConfigPlugin (cloud-connection) derives only `marketplace` and `installLocal` from the route ledger; any other key reaches `features` only through a distribution's resolveFeatures hook, and objectui's initRuntimeConfig maps named keys only (an unknown key is dropped). The card's premise holds (an admin session on a non-cloud runtime probes and gets 404); the order's mechanism assumption 1 holds for admin sessions only (both banners pass enabled: isAdmin), and assumption 2 is falsified: ConsoleShell never calls useDiscovery (only a stale comment in ConnectedShellInner names it; the AI gate is useAiSurfaceEnabled off the agent catalog, whose header forbids gating on discovery), and the banners mount in ConsoleShellProviders, above ConnectedShell's SchemaRendererProvider, where useDiscovery has no dataSource and resolves discovery: null.",
  "tests": "No code changed, so no gate ran on a diff. Measurements: (1) existing pins at objectui BASE bf7ab35ce, from the worktree root under os-verify-lock (slot issue-11002): `pnpm exec vitest run` over packages/app-shell/src/hooks/__tests__/useStorageUsageReading.test.tsx, useReadRateReading.test.tsx, packages/app-shell/src/layout/__tests__/StorageUsageBanner.test.tsx, ReadRateBanner.test.tsx gave 'Test Files 4 passed (4)', 'Tests 46 passed (46)', 'VERDICT command-exit 0'. They include 'fetches {apiBase}/usage/storage and exposes the storage half' (a default-enabled hook requests with nothing advertised, i.e. assumption 1) and 'is for the environment admin — an ordinary session renders nothing and issues no request' (the admin-only scope). (2) objectstack origin/main e666636f, read with git show, never the working tree: subject grep `usage/storage|StorageUsageEndpoint|storage-usage|storageUsage` over the whole tree excluding CHANGELOGs exit 1, 0 hits; control grep of the same shape for `marketplace/install-local|MarketplaceInstallLocal` exit 0, 243 hits. NOT MEASURED: type-check, eslint, check-changeset-presence, check-control-bytes, reason: no diff exists. No ablation: nothing to ablate.",
  "files_changed": [],
  "gates": "none run on a diff (no diff); the existing-pin run above is a measurement of BASE, not a gate on a change",
  "deviations": [],
  "mcp_calls": "0 — no MCP GitHub tool called",
  "api_writes": "1 — POST /repos/objectstack-ai/objectui/issues/11002/comments (this os-dev-report, via objectstack scripts/pm/post-stamped.mjs through the fleet relay). Not REST writes: git push of the empty branch. Reads only: GET /repos/objectstack-ai/objectui/issues/11002, .../issues/11002/comments, .../issues/10439. No pr_create and no label-write, because there is no PR.",
  "open_questions": [
    {
      "question": "Which runtime surface advertises that GET /api/v1/usage/storage is served, and which repo sets it? This card cannot close without one: no key exists today that the endpoint's provider (cloud StorageUsageEndpointPlugin, registered by objectos-runtime per objectui#10439) sets, and the order forbids inventing a key, hard-coding cloud-or-not, or probing once and remembering the 404.",
      "options": [
        "A — a runtime-config flag set by cloud through the existing open-core seam. Cloud's objectos-runtime (the package that registers StorageUsageEndpointPlugin and already subclasses RuntimeConfigPlugin) serves one boolean, e.g. features.storageUsage, DERIVED from mounting that plugin rather than stated as a constant; objectui declares it as an optional default-off key in RuntimeFeatures (the customDomain / sso / scim pattern, read as === true) and gates both hooks on one derived boolean, so the two banners still cost one request when it is on and none when it is off. Repos: cloud (set) + objectui (this card, read). Cost: two small PRs, no spec change, no framework change; initRuntimeConfig is awaited before first render, so there is no loading window. Axes — business need: the endpoint's only producer is cloud (measured: zero objectstack hits), so the fact belongs to the repo that serves it; long-term: this is the seam RuntimeConfigPlugin's header documents for distribution-owned features (the framework must not enumerate the distribution catalog, and the cap is plan policy, Free 1 GB / Team 20 GB); AI-error: default-off means an unknown or older runtime issues no request, but declared = enforced rests on cloud deriving the flag from its mount (a literal true re-opens the lie); startup focus: the smallest change, no new gate, no spec key.",
        "B — the open framework derives the flag. objectstack's RuntimeConfigPlugin derives features.storageUsage from the raw app's route ledger (the someRoutePattern mechanism behind marketplace and installLocal): true iff /api/v1/usage/storage is mounted. Repos: objectstack (derive) + objectui (read); cloud does nothing. Axes — business need: same as A; long-term: names a cloud-only path and a plan-driven commercial surface inside the open framework, against that plugin's own open-core boundary text; AI-error: strongest declared = enforced (the mount is the answer), but an adapter with no observable route ledger answers false and darkens the banner on a host that serves it; startup focus: a framework key with zero open producers, the declared-with-no-pull shape the framework retires elsewhere.",
        "C — a discovery key. The spec declares a new slot or route key (a CoreServiceName slot or an ApiRoutesSchema key); both discovery producers and the rest handler must answer it (closed vocabulary, three conformance gates); cloud registers into it; objectui reads it. Repos: objectstack spec + runtime + metadata-protocol + rest, cloud, objectui. Axes — business need: same; long-term: a public protocol key for one cloud-only reading; AI-error: the strongest contract (conformance-gated), but the banners mount above ConnectedShell's SchemaRendererProvider where useDiscovery has no dataSource, so objectui must also move the mount or fetch discovery a second way, and discovery resolves after first render (a loading window the request must wait through); startup focus: the largest change for a p3 card.",
        "D — close the card as accepted cost: one 404 per admin page load on a non-cloud runtime, and the banner already renders nothing. Repos: none. Axes — business need: the cost is one console error line, admin sessions only; long-term: the console keeps guessing at a surface the runtime never advertised, which is the card's own objection; AI-error: nothing added or removed; startup focus: zero work."
      ],
      "recommendation": "A. The fact 'this runtime serves the storage reading' is owned by the only repo that serves it, through the seam the framework already built for distribution-owned flags, with no spec or framework surface added, and a default-off read makes every non-cloud runtime issue zero requests with no loading window. Condition the ruling on cloud deriving the flag from its own mount of StorageUsageEndpointPlugin, never a constant. Landing order: cloud first (objectui's initRuntimeConfig drops unknown feature keys, so a cloud-first flag is inert), then this card with a Blocked-by line naming the cloud card; objectui first would silence the live cloud banners until cloud ships. Dedupe words for the cloud card: `usage/storage runtime config flag`, `StorageUsageEndpointPlugin advertise`, `resolveFeatures storage usage`, `storage banner 404 non-cloud`."
    },
    {
      "question": "If A or B is chosen: the wire name, and one flag or two? This is a cross-repo key with no shared type (the two sides are pinned only by prose, like PlatformStage).",
      "options": [
        "A — one flag (e.g. storageUsage) gating both banners: both read one response through readStorageUsage, so one fact (the route is served) and one request.",
        "B — two flags (storage quota, read rate), one per banner: lets cloud withdraw one reading without the other, at the cost of two keys for one route."
      ],
      "recommendation": "A — one route, one response, one fact. The spelling is the maintainer's; storageUsage mirrors the endpoint path."
    }
  ],
  "out_of_scope_findings": [
    "carrier: the PR that implements this card's ruled option (it edits ConsoleShell.tsx) · stale comment in ConsoleShell.tsx ConnectedShellInner: 'useDiscovery() (used to gate the global AI chatbot)' — nothing in app-shell src calls useDiscovery; the AI gate is useAiSurfaceEnabled off the agent catalog · noted, not filed",
    "carrier: 承接者:无 · AiUsageIndicator via useAiUsage requests cloud GET /api/v1/ai/usage with the same no-advertisement shape; NOT MEASURED whether it ever mounts on a non-cloud runtime (the ChatDock shows only with at least one agent) · noted, not filed"
  ]
}

---

Generated by Claude Code

[objectstack-fleet]

[Decision] 存储用量横幅该凭哪个运行时信号决定"要不要问" · domain:ui seat 2 · session_011p7ikEivgXefNDaE5S5Uec · 2026-09-29T06:15Z

⛔ Not a ruling. The seat escalates: the options differ in which repository owns a public contract key, across cloud, objectstack and objectui, and no existing text decides it.

Release: session_011p7ikEivgXefNDaE5S5Uec · cause: the premise the dispatch rested on is falsified (no advertised signal exists), so the card needs a ruling before any build · destination: needs-user-decision. The claim 5884584772 is spent; the dev changed nothing (report 5884730567; the pushed branch claude/issue-11002-storage-usage-advertised equals main and carries no commit).

一句话问题

自建或开源版的运行时上，管理员每打开一个 console 页面，浏览器都会去请求一个只有云版才提供的存储用量接口，收到 404 并在控制台留一行报错。要让它"不该问就不问"，必须有一方在运行时里声明"我提供这个读数"，而今天三个仓库里谁都没声明。

背景与已测前提(每条带复测命令)

• 这个接口只有云版的 StorageUsageEndpointPlugin 提供(objectui#10439 记录)。objectstack 源码零命中。复测:git -C /home/user/objectstack grep -c "usage/storage" origin/main -- . ':!**/CHANGELOG.md' | wc -l → 本席在 objectstack 7a1faf1a 读得 0。
• discovery 的 services 由固定的核心槽位表生成,routes 与 capabilities 是封闭词表并有三道一致性门禁,插件挂一个路由不会自动出现在 discovery 里(dev 在 objectstack e666636f 读 HttpDispatcher.getDiscoveryInfo 与 ObjectStackProtocolImplementation.getDiscovery)。
• runtime config 的 features 只由框架自己推导 marketplace / installLocal,其余键只能经发行版的 resolveFeatures 钩子进入;objectui 的 initRuntimeConfig 只映射具名键,未知键丢弃。
• 两个横幅都只对管理员发请求(StorageUsageBanner 以 enabled: isAdmin 调用读数钩子),普通会话零请求。复测:git -C /home/user/objectui grep -n "enabled: isAdmin" origin/main -- packages/app-shell/src/layout/StorageUsageBanner.tsx。
• 派发令的假设"ConsoleShell 已用 useDiscovery() 门控 AI 入口"被证伪:只剩一句过期注释,AI 门控走的是 agent 目录;且横幅挂在 SchemaRendererProvider 之上,那里 useDiscovery 拿不到 dataSource。

Governing text

objectstack packages/cloud-connection/src/runtime-config-plugin.ts,"Feature seam (open-core boundary — cloud ADR-0012)":

This open package owns the mechanism: serve a per-request features map to the SPA. It does NOT own the catalog or policy — which feature keys exist and which billing plan unlocks them is a distribution concern and must never be enumerated here (that would bleed commercial/pricing policy into the open framework).

objectui packages/app-shell/src/runtime-config.ts 的先例:customDomain / sso / scim 是"absent on self-hosted / vanilla runtimes (treated as off)"的可选商业开关,由云版服务端推导。协议声明:不改 spec(选项 C 除外)。

选项 × 真实代价

选项	做什么	客户可感知的后果
A 云版声明开关	云版 objectos-runtime 依据自己是否挂载了该插件推导 features.storageUsage;objectui 声明它为可选、默认关闭,两个横幅共用这一个布尔	自建版管理员零请求零报错;云版横幅照常;两仓各一个小 PR,云先落
B 开源框架推导	objectstack 的 RuntimeConfigPlugin 从路由表推导 features.storageUsage	效果同 A;但开源框架里出现一个只有云版才会为真的键,违背上面那段 open-core 边界原文
C discovery 新键	spec 新增槽位或路由键,两个 discovery 生产者与 rest 处理器都要答,云版注册,objectui 读	契约最强;但要动 spec、三个包与三道门禁,且横幅挂载位置读不到 discovery,objectui 还得挪挂载点并承受首屏后的加载窗口
D 接受现状关卡	不改	自建版管理员每页一行 404 报错,横幅本身已不显示任何东西

业务含义直译

• A:像 SaaS 的套餐功能开关,谁卖这个功能谁负责打开它;开源版默认没有,就不去敲门。
• B:让开源内核去认识商业版的某个功能名,等于把价目表写进开源代码。
• C:为一个云版专属读数修改公开协议,相当于为一个客户改行业标准。
• D:接受"在不提供这项服务的地方每次都去问一下"。

四轴论证(业务立场)

• 项目长远合理性:A 把"这个运行时提供存储读数"这一事实放在唯一提供它的仓库,走框架已为发行版功能建好的通道,不新增 spec 或框架键;B 违背 open-core 边界原文;C 为单一云版读数扩大公开协议;D 留着"猜测一个从未声明的接口"。
• 实际业务拉动:今天撞上的是自建版的管理员,每页一行 404(实测);云版管理员依赖这个横幅看配额(Free 1 GB / Team 20 GB,dev 转述)。零拉动的是 B 与 C 引入的开源侧键。
• 防 AI 犯错:出错时谁看到什么——A 默认关闭,旧版或未知运行时零请求;但若云版把开关写成常量 true 而不是从挂载推导,就又成了"声明而未兑现",云版未挂插件时管理员会看到横幅静默失效。所以裁决要附条件:开关必须由挂载推导。C 契约最硬但改动面最大;D 让 AI 读到的 console 继续对着 404 猜。
• 创业阶段不扩散:A 是最小改动(两个小 PR,无新门禁无 spec 键);C 最大;D 零工作但保留缺陷。

os-decision-facets

• ① 项目长远合理性:A 不增加开源侧契约,事实归属提供方;B、C 扩大开源或协议面。
• ② 实际业务拉动:自建版管理员每页一行 404(实测);云版横幅在用。
• ③ 防 AI 犯错:A 默认关闭 + 由挂载推导(附条件)最难写错;常量 true 即退化。
• ④ 创业阶段不扩散:A 最小;C 最大;D 零成本但留缺陷。

Prior rulings read: usage/storage, StorageUsageEndpoint, resolveFeatures, storage banner over the 1000 most recent objectui and objectstack issues and PRs → objectui 4 / 2 / 0 / 5 hits (objectui#10439 closed, its 7 comments carry no advertisement ruling; the rest are seat posts, this card and the landing PRs), objectstack 1 / 0 / 0 / 0 (PR objectstack-ai/objectstack#20436, no ruling); ADR: cloud ADR-0012 (quoted above via the plugin header); thread: none.

推荐:A,附条件:云版的 features.storageUsage 必须由它自己挂载 StorageUsageEndpointPlugin 推导,⛔ 不写常量。一个开关同时管两个横幅(同一个接口、同一次请求)。键名由维护者定,storageUsage 与接口路径同名。
只看①选 A;②③④ 是否翻转:否。
回退:D(若维护者判定一行 404 不值两个 PR)。
置信缺口:objectstack-ai/cloud 在本容器不可读,云版 objectos-runtime 是否便于从挂载推导该开关,本席看不见;dev 的"cloud 已子类化 RuntimeConfigPlugin"来自 objectui 注释,未在云仓实测。

裁后执行

• 选 A:本席在云仓相应车道立一张子卡(云版推导并发出开关),本卡转 pm:blocked + Blocked-by: 该子卡;云版落地后本卡回队,派发令改为"读 features.storageUsage,默认关闭,两个横幅共用"。顺手修掉 ConsoleShell.tsx 里那句过期的 useDiscovery() 注释。
• 选 B / C:本席在 objectstack 立对应的 spec 或框架卡,本卡同样转 pm:blocked。
• 选 D:本卡以 not_planned 关闭,关单评论引裁决。

相关

objectui#10439(横幅落地卡,已关)· PR objectui#10910 · dev 报告 5884730567(含 A–D 的完整代价分析)。

---

Generated by Claude Code

[objectstack-fleet]

Ruling: batch #243 item 1 · letter A · maintainer 「11002 A」 2026-09-29T13:01Z

Director seat (objectstack#12708, summon #30 续 2, session_01AsCNgFBs8HCjwhyHQsFbx3). Provenance: maintainer, live PM chat with the director seat, 2026-09-29, replying 「11002 A 20619 A 10866 A 20637 C 11088 同意」 to batches #243–#245 as presented. Presented on this card: the domain:ui seat 2 escalation 5884767712, read whole, with the director's own reading in chat (which closed the seat's confidence gap from the cloud repository: objectos-runtime subclasses the open RuntimeConfigPlugin with its own resolveFeatures, and the same objectos-stack.ts composition registers both that plugin and StorageUsageEndpointPlugin).

Ruled: A. The cloud distribution declares the switch: objectos-runtime serves features.storageUsage, derived from mounting StorageUsageEndpointPlugin, never a literal; objectui declares RuntimeFeatures.storageUsage as optional, default off, read as === true, and gates both banners' hooks (useStorageUsageReading, useReadRateReading — one endpoint, one request) on that one boolean. ⛔ No key in the open framework (B): the open-core boundary text in runtime-config-plugin.ts forbids the framework enumerating a distribution's catalog. ⛔ No discovery slot (C): a public-protocol change for one cloud-only reading, and the banners mount where discovery cannot be read.

Readings that decided it:

• Long-term: the fact "this runtime serves the storage reading" lives in the only repository that serves it, through the seam the framework built for distribution-owned features; no spec key, no framework key.
• Real use: every self-hosted administrator's console page load issues a 404 today (measured); cloud administrators read their quota from this banner.
• AI-safety: default off means an older or unknown runtime issues no request; the condition on the derivation keeps the flag from becoming a second "declared, not delivered" key.
• Startup scope: two small PRs, no new gate, no spec key.

Execution parameters:

• Cloud first: objectstack-ai/cloud#2481 (filed in the same stroke, pm:queue, p3) — the flag served from the composition that mounts the endpoint plugin, with a pin that it changes with the mount (a composition fact or a route-ledger read; the seat's choice); it is not plan policy, so it is not derived from plan.
• Then this card: the dispatch is rewritten to "read features.storageUsage, default off, one boolean for both banners; delete the stale useDiscovery() comment in ConsoleShell.tsx". initRuntimeConfig is awaited before first render, so no loading window.
• Key name storageUsage, the same as the endpoint path; the maintainer may rename it on either card.
• Confidence gap recorded: none left on the cloud side (read at cloud origin/main 3efda04); the objectui side is as measured by the dev.

State: needs-user-decision → pm:blocked, Blocked-by: objectstack-ai/cloud#2481; the Ruled line goes on the body in the same stroke. When cloud#2481 lands, this card returns to pm:queue.