guide: Atlassian

[walker-tx]

Closes #135

Factory draft of guides/atlassian/ via draft-guide (pipeline agents).

Updated by a factory re-run (resume) — prior research/setup on this branch were reused where the lock allowed.

Pipeline converged — ready for human review (agents never commit; this Action did).

Pipeline review (atlassian)

Outcome: Reviewers passed after 2 round(s). Still skim the open questions below before merging.

Open questions (4)

Research could not prove these from public docs. Check the boxes by replying with answers, or say “unknown / omit”. Silence + an existing hedge in the guide usually means omit / keep hedge — not a console capture.

• Does the Speakeasy MCP Catalog contain an exact, current Atlassian Rovo remote MCP Server entry in addition to the deprecated old external-protocol entry?
• After selecting Configure Manually, does the discovered Atlassian issuer remain populated in Issuer URL?
• What stable hosted outbound IP ranges, if any, are available when an organization enforces Atlassian IP allowlists?
• When User Installed Apps is blocked, what exact current Atlassian Administration path approves or installs the Atlassian MCP app?

How to retry

1. Reply on this issue using the Decision N: … lines above (render fixes: apply / override; scope gaps: verified / drop / hedge) and answer open questions.
2. Re-add the guide:draft label. Distill reads the issue body and comments into pipeline notes.
3. If a factory draft PR already exists (guide/issue-<N>-*), the next run resumes on that branch and revises prior research/setup instead of starting blank. Late setup-file fidelity misses get one automatic salvage revise at finalization before surfacing here.

Source: run-record.json