feat: add agents.sessions.setStatus and agents.sessions.rename

[zimeg]

Adds the agents.sessions.* Web API methods — the agent-sessions successors to assistant.threads.setStatus / assistant.threads.setTitle.

Documentation

• agents.sessions.setStatus — set an agent session's lifecycle status, creating the session if needed.
• agents.sessions.rename — rename an agent session.

Methods

• agents.sessions.setStatus — channel_id (required), status (required), optional thread_ts, title, initiator_user_id, icon_emoji, icon_url, username
• agents.sessions.rename — channel_id (required), title (required), optional thread_ts

Bot token scope: chat:write. Rate limit: Tier 3 (both).

What's included

• Request classes: AgentsSessionsSetStatusRequest, AgentsSessionsRenameRequest
• Response classes: AgentsSessionsSetStatusResponse, AgentsSessionsRenameResponse
• Sync + async client method declarations and implementations
• RequestFormBuilder form serialization
• Rate-limit tier registration (MethodsRateLimits + rate_limit_tiers.json)
• Response-sample dump (MethodsResponseDumpTest.agents_sessions()) for downstream type generation
• Remote API tests (test_with_remote_apis/methods/agents_sessions_Test) — assume-gated on a bot token, so they skip cleanly without credentials

Mirrors the Python SDK implementation (slackapi/python-slack-sdk#1942). Draft/experimental.

[codecov]

Codecov Report

❌ Patch coverage is 8.00000% with 23 lines in your changes missing coverage. Please review.
✅ Project coverage is 72.87%. Comparing base (0bcc88f) to head (3aaade9).
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...java/com/slack/api/methods/RequestFormBuilder.java	0.00%	15 Missing ⚠️
...slack/api/methods/impl/AsyncMethodsClientImpl.java	0.00%	4 Missing ⚠️
.../com/slack/api/methods/impl/MethodsClientImpl.java	0.00%	4 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1633      +/-   ##
============================================
- Coverage     72.99%   72.87%   -0.12%     
+ Complexity     4523     4522       -1     
============================================
  Files           479      479              
  Lines         14365    14390      +25     
  Branches       1503     1503              
============================================
+ Hits          10486    10487       +1     
- Misses         2989     3013      +24     
  Partials        890      890              

Flag	Coverage Δ
jdk-14	72.87% <8.00%> (-0.12%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

[zimeg]

Self-review notes (author) — for a reviewer's context

Sharing what I checked so a reviewer has the full picture. This is a self-review, not an approval.

Scope

• Rebased onto current main so the diff is exactly the agent-sessions work (16 files) — request/response classes, sync + async client declarations + impls, RequestFormBuilder serialization, Methods constants, rate-limit tier registration (MethodsRateLimits + rate_limit_tiers.json), the MethodsResponseDumpTest.agents_sessions() dump, the remote test, and the two committed JSON samples. Nothing unrelated.

Correctness

• Clones the established assistant.threads.* add-a-method pattern across every touchpoint (interface + impl, sync + async, form builder, rate-limit metadata, dump test).
• Ordering is alphabetical by family in each file: admin.workflows → agents.sessions → api → apps → assistant.
• Argument sets match the reference docs and are identical to the Python (feat(web-api): add agents.sessions.setStatus and agents.sessions.rename python-slack-sdk#1942, merged) and Node (feat(web-api): add agents.sessions.rename and agents.sessions.setStatus node-slack-sdk#2703) implementations.
• Bot token scope chat:write; both methods registered as Tier 3.

Testing

• mvn -pl slack-api-client -am compile — BUILD SUCCESS against current main.
• The remote test (test_with_remote_apis/methods/agents_sessions_Test) was run live against a test workspace: chat.postMessage → setStatus(processing, title) → rename → setStatus(closed), all ok: true. The response classes were shaped from that live response (Gson strict-mode surfaced status / agent_status / title), and the committed json-logs/samples/api/agents.sessions.*.json are what the node-slack-sdk type generator consumes.

Docs: agents.sessions.setStatus, agents.sessions.rename.