Flow debug cannot resolve registered in-solution coded agent process

[tmatup]

Summary

A Flow that references a task-created coded agent registered as a sibling in the same solution validates and uploads, but local Flow debug faults when starting the agent job:

[170007] Failure to start the Orchestrator job
404: The job's associated process could not be found

Environment

• UiPath CLI: 1.198.0
• coder-eval agent image: 0.9.5
• Claude Sonnet 5 through Bedrock
• Flow and coded agent created from the current uipath-maestro-flow skill

Reproduction shape

1. Initialize a solution and a Flow project.
2. Create a coded agent sibling, initialize it, and verify one local invocation succeeds.
3. Register it with uip solution projects add.
4. Read the generated local agent resource and add a uipath.core.agent.<resource key> node carrying its local projectId/projectName.
5. Validate the Flow and run Flow debug with a sentence input.

Observed evidence

• uip maestro flow validate succeeds.
• The solution resources contain the coded-agent package and process/agent resource, with matching resource key and project key.
• The Flow definition uses the same resource key and project key and has local/in-solution tags.
• Debug reaches the agent service task.
• The element variables show the expected sentence under JobArguments.sentence.
• The engine then faults with 170007 / 404; the incident has processKey: null and an empty packageVersion.

Expected

Flow debug should resolve the registered sibling agent process and return the coded agent's declared output.

This blocks validated in-solution coded-agent Flows from executing even though the solution resource graph and runtime input binding are present.