[codex] Pilot Maestro BPMN skill scenarios

[gozhang2]

Summary

Pilots the uipath-maestro-bpmn skill against three public-safe authoring/debugging requests and folds the findings back into the synthetic validation corpus:

• service-desk connector intake with generated package metadata
• gateway and boundary-error debugging for approval-style branching
• subprocess multi-instance batch processing with script normalization and message wait

Changes

• Documents the pilot scenarios, latest fixture validation output, and open questions for Maestro owners in fixtures/validation/README.md.
• Extends the public-safe fixture checker to validate message event references and multi-instance loop metadata.
• Adds author validation bullets and diagnose failure modes for multi-instance variable drift and message reference mismatch.

Validation

• bash skills/uipath-maestro-bpmn/.maintenance/check-validation-fixtures.sh -> validation_fixture_projects=4 bpmn_files=4 errors=0
• bash skills/uipath-maestro-bpmn/.maintenance/check-all.sh -> All checks passed.
• uv run ruff check skills/uipath-maestro-bpmn/.maintenance/check-validation-fixtures.py -> All checks passed.
• run_workspace_checks(kinds='auto') -> changed-file fmt passed, pytest passed, typecheck skipped; repo-wide tests lint still has 49 pre-existing errors.
• run_workspace_checks(check_kinds=["fmt","lint","typecheck","test","test_web"]) -> full gate failed on pre-existing repo-wide tests/ formatting/lint issues; pytest passed, typecheck/test_web skipped.

Open Questions

• Should uipath:loopCharacteristics remain the stable public contract for multi-instance collection and item binding, or should fixture validation prefer registry/CLI-generated loop metadata when available?
• Which Intsvc.* context fields are mandatory across all connector families versus connector-specific fields that should stay outside this static checker?
• Should entry-points.json validation compare full input schemas against root variables, or only verify entry point IDs and file paths until the CLI generator owns schema normalization?

[gozhang2]

Closed as duplicate/stale. The same pilot changes were finalized onto the shared Maestro BPMN PR #616 as commit c5d9a08; review and the three open product-contract questions should continue on #616.