Skip to content

🍒 [v1.207] fix(uipath-maestro-case): add test-recipient and go-live guidance [CA-232] - #4998

Merged
rockymadden merged 1 commit into
release/v1.207from
fix-case-test-recipient-guidance-CP-to-release-v1-207
Nov 19, 2026
Merged

rockymadden merged 1 commit into
release/v1.207from
fix-case-test-recipient-guidance-CP-to-release-v1-207

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

  • The case skill had no guidance on action recipients or the go-live trap. recipient: '<email>' bakes the address into the plan. To go live, someone must edit every action and publish again.
  • PACT golden thread step 27 caught this. Autopilot routed actions to the user's own email and did not say what going live requires (CA-232).
  • New rules in case-runtime.md § Action recipients and the go-live trap:
    • RULE:case.recipient.externalize gives the recipe for a test or placeholder assignee: declare a case input with a test default, then set recipient: { type: 3, value: '=vars.<input>' }.
      • To go live, change the input default or pass the real address at case start. The actions stay unchanged.
      • The rule also lists the recipient types (0 user id, 1 group, 2 email, 3 expression). It says a bare '=vars.x' string is type 2 and is looked up as an email.
    • RULE:case.recipient.no-silent-default makes the final summary list every assignee that the user did not name as production: input defaults, literal recipients, toUser/toGroup escalation targets, and <UNRESOLVED: ...>. For each, the summary says what going live changes.
      • The rule gates the two commands that start a case instance, case debug and case process run. An <UNRESOLVED> assignee never runs.
      • An unconfirmed address needs the user's answer. A request or pre-approval that names the step counts as that answer.
      • upload, publish, check, compile and validate are not gated.

Evidence for type 3

  • CLI packages/case-tool/src/services/sdd-convert/recipient.ts maps an expression recipient to Type 3, the engine's Unknown (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.md matches), and that a type 3 recipient ran in demo TIF-12003.
  • CLI strict-case-rules.spec.ts accepts { Type: 3, Value: '=vars.x' }. It errors on =vars.x under types 0, 1 or 2.
  • Probe with SDK 6.120.17:
    • case-check --source on the recipe prints check: OK.
    • case-compile emits {"Type": 3, "Value": "=vars.approver"}, and the input default lands in variables.inputs[].default.
    • The same expression written as a bare string makes check warn STRICT_RECIPIENT_EXPRESSION_TYPE.
  • Not run:
    • uip maestro case validate --strict: the local uip cannot install its maestro-tool (npm edgesOut error).
    • case debug.
  • The SDK's own RecipientType doc 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 (types is not exported from /case) and used the Flow path vars.start.output.*. A later draft dropped the recipe because runtime support looked unconfirmed. The evidence above confirms it.

Test plan

  • Adversarial review clean
  • skill-lint CI passes
  • case-runtime.md is linked from SKILL.md's reference navigation
  • pytest tests/tasks/uipath-maestro-case/ -q: 459 passed, 2 skipped, 11 subtests passed
  • Smoke skill-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.207 by @rockymadden.

…-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>
@rockymadden
rockymadden merged commit aa083ff into release/v1.207 Nov 19, 2026
3 checks passed
@rockymadden
rockymadden deleted the fix-case-test-recipient-guidance-CP-to-release-v1-207 branch November 19, 2026 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants