Repository navigation
Commit 2babdf1
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
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
89 | 89 | | |
90 | 90 | | |
91 | 91 | | |
| 92 | + | |
92 | 93 | | |
93 | 94 | | |
94 | 95 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
35 | 35 | | |
36 | 36 | | |
37 | 37 | | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
38 | 83 | | |
39 | 84 | | |
40 | 85 | | |
| |||
0 commit comments