docs(uipath-maestro-flow): an unshipped version pin is also a check error (NODE_VERSION_UNREGISTERED)

[dmetzgar]

Pairs with UiPath/builder-sdk#1098 (Phase 1b of the node-type architecture).

That PR adds the diagnostic code NODE_VERSION_UNREGISTERED: check now reports an explicit { version } the SDK does not ship as an error that names the versions it does ship. Until now only compile refused such a pin. It applies to node types on the SDK's new node-type registry, so the set of types that report it grows as families are ported.

The one place the Flow skill covers this case is the decompile-warnings list in references/brownfield.md. That bullet now names the code; the fix (drop the pin) is unchanged. The bullet also no longer says "core", because per-tenant registered types can hit the same pin.

Merge after the SDK change is released; before then, check never emits the code.

🤖 Generated with Claude Code

[github-actions]

Claude finished @dmetzgar's task in 1m 11s —— View job

---

Summary

Updates one bullet in references/brownfield.md to document the new NODE_VERSION_UNREGISTERED diagnostic code that check can now emit for an unshipped version pin. Also broadens the bullet from "core" types to all registered types, matching the SDK's expanded scope.

Change-by-Change Review

1. skills/uipath-maestro-flow/references/brownfield.md (lines 119–121)

Severity: OK

Three changes in the decompile-warnings bullet:

• "core" dropped — correct, per-tenant registered types can hit the same pin.
• "does not bundle" → "does not ship", "registry" → "platform registry" — clearer wording, consistent with how the SDK refers to itself elsewhere.
• New sentence naming NODE_VERSION_UNREGISTERED as the check-time equivalent of the compile refusal, with the same fix (drop the { version }).

Content is accurate, scoped, and the fix guidance stays unchanged. The new sentence reads naturally as a continuation of the existing bullet.

What's Missing

Nothing identified.

Area Ratings

Area	Status	Notes
Frontmatter	OK	Not touched
E2E Tests	OK	Existing test coverage present; reference-only doc change, no new CLI workflows
Skill Body	OK	Not touched
References & Assets	OK	Change is accurate and well-scoped
Repo Hygiene	OK	No secrets, no cross-skill deps, single-file change

Issues for Manual Review

• The PR description says "Merge after the SDK change is released; before then, check never emits the code." Verify the SDK release has shipped (or will ship) before merging, so the documented behavior is observable.

Conclusion

Clean, well-scoped documentation change. No issues found — approve.

---

[uipathepixa-dogfood]

Epixa-Dogfood Review

Approved · no findings · 1/1 files reviewed

What this PR does

This change updates the Flow skill guidance that explains what happens when a deployed flow pins a node version the builder package does not ship. The guidance now tells the agent that the static check step can report that pin as an error before the compile step refuses it, and it names the diagnostic the check prints. The prescribed fix stays the same: remove the pin so the node takes the shipped version. The text also stops limiting the case to built-in node types.

Full review: 9deb628 0 findings