Repository navigation
🍒 [v1.207] fix(uipath-maestro-case): add test-recipient and go-live guidance [CA-232] - #4998
Merged
rockymadden merged 1 commit intoNov 19, 2026
Conversation
…-232] (#4870) * fix(uipath-maestro-case): add test-recipient and go-live guidance [CA-232] The case skill had no guidance on action recipients and the go-live trap: a literal recipient email baked into the plan requires editing and republishing to change. PACT golden thread caught it at step 27 when the agent set the user's email as a default without warning. New RULE:case.recipient.externalize and RULE:case.recipient.no-silent-default in case-runtime.md tell the agent to wire recipients through case inputs and warn the user before publishing with a test default. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): add check caveat for expression recipient The =vars. expression syntax on the recipient field is unverified by any existing example or test. Add a verification step (case check) and a fallback path in case the compiler treats it as a literal. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): drop unverified expression recipient recipe The snippet did not compile (types is not exported from /case), used the Flow path shape vars.start.output.*, and case check never reads action.recipient. No case plan in use carries an expression recipient. Keep the go-live warning; tell agents to write a plain address and say what going live requires. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): one trigger for the recipient disclosure; state the recipient type Say that a bare string compiles to type 2 (single user by email) and that types 0/1/3 are unexercised. Drop the unproven validate claim. Fire the disclosure for any recipient the user did not name as the production assignee, and keep that text in one rule only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): cover escalation targets and decompiled recipients Keep a decompiled { type, value } recipient as is. Apply the go-live disclosure to SLA escalation targets too, and give an unattended run a path: list the recipients in the final summary and do not publish. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): name the publish commands an unattended run must skip "Do not publish" named no command, so an agent could read compile as publishing. Name uip solution upload/publish/deploy run, keep check, compile and validate running, treat a request that already says to publish as the user's decision, and count an <UNRESOLVED: ...> target as not production. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): treat case debug like publish; never route to an unresolved target case debug creates real Action Center tasks for the baked-in recipients, so it joins upload/publish/deploy run. A recipient or escalation target still <UNRESOLVED: ...> never debugs or publishes; a request that says to debug or publish decides for a real or test address or group. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): gate only the commands that start instances upload and publish do not create tasks; only case debug and solution deploy run do. List non-production recipients in every final summary, not only before publish, and count a pre-approval that names the debug or deploy step as the user's answer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): restore input-wired recipient as a Type 3 expression The engine resolves a Type 3 recipient by evaluating its value (CLI sdd-convert recipient.ts; 68 of 74 corpus expression recipients; TIF-12003 demo). SDK 6.120.17 case check warns STRICT_RECIPIENT_EXPRESSION_TYPE on an expression under type 0-2 and validate --strict fails it. Teach input + { type: 3, value: '=vars.<input>' }, verified by check and compile. Gate any command that starts an instance, not a fixed verb list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): gate only debug and process run; flag the stale SDK comment No evidence shows deploy run or activate starting a manual-trigger case, so the gate names only case debug and case process run. Say in the rule that the SDK's RecipientType comment ("0/1/3 reserved") is stale, and point SKILL.md's literal-recipient example at the go-live section. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * fix(uipath-maestro-case): disclose test assignees before upload or publish CA-232 asks for the go-live notice before publishing. Tell the user before uip solution upload or publish, and repeat it in the final summary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q * docs(uipath-maestro-case): name the list the disclosure tells the user Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
github-actions
Bot
requested review from
a team,
dmetzgar and
tmatup
as code owners
November 19, 2026 15:30
2 of 5 tasks
dmetzgar
approved these changes
Nov 19, 2026
rockymadden
deleted the
fix-case-test-recipient-guidance-CP-to-release-v1-207
branch
November 19, 2026 20:27
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
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
recipient: '<email>'bakes the address into the plan. To go live, someone must edit every action and publish again.case-runtime.md§ Action recipients and the go-live trap:RULE:case.recipient.externalizegives the recipe for a test or placeholder assignee: declare a case input with a test default, then setrecipient: { type: 3, value: '=vars.<input>' }.'=vars.x'string is type 2 and is looked up as an email.RULE:case.recipient.no-silent-defaultmakes the final summary list every assignee that the user did not name as production: input defaults, literal recipients,toUser/toGroupescalation targets, and<UNRESOLVED: ...>. For each, the summary says what going live changes.case debugandcase process run. An<UNRESOLVED>assignee never runs.upload,publish,check,compileandvalidateare not gated.Evidence for type 3
packages/case-tool/src/services/sdd-convert/recipient.tsmaps an expression recipient toType 3, the engine'sUnknown(AppTasksFacade.ResolveAssignmentCriteria). The engine evaluates the value and assigns it as a user when it is an email, or as a group name otherwise. The same source comment says 68 of the 74 expression recipients in the eval corpus carry type 3 (tests/fixtures/strict/README.mdmatches), and that a type 3 recipient ran in demo TIF-12003.strict-case-rules.spec.tsaccepts{ Type: 3, Value: '=vars.x' }. It errors on=vars.xunder types 0, 1 or 2.case-check --sourceon the recipe printscheck: OK.case-compileemits{"Type": 3, "Value": "=vars.approver"}, and the input default lands invariables.inputs[].default.checkwarnSTRICT_RECIPIENT_EXPRESSION_TYPE.uip maestro case validate --strict: the localuipcannot install its maestro-tool (npmedgesOuterror).case debug.RecipientTypedoc comment still says 0/1/3 are "reserved". That comment is stale against the CLI rule and its own ported lint. It should be fixed in builder-sdk.Not covered
CA-232 also asks for test settings that live outside the case, such as an Orchestrator asset. This PR moves the assignee into a case input, which the caller can override at start (
uip maestro case process run --inputs). It does not read the assignee from an asset. That part of CA-232 stays open.Earlier drafts
The first draft's snippet did not compile (
typesis not exported from/case) and used the Flow pathvars.start.output.*. A later draft dropped the recipe because runtime support looked unconfirmed. The evidence above confirms it.Test plan
case-runtime.mdis linked from SKILL.md's reference navigationpytest tests/tasks/uipath-maestro-case/ -q: 459 passed, 2 skipped, 11 subtests passedskill-case-edit-add-task-run-once-default(7/8 on an earlier head) is investigated separately🤖 Generated with Claude Code
https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q
Automatically cherry-picked from #4870 to
release/v1.207by @rockymadden.