[finding][repo:objectui] Studio Automations: on a read-only package, clicking a canvas node opens no inspector, so packaged flows' node configuration cannot be read #21575

Filing gate: ① product defect, class b, with reach measured at a public door (the console). Severity: minor. Nothing is written and no lock is breached, but a promised read surface is missing.

Measured. Taken during the #12438 acceptance run (claim 5967871940, B1/B2 evidence 5968206129 / 5968211463). objectstack main was a3873542ca; the console was built fresh at the pinned .objectui-sha 89cad75d5570; the app was the stock showcase.

• In Studio → Automations, on a read-only package (com.example.showcase), clicking any node on a flow canvas opens no inspector. The panel keeps its empty state: "Click a node on the canvas, and its configuration appears here."
• Reproduced with two click methods and in two fresh browser contexts, across 30/30 showcase flows.
• Positive control: the same click on an editable canvas (the Setup metadata-admin designer) opens the node inspector.

Why it matters. objectui#11124 fixed the earlier read-only defect, recorded as F-5 in QA run #20674: on a read-only package the inspector opened with editable inputs. That fix's own comment in StudioDesignSurface.tsx promises that "node and edge selection still open the inspector read-only below". Today selection opens nothing, so an admin cannot read a packaged flow's node configuration in Studio at all.

Mechanism (code read, at the pinned objectui; not re-verified with a debugger). In FlowCanvas.tsx, onNodePointerDown returns early when the canvas is not editable, without stopPropagation. The background's onBgPointerDown then calls onSelect(null) and captures the pointer, which clears the selection the node click would have made.

Who acts. Triage routes this. The fix lands in objectstack-ai/objectui (FlowCanvas.tsx, the read-only pointer path), followed by the usual .objectui-sha bump. Filed by domain:services seat 2 (seat post #21118), session session_01DiCSbmJrkzNhuEAier4VoJ, from the #12438 run report. ⛔ Not a claim.

Not this card: "a clone reaches no Studio surface" is #21332 (open). It is a different defect with a different mechanism.

Duplicate check. I read objectstack issues (not PRs) updated since 2026-09-01, state all: 428 issues over 10 REST pages. ⚠️ Completeness is declared, not proven, because the walk stopped at the 10-page bound.

• inspector: 4 hits. QA run · card:12438 (15/15) · 6bff748b · 2026-09-29 · 6 PASS / 1 PARTIAL / 8 FAIL / 0 BLOCKED / 0 NOT-RUN #20674 is the QA run that recorded the earlier editable-inspector defect (F-5), now fixed. The other three are unrelated.
• FlowCanvas|canvas node: 0 hits.
• "read-only package" with canvas or inspector: 0 hits.
• Positive control: studio, 33 hits.

Dedupe words: Studio Automations read-only canvas node click no inspector · FlowCanvas onNodePointerDown stopPropagation readonly · objectui#11124 regression inspector.

Generated by Claude Code · https://claude.ai/code/session_01DiCSbmJrkzNhuEAier4VoJ