Reduce the Atlassian skills to Jira, and fix eight broken modules

[johnml1135]

Start here: .claude/skills/atlassian-skills/SKILL.md — the Configuration and Core Workflow sections show the shape of the whole change.

The two Atlassian skills supported Jira, Confluence and Bitbucket. FieldWorks uses Jira. Confluence and Bitbucket are gone — 4,362 deletions against 293 insertions — and nine modules that never worked are fixed.

Where to look:

• Nine of twelve read-only modules were unusable. Eight raised NameError on import, so any read through them failed and callers reached into the write skill to do a read. The ninth, jira_projects, imported cleanly and raised an unimported NotFoundError only when a project was absent — a successful import is not evidence a module works.
• The cause was upstream's, and upstream had already fixed it. The bug arrived in cdd1823f6 (2025-12-20) and was fixed in 0fafb48e7 (2026-02-10); d1a9bc66d vendored the pre-fix state on 2026-06-11. Our files are byte-identical to upstream at cdd1823f6 — a stale snapshot, so a re-sync would have fixed this, not reintroduced it. Upstream LT-21672: Add Tables to Word Export #14 is closed as already-fixed.
• Confluence and Bitbucket removed to the roots — not just the script modules but their docs, config blocks, credential fields, the CQL reference, and the plumbing in _common.py. Zero references outside PROVENANCE.md. What remained was rewritten rather than left with holes, and the read-only variant lost 237 lines of function signatures that REFERENCE.md already documents.
• Both frontmatter descriptions advertised Confluence and Bitbucket and are rewritten. An overstated description is how the wrong skill gets loaded.
• PROVENANCE.md records two local modifications that were unlisted: TLS verification is off in three places, because jira.sil.org's certificate chain does not validate here, and the write variant's "no script changes" was untrue.

Deliberately not here: _common.py keeps check_available_skills even though only one service can now be unavailable — load-bearing for the credentials path, cheap to leave.

Verification: pyflakes reports nothing across both variants and all 16 modules import. Live through the read-only skill: jira_get_issue('LT-22723'), jira_get_transitions, and jira_get_project_versions for both a real and an absent project — the last is what the ninth fix buys, and ablating that one import turns it back into a NameError. gitlint clean. No build.ps1/test.ps1: Python utilities outside the build.

Next: review and merge. Independent of #1098/#1099/#1102; #1100 now overlaps by two lines in jira_workflow.py and jira_projects.py, so whichever merges second takes a trivial conflict.

---

Size before and after

	Before	After
atlassian-skills (md + py)	~5,900	3,325
atlassian-readonly-skills (md + py)	~4,400	2,219
Script modules per skill	17	9
Broken modules (read-only)	9	0

SKILL.md specifically: write variant 741 → 382 lines, read-only 560 → 148.

What the licence investigation found

Both skills carry license: Complete terms in LICENSE in frontmatter, which is what stopped an earlier pass from touching them at all. Checking properly:

Question	Answer
Where from?	https://github.com/langpingxue/atlassian-skills, vendored in d1a9bc6
Declared licence?	MIT, in the upstream README
LICENSE file upstream?	No. GitHub's license endpoint 404s
Copyright line anywhere?	No
LICENSE file here?	No — the frontmatter reference dangles in both places

MIT permits modification, so the earlier caution was unnecessary. The attribution it does ask for was missing and now exists as PROVENANCE.md in each skill. Since upstream names no copyright holder, a verbatim MIT text could not honestly be authored on their behalf; the provenance files record the declaration and its gaps instead.

This is now a hard fork. A re-sync is no longer a merge — upstream becomes a source to cherry-pick Jira fixes from. PROVENANCE.md says so.

Data Center gotchas captured while investigating

Upstream's docstrings describe Jira Cloud; SIL's instance is Data Center. Three that silently disagree, now in atlassian-skills/PROVENANCE.md:

• assignee wants a username, not an accountId. jira_create_issue and jira_update_issue both send {"accountId": ...}, which Data Center rejects. Pass custom_fields={"assignee": {"name": "<username>"}}.
• Affects Version is not exposed at all. Pass custom_fields={"versions": [{"name": "FW 9.3"}]}.
• resolution cannot be set by an update — not on the edit screen; only a transition sets it.

Each was found by hitting it. They are duplicated into jira-issue/references/publish.md on #1098, where someone working an LT ticket looks first.

---

This change is 

[github-actions]

NUnit Tests

    1 files  ± 0      1 suites  ±0   11m 31s ⏱️ +31s
5 864 tests +11  5 783 ✅ +11  81 💤 ±0  0 ❌ ±0 
5 873 runs  +11  5 792 ✅ +11  81 💤 ±0  0 ❌ ±0 

Results for commit f1a4455. ± Comparison against base commit 6f72671.

♻️ This comment has been updated with latest results.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 38.36%. Comparing base (6f72671) to head (f1a4455).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1101      +/-   ##
==========================================
+ Coverage   38.33%   38.36%   +0.02%     
==========================================
  Files        1507     1507              
  Lines      350580   350634      +54     
  Branches    40293    40304      +11     
==========================================
+ Hits       134410   134505      +95     
+ Misses     186941   186897      -44     
- Partials    29229    29232       +3     

see 12 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.