bpmn docs: is a node-scoped variable visible to debug-instance variables-all?

[nikhil-maryala]

Flagged by @rockymadden while reviewing #3379 (his "out of scope" note). Two places in the skill disagree, and nothing in the repo settles it:

• skills/uipath-maestro-bpmn/references/expression-authoring.md:100-101 — a variable scoped to an element "is not surfaced as a root runtime variable, so debug-instance variables-all cannot show it."
• fix(uipath-maestro-bpmn): bridge public process inputs and outputs #2369's commit (826927089) reports the opposite from live runs: outputs "declared with elementId bound to the end event still appear as keys in the Globals map."

Why it matters now

The #3378 follow-up wants the edit checks to require elementId presence (not merely "not dangling"), matching check_variable_scopes.py criterion 1. Whether node scoping hides a variable from runtime diagnostics changes what we should tell agents to do with process-level state, so it is worth settling before that tightening lands.

How to settle it

A live read, not a doc edit: author a BPMN with one process-scoped and one node-scoped uipath:inputOutput, run it, and compare uip maestro bpmn debug-instance variables-all output for both. Then correct whichever statement the runtime contradicts.

🤖 Generated with Claude Code