Record the ticket key in the branch name and Source changes

[10zingpd]

Follow-up to #5262. Stacked on it — based on its head, so the diff below includes its content until that merges.

Problem

Docs PRs branch as claude/update-<description> and cite only <repo>#<number>. Neither carries a ticket key, so GitHub for Jira never links the PR and no DOCS ticket knows about it.

Before the poller went live on 2026-04-07, 188 of 350 docs PRs (54%) had a DOCS key in the branch. After: 1 of 350.

Changes

docs-agent/playbook-daily-code-changes.md:

1. Branch naming — DOCS key, else upstream key, else the existing fallback
2. Source changes — prefix with the bare <TICKET-KEY>
3. Recording the ticket key — how to obtain and resolve it
4. Review in progress — the ticket moves when a docs PR opens, via a Jira Automation rule

Verified

• A branch carrying a DOCS key links the PR automatically — DOCS-4927 ↔ [DOCS-4927] Test Jira sync loop #5261
• The integration indexes events, not edits: a title change alone does nothing until a push makes it rescan — DOCS-4836 ↔ [DOCS-4836] Document SDK request tracing for Python and C++ #5212
• Branch, title, commit message and body are all carriers but populate different tabs; a commit message alone gives a commit link, not a PR link — DOCS-4811 ↔ [DOCS-4811] Document the AI configuration assistant #5217
• [DOCS-4930] Add --order and --range flags to machines logs CLI reference #5263 is the motivating case: it cited app#13122, titled [APP-17430], and DOCS-4930 is blocked by APP-17430. Every hop existed; nothing wrote the key down.

Backfill

Mapping merged docs PRs back to open tickets by hand closed 16 DOCS tickets — 13 traced through a PR that cited the upstream change, 3 matched directly to merged docs. That was one manual pass over the backlog; the convention above is what removes the need for the next one.

To Do

The DOCS-key lookup only stops being best-effort once the agent has Jira read access. That means three variables in the Claude Code cloud agent's trigger environment, alongside the existing GH_TOKEN — not in this repo, not in viam-code-map, and not in any file (per docs-agent/README.md):

JIRA_BASE_URL    https://viam.atlassian.net
JIRA_USER_EMAIL  <service account>
JIRA_API_TOKEN   <scoped token, read:jira-work>

Read-only. Browse Projects on DOCS, APP and RSDK is the whole permission set — linkedIssues() reads both ends of the link, and the transition is performed by the automation rule under its own actor, so the agent never needs write access.

Until that exists, the agent writes the upstream key and the rule covers only PRs whose branch already carries a DOCS key.

[netlify]

❌ Deploy Preview for viam-docs failed. Why did it fail? →

Name	Link
🔨 Latest commit	8935393
🔍 Latest deploy log	https://app.netlify.com/projects/viam-docs/deploys/6a85fcfe79addd0008477aa9

[10zingpd]

cc Jeremy Rose (@jeremyrose-viam) Eliza Farley (@elizafarley)