Skip to content

Commit 2babdf1

Browse files
roberts-cliffclaude
authored andcommitted
fix(uipath-maestro-case): add test-recipient and go-live guidance [CA-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>
1 parent a7ee357 commit 2babdf1

2 files changed

Lines changed: 46 additions & 0 deletions

File tree

‎skills/uipath-maestro-case/SKILL.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,7 @@ export default casePlan('loan-approval')
8989
.required()
9090
.entryWhen(rule('current-stage-entered')))
9191
.task('Manager Approval', t => t
92+
// Literal recipient is baked into the plan; test or unknown assignee: references/case-runtime.md § Action recipients
9293
.action({ title: 'Approve loan', priority: 'High', recipient: 'manager@corp.com', app: { name: 'LoanApproval', folder: 'Shared' } })
9394
.entryWhen(rule('selected-tasks-completed', { tasks: ['Check Policy'] }))))
9495
.stage('Decision', s => s

‎skills/uipath-maestro-case/references/case-runtime.md‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,51 @@ make from syntax alone. Exact signatures remain in the generated API.
3535
error. Write the complementary condition explicitly, even when the negative
3636
arm only routes to a close-out.
3737

38+
## Action recipients and the go-live trap
39+
40+
<!-- RULE:case.recipient.externalize -->
41+
- A literal `recipient: '<email>'` compiles to `{ Type: 2, Value: <email> }`
42+
and bakes the address into the plan: going live means editing every action
43+
and publishing a new version. When the request names a test, placeholder or
44+
not-yet-known assignee, wire it through a case input instead:
45+
46+
```ts
47+
.input({ approver: { type: 'string', default: '<TEST_EMAIL>' } }, { from: manual })
48+
// ...
49+
.action({ ..., recipient: { type: 3, value: '=vars.approver' } })
50+
```
51+
52+
Going live then means changing the input default, or passing the real
53+
address when the case starts; the actions stay unchanged.
54+
Recipient types are `0` user id, `1` group name, `2` email, `3` expression.
55+
Type `3` evaluates `value` and assigns the result as a user when it is an
56+
email, and as a group name otherwise. An expression needs type `3`: a bare
57+
string `'=vars.approver'` is type `2` and is looked up as a literal email.
58+
`case check` warns `STRICT_RECIPIENT_EXPRESSION_TYPE` on that, and
59+
`case validate --strict` fails. The SDK's `RecipientType` doc comment still
60+
calls `0`/`1`/`3` reserved; that comment is stale, and type `3` is the
61+
expression type the CLI and `case check` accept.
62+
Brownfield: keep a decompiled `{ type, value }` recipient as is.
63+
64+
<!-- RULE:case.recipient.no-silent-default -->
65+
- Before `uip solution upload` or `uip solution publish`, tell the user the
66+
list below, and repeat that list in the final summary of every build or
67+
edit. List each assignee the user did not name as the production assignee: an input default, a literal
68+
`recipient`, or an SLA escalation target (`toUser`, `toGroup`). These include
69+
a test mailbox, the user's own email, and `<UNRESOLVED: ...>`. For each one,
70+
give the address or group, the actions or escalations it routes, and what
71+
going live changes: the input default, or each literal in the source plus a
72+
new published version.
73+
74+
`uip maestro case debug` and `uip maestro case process run` start a case
75+
instance and create real tasks for these assignees. `upload`, `publish`,
76+
`check`, `compile` and `validate` start none. Before `debug` or
77+
`process run`:
78+
1. An assignee still `<UNRESOLVED: ...>`: do not run it.
79+
2. An address or group the user did not confirm: ask. A request or
80+
pre-approval that names that step is the user's answer. When no user can
81+
answer and nothing names that step, do not run it.
82+
3883
## Script tasks
3984

4085
<!-- RULE:case.script.positional-rename -->

0 commit comments

Comments
 (0)