docs(maestro-flow): inline-agent vs resource source identity — never transpose the UUIDs - #2556
Draft
jiyangzh wants to merge 1 commit into
Draft
docs(maestro-flow): inline-agent vs resource source identity — never transpose the UUIDs#2556jiyangzh wants to merge 1 commit into
jiyangzh wants to merge 1 commit into
Conversation
Live nightly run on 2026-08-10 transposed the inline-agent node's
inputs.source (agent projectId) with an attached context-index node's
inputs.source (resource UUID). flow validate scored the flow Valid --
the agent validators skip silently when <source>/agent.json is absent
-- and the swap only surfaced at debug as [170002] / Orchestrator Job
failure, backend Serverless.PythonAgent.PrepareEnvironmentError
("Project folder '<uuid>' not found in project <solutionId>"). Swapping
the two UUIDs back, with no other change, reproduced a full live debug
pass with SOP-grounded output -- proving the transposition as the sole
cause.
Add the identity rule at the resource-node inputs.source teaching point
in the inline-agent impl.md, a Debug table row for the failure
signature, and a matching pattern entry + index row + "not caught"
bullet in diagnose/references/failure-modes.md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A nightly resolution build (2026-08-10) faulted
[170002] Failure in the Orchestrator Job/Serverless.PythonAgent.PrepareEnvironmentErrornine minutes into debug, after a clean validate. Root cause: the agent transposed two adjacent opaque UUIDs — the inline-agent node'sinputs.sourcepointed at its context-index resource UUID, and the index node pointed at the agent project id. Everything else in the build was byte-correct. One-change-proven: swapping the two values back produced a full live-debug pass (SOP-grounded output).flow validatescores the swap as Valid — the agent checks silently skip when<source>contains noagent.json. (The durable fix is a validator rule that errors instead of skipping; queued for the post-#3420 validator batch. This PR is the bridge + the triage map.)Changes (+25 lines, two on-demand reference files — no SKILL.md, no tasks)
author/…/inline-agent/impl.md— 3-line rule at the point of authoring: agentsource= the project id (the dir containingagent.json); resourcesource= the resource UUID (nested underresources/<uuid>/); never transpose — validate won't catch it. Plus a Debug-table row keyed on the exact runtime signature.diagnose/…/failure-modes.md— full symptom → cause → fix pattern for the[170002]/PrepareEnvironmentErrorsignature, indexed, listed under "not caught by validate," cross-linked to the authoring rule.Testing
Docs-only. Anchors and relative links verified;
check-skill-status.pyand skill-description hook green; no frontmatter touched.