feat(form,team,kudos): forms lifecycle + team-aware kudos

[xergioalex]

Summary

Implements the api-services cross-repo handoff for the forms-response lifecycle and team-aware kudos. Three additive workstreams on dailybot:

• Forms lifecycle. Extends dailybot form with get, responses, response get, update, transition, delete so a coding agent can drive any form — including workflow-enabled ones — end-to-end after dailybot login.
• Teams. New dailybot team list / dailybot team get [--with-members] consuming GET /v1/teams/. Visibility is scoped server-side by role (admins see all org teams, members see only their own). The CLI never client-filters.
• Team-aware kudos. dailybot kudos give accepts --to, --team, or both. Payload migrated from receivers to user_uuid_receivers + team_uuid_receivers per the new api-services contract.

Surface added

Command	Endpoint
dailybot form get <uuid>	GET /v1/forms/<uuid>/
dailybot form responses <uuid> [--state] [--latest]	GET /v1/forms/<uuid>/responses/
dailybot form response get <uuid> <resp>	GET /v1/forms/<uuid>/responses/<resp>/
dailybot form update <uuid> <resp> --content '{...}'	PATCH …/responses/<resp>/
dailybot form transition <uuid> <resp> <state> [--note]	POST …/responses/<resp>/transition/
dailybot form delete <uuid> <resp>	DELETE …/responses/<resp>/
dailybot team list	GET /v1/teams/
dailybot team get <uuid_or_name> [--with-members]	GET /v1/teams/<uuid>/ + …/members/
dailybot kudos give --team <name_or_uuid>	POST /v1/kudos/ (new payload)

Error-code mapping

APIError now carries the code from {detail, code} 4xx bodies. exit_for_api_error maps every server code from the handoff to a friendly message + structured exit code:

• form_response_change_state_forbidden, final_state_locked, form_response_delete_forbidden, user_can_not_see_form_responses → 403 → exit 4
• form_response_not_found, form_does_not_exists → 404 → exit 5 (new EXIT_NOT_FOUND)
• payload_too_large, no_valid_team, no_valid_users, no_users_found → 400 → exit 2

--json output surfaces error, status, code, and detail so chat-agent consumers can pattern-match on the structured shape.

Tests

• 24 new tests across tests/api_client_test.py and tests/public_api_commands_test.py covering: form get / responses (state filter + latest) / response get (404) / update / transition (forbidden + final_state_locked) / delete (forbidden); team list / team get / team get --with-members; kudos give --team / kudos give --to + --team / kudos give --team unseen-team / kudos give without --to or --team.
• Existing kudos test migrated to the user_uuid_receivers / team_uuid_receivers payload shape.
• ruff check, ruff format --check, mypy dailybot_cli — all clean.
• 182/182 new + touched tests pass. The 11 pre-existing failures in commands_test.py exist on bare main (unrelated CLI Agent vs CLI agent-name resolution).

Live validation

Verified against the local api-services dev server (http://djangovscode:8000) via clitest-local:

• dailybot login → multi-org selection works (XergioAleXDailyBot selected).
• dailybot team list → returns General, Tech, Product (admin view).
• dailybot user list → returns the 4 org members.
• dailybot form list → returns all 6 org forms.
• dailybot form get, form submit, form response get, form update, form transition exercised end-to-end on the "Code Release Form" (65de0ec6-…). Response 04dbefcf-… walked null → pre_release → qa → code_review with notes; workflow surface (current_state, allowed_transitions, state_history) rendered correctly after every mutation.

Docs

• README.md — new sections for form get / responses / response get / update / transition / delete, the team commands, team-aware kudos, the workflow-state vocabulary, and the structured-code JSON mode.
• AGENTS.md (≡ CLAUDE.md) — project overview now covers forms-lifecycle, workflow states, team browsing, team-aware kudos. Endpoint list extended. Project Structure tree shows all per-command files.
• docs/API_REFERENCE.md — every new subcommand documented with its endpoint, options, and the full server-code error table.
• docs/PRODUCT_SPEC.md — feature matrix split out per new command.
• docs/CLI_COMMAND_BEST_PRACTICES.md — note on short-alias per-command scoping.
• docs/DISPLAY_OUTPUT_BEST_PRACTICES.md — 7 new specialized renderers documented.
• docs/TESTING_GUIDE.md — coverage expectations: happy + error path per code + JSON-mode shape; "no legacy receivers key" rule.
• docs/TROUBLESHOOTING.md — new Forms & Workflow + Teams & Kudos sections covering every server code, plus a Form-response Markdown: supported subset entry (only single-level # headings render; real \n newlines required; rest of the inline + block features documented).

Risks

• The /v1/kudos/ payload no longer includes the legacy receivers field. Coordinated with api-services per the cross-repo handoff — backend is fully ready.
• No new env variables, no new Python dependencies, no Homebrew formula changes.
• No changes to auth resolution or repo-profile behavior.
• Backward compatible across all stored files (agents.json, config.json, credentials.json, .dailybot/profile.json) — no schema changes.

Release notes

• Release order: this CLI PR must land after the api-services PRs (#7078, #8589, #3067) are deployed — those endpoints are required at runtime.
• auto-release.yml will cut the next bump automatically on merge per default_bump_level = 2 in pyproject.toml.
• Post-release: ping the agent-skill repo so forms/SKILL.md can re-test end-to-end against the new CLI version.

Test plan

• dailybot form get <uuid> renders questions + workflow states.
• dailybot form responses <uuid> --latest --json returns at most one response.
• dailybot form transition maps form_response_change_state_forbidden (exit 4) and final_state_locked (exit 4).
• dailybot team list returns admin's all-teams set; member view scoped server-side.
• dailybot kudos give --team "Tech" posts with team_uuid_receivers.
• dailybot kudos give --to "X" --team "Y" posts both arrays.
• dailybot form delete honors author / owner / admin invariant.

🤖 Generated with Claude Code