Added support for creating Work Items

[pcodding]

Description

Added a create_work_item_for_agent action that resolves agents by name and creates Work Items with optional attachments. Attachments now support local paths or chat file basenames (via chat files API), and the Work Item API client handles uploads/confirm flow. Work Item API URL resolution now supports v2 and falls back to v1 on 404 to handle mixed environments. Documentation and devdata were updated accordingly.

Motivation: enable agents to create Work Items for other agents, including passing files from chat context, and ensure compatibility when only v1 Work Item API is available.

Dependencies: no new dependencies added.

How can (was) this tested?

• Ran the create_work_item_for_agent action locally using the devdata input with an attached PDF. Verified Work Item creation and upload flow after iterating on API URL handling and multipart uploads.
• Repro:
  1. Ensure Work Item API is available (v2 preferred, v1 fallback supported).
  2. Run: create_work_item_for_agent using devdata/input_create_work_item_for_agent.json.
  3. Verify a Work Item is created and attachment is present.

Test configuration:

• Tested locally in the SDK using devdata and local file attachments
• Tested in Studio using chat attachments
• Tested in Work Room using chat attachments

Screenshots (if needed)

N/A

Checklist:

• I have bumped the version number for the Action Package / Agent
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation - README.md file
• I have updated the CHANGELOG.md file in correspondence with my changes
• I have added tests that prove my fix is effective or that my feature works
• OAuth2: I have made sure that action has necessary scopes (works in whitelisted mode)

[tonnitommi]

🚢

[joshyorko]

@pcodding I noticed a mismatch in how the environment is being handled versus the actual product architecture.

1. sema4ai-actions Version Strategy The PR currently pins v1.4.2, but v1.6.6 is the latest. There is a significant feature and security delta here:

Security: v1.6.6 includes critical CVE updates not present in 1.4.2.

Features: Sticking to 1.4.2 misses out on Model Selection (added in 1.4.3) and the Dataframe Access APIs (agent.list_data_frames, added in 1.6.0), which limits the agentic capabilities compared to the current platform standard.

2. Redundant uv Configuration Hardcoding uv in package.yaml is technically redundant. The Action Server build (RCC v20.3.1+) bundles the uv 0.8.17 binary, which will supersede whatever is defined here. It’s cleaner to rely on the bundled binary.

Quick tip: The Sema4.ai VS Code extension actually catches these deprecated packages automatically—might be worth checking against that.

[joshyorko]

🚢

@tonnitommi Not sure this was really ready to ship.