ws-jira-conventionslisted

# WS Agency Jira Conventions How we link git activity to Jira at WS Agency. Aligns with Atlassian's official Smart Commits and dev-connector recognition rules. ## Branch naming ``` <TICKET-KEY>-<slugified-summary> ``` Examples: - `WSC-142-otp-screen` - `WSC-138-token-refresh-race` - `WSC-150-dark-mode-toggle` Ticket key first → Jira auto-detects via the GitHub/Bitbucket/Gitea dev connector. Key MUST be uppercase. ## Commit messages Format: **Conventional Commits + Jira suffix**. ``` <type>(<scope>): <imperative description> (<TICKET-KEY>) - optional body bullets Refs: <TICKET-KEY> ``` Examples: ``` feat(auth): add OTP screen for login (WSC-142) - validates 6-digit code - handles 30s resend timeout Refs: WSC-142 ``` ``` fix(api): handle expired token race (WSC-138) Refs: WSC-138 ``` Rules: - `type`: feat, fix, refactor, chore, docs, test, perf, style, build, ci - Subject ≤ 72 chars including ` (WSC-XXX)` suffix - Ticket key uppercase, in parens at end of subject - `Refs:` trailer at the end of the body (git-trailers convention) ## Smart Commits (optional record, not the mechanism) Since the jira-cli migration, worklogs/transitions/comments are applied by **explicit jira-cli calls** (`jira issue worklog add`, `jira issue move`, `jira issue comment add`) — the trailer below is a human-readable record in the commit body, included when `defaults.smart_commit_trailer: true` (default). ⚠️ If your Jira has an active dev-connector that ingests Smart Commits from th