Kickside Atlassian

Jira and Confluence provider for Kickside.

Auth

Two connection modes resolve to a single authenticated transport, so the service and tool layers never branch on auth:

• OAuth (3LO) — self-declared oauth_provider: atlassian, discovered by kickside/oauth and run through kickside.oauth:base_connector. Tokens are stored and refreshed by the oauth subsystem, keyed by the connection component_id. transport.connect resolves the Atlassian cloudId from /oauth/token/accessible-resources to build the api.atlassian.com/ex base.
• Stored credentials — one kickside.connection:connection binding (provider: atlassian) covers both Jira and Confluence. Cloud uses Basic email:api_token; Server/Data Center uses Bearer PAT. Secrets live in the connection component's private_context.

Layout

• core/ — shared transport (auth + HTTP), site/base-url resolution, types.
• connection/ — shared Atlassian connection binding and live Jira/Confluence resource discovery.
• jira/ — Jira REST client and agent traits/tools.
• confluence/ — Confluence REST client and agent traits/tools.

Planes

• A — agent tools: JiraGet/JiraWrite, ConfluenceGet/ConfluenceWrite over OAuth or credential connections.
• B — source flows: automation types store Jira/Confluence selection and private state, schedule through cron, keep source cursors in their own runtime state, and write durable events into their owned threads.