feat(uipath-maestro-case): wire connector-activity to case spec --input-details

[song-zhao-25]

Summary

• Switch the case skill's connector-activity plugin from the legacy case tasks describe + is resources describe two-call dance to the unified uip maestro case spec command (CLI shipped on uipcli feat/connector-task-spec).
• Phase 3 now builds the connector task by passing user-collected input-values + filter through case spec --input-details, reading the populated caseShape, substituting {{CONN_BINDING_ID}} / {{FOLDER_BINDING_ID}} placeholders with minted ids, and dropping caseShape.{context, inputs, outputs} straight into caseplan.json.
• Cross-skill borrowing from uipath-maestro-flow's connector plugin: cross-link uipath-platform for filter-trees-ceql / reference-resolution / connections rather than restate; adopt flow's Step-5 hard gate + Step-6a FilterBuilder detection wording.
• Trigger plugins (connector-trigger, triggers/event) are intentionally out of scope here — they follow in PR 2.

What's wired

Doc	Change
connector-activity/planning.md	Resolution pipeline now uses case spec --skip-case-shape for required-field discovery, references with pre-built discoverCommand, and filter contract.
connector-activity/impl-json.md	Phase 3 collapses to one case spec --input-details call → placeholder substitution → mint var/id/elementId → write task. Drops the legacy is resources describe re-fetch.
SKILL.md Rule 10	Connector tasks discover output names via case spec; non-connector tasks via case tasks describe.
connector-integration.md	Top-level orientation rewritten to establish the case-spec-first contract.
registry-discovery.md	Note that case spec is the unified post-pull endpoint for connector tasks.
implementation.md	Phase 2 / Phase 3 step references switched to case spec.
case-commands.md	Adds a full case spec section above the existing case tasks describe (which stays for non-connector tasks).
skeleton-tasks.md	Schema-fetch references include case spec for connector tasks.
references/evals/evals.json	Adds eval #6 — Outlook Send Email end-to-end through the new flow.
.maintenance/case-spec-cli-migration-plan.md (NEW)	Internal planning doc tracking PR 1 + PR 2 split.

Test plan

• Lint pass on changed markdown (no broken cross-links — paths verified during write).
• Eval feat(CodedAgents): file-sync skill and deployment fixes #6 (Outlook Send Email) manual run end-to-end: planning → case spec --skip-case-shape → required-field gate → reference resolution → tasks.md → Phase 3 case spec --input-details → placeholder substitution → caseplan.json populated.
• Verify trigger plugins still run the legacy flow (no accidental cross-pollination from this PR).
• Spot-check the essentialConfiguration round-trip on a real Outlook 365 Send Email task — confirm Studio Web re-renders cleanly.

🤖 Generated with Claude Code

[github-actions]

Claude finished @song-zhao-25's task in 3m 43s —— View job

---

PR Review: feat(uipath-maestro-case): wire connector-activity to case spec --input-details

• Read review criteria and project conventions
• Read PR conversation for existing feedback
• Run full diff and read changed files
• Verify relative links resolve
• Check for cross-skill references, secrets, paths
• Post review

---

Summary

Migrates the connector-activity plugin from the legacy three-call CLI dance (case registry get-connection + case tasks describe + is resources describe) to the unified uip maestro case spec command. The PR rewrites planning.md and impl-json.md for the connector-activity plugin, adds a case spec section to case-commands.md, and cross-links uipath-platform for filter/reference/connection docs rather than restating them. Eval #6 exercises the new end-to-end flow. A new .maintenance/ planning doc tracks the PR 1 + PR 2 split.

Change-by-Change Review

1. .maintenance/case-spec-cli-migration-plan.md (NEW, +329)

Severity: High

The planning doc contains personal filesystem paths on 3 lines:

• Line 4: /Users/song.zhao/Vscode/skills-spec-cli
• Line 139: /Users/song.zhao/Vscode/skills-spec-cli
• Line 159: /Users/song.zhao/Vscode/skills-spec-cli-triggers

Per .github/code_review.md and CLAUDE.md: "No secrets, tokens, API keys, or personal filesystem paths in any file." Fix this →

Additionally, the doc contains links to an external repo that don't resolve within this repo (e.g., ../../../../uipcli/packages/case-tool/docs/spec-input-details.md). These are informational references in a .maintenance/ planning doc so they're not broken from an agent perspective, but noting for awareness.

2. SKILL.md (+1/-1)

Severity: OK

Rule 10 now correctly routes connector tasks to uip maestro case spec and non-connector tasks to uip maestro case tasks describe. Clean, minimal change.

3. references/case-commands.md (+33/-2)

Severity: OK

Adds the case spec command entry above case tasks describe. Well-structured with clear flag table, examples for both planning and Phase 3 usage, and an accurate note that case tasks describe stays for non-connector tasks. The --input-details flag doc includes a cross-link to the external CLI repo doc — this link doesn't resolve locally but the inline description is self-sufficient.

4. references/connector-integration.md (+79/-49)

Severity: OK

Top-level rewrite establishes the case-spec-first contract. The resolution pipeline now has 4 steps instead of the old multi-call dance. Cross-links to uipath-platform for filter/reference/connection rules rather than restating — good reference-pointer discipline. The "Applying Results to caseplan.json" and "Output Contract to Tasks.md" sections are clear.

5. references/evals/evals.json (+18/-0)

Severity: OK

Eval #6 covers the Outlook Send Email happy path end-to-end. Expectations are specific — checks for case spec --skip-case-shape during planning, --input-details during Phase 3, placeholder substitution, and explicitly verifies the agent does NOT fall back to legacy commands. Well-written eval.

6. references/implementation.md (+5/-4)

Severity: OK

Step 9.7 now references case spec instead of is resources describe. The "get-connection (each task runs its own)" instruction is preserved. Clean update.

7. references/plugins/tasks/connector-activity/impl-json.md (+126/-200)

Severity: Medium

The rewrite is the core of this PR and is well-structured. Phase 3 collapses to a clean 10-step flow. However:

a) Personal path (line 217): ~/Documents/knowledge/Skill_CLI/connector/case-spec-fe-discrepancies.md in the Known Limitations section. This is a local filesystem path that no agent or reviewer can access. Fix this →

b) Unresolvable external links: 4 references to ../../../../../../uipcli/packages/case-tool/docs/spec-input-details.md (line 45) and similar. These point to an external repo and won't resolve. The surrounding text is self-sufficient, but the links are misleading. Consider either removing them or noting they're CLI-repo-only.

8. references/plugins/tasks/connector-activity/planning.md (+72/-33)

Severity: Medium (pre-existing)

a) Cache path inconsistency (line 21, pre-existing): Uses ~/.uip/case-resources/ while registry-discovery.md and connector-integration.md use ~/.uipcli/case-resources/. This is pre-existing (not introduced in this PR) but since the file was substantially rewritten, it's worth fixing. Fix this →

Otherwise, the planning rewrite is clean. Step 3 correctly swaps in case spec --skip-case-shape. Steps 4-8 build a clear pipeline from reference resolution through filter authoring to input-values.

9. references/registry-discovery.md (+3/-1)

Severity: OK

Adds a note that case spec is the unified metadata endpoint for connector tasks after registry pull. Well-placed at the end of the Connector Tasks section.

10. references/skeleton-tasks.md (+2/-2)

Severity: OK

Updates the schema-fetch reference in the Upgrade Procedure section to include case spec for connector tasks alongside tasks describe for non-connector tasks. Clean update.

What's Missing

• No new e2e test task YAML in tests/tasks/uipath-maestro-case/ for the case spec workflow. Existing tasks (init_validate.yaml, registry_discovery.yaml) don't cover the connector-activity planning/implementation flow. The eval in evals.json is a specification, not an executable test. Severity: Medium — existing tests don't cover the new capability, though this is consistent with the overall test gap for this skill.

Area Ratings

Area	Status	Notes
Frontmatter	OK	SKILL.md frontmatter unchanged; name matches folder
E2E Tests	Issue	No test YAML for the new case spec workflow (Medium — consistent with existing gap)
Skill Body	OK	Rule 10 update is correct and minimal
References & Assets	Issue	Personal paths in .maintenance/ doc and impl-json.md; cache path inconsistency in planning.md; unresolvable external repo links
Repo Hygiene	Issue	Personal filesystem paths committed (3 in .maintenance/, 1 in impl-json.md)

Duplication Assessment

The reference-pointer discipline is generally good. Cross-skill content (filter trees, reference resolution, connections) is linked to uipath-platform rather than restated. Within the skill, some content appears in both connector-integration.md and planning.md (connection-scoped warning, pagination note, filter anti-pattern), but these are single-sentence warnings appropriate for both the top-level reference and the plugin-level guide — borderline acceptable.

Issues for Manual Review

• CLI correctness: Cannot verify that uip maestro case spec --type activity --activity-type-id <id> --connection-id <id> --skip-case-shape --output json is the exact CLI syntax. The PR states this is shipped on feat/connector-task-spec in the uipcli repo.
• caseShape structure accuracy: Cannot verify the exact shape of caseShape.context[] (8-entry array with {{CONN_BINDING_ID}} / {{FOLDER_BINDING_ID}} placeholders) matches the CLI's actual output.
• essentialConfiguration round-trip: The Known Limitations note says the FE may not render certain fields — confirm this is acceptable for the target use case (Studio Web re-rendering).

Conclusion

Request changes — two actionable items to fix before merge:

1. High: Remove personal filesystem paths from .maintenance/case-spec-cli-migration-plan.md (3 instances of /Users/song.zhao/...) and impl-json.md line 217 (~/Documents/knowledge/...). Per repo rules, no personal paths in committed files.
2. Medium: Fix cache path in planning.md:21 — ~/.uip/ should be ~/.uipcli/ to match the rest of the skill (pre-existing but touched in this PR).

The overall design is sound — collapsing three CLI calls into one, using cross-links instead of duplication, and cleanly separating activity (this PR) from trigger (PR 2).

---