Skip to content

guide: Atlassian - #139

Merged
svadrutk merged 1 commit into
mainfrom
guide/issue-135-atlassian
Aug 7, 2026
Merged

guide: Atlassian#139
svadrutk merged 1 commit into
mainfrom
guide/issue-135-atlassian

Conversation

@walker-tx

Copy link
Copy Markdown
Member

Closes #135

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

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

Pipeline review (atlassian)

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

Open questions (2)

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 result for the current Atlassian Rovo remote MCP Server? The supplied lookup was ambiguous, so both add-server paths remain conditional.
  • If Use Discovered is unavailable, can the current manual sheet retain the protected-resource-discovered registration endpoint while showing https://auth.atlassian.com as the issuer/base auth URL? The base issuer metadata does not advertise registration, so no unverified manual fallback is claimed.

Optional nits (1)

  • Connect your credentials {#connect-speakeasy-credentials}, step 3: The step refers to an "issuer/base auth URL" instead of naming the sheet's Issuer URL field, leaving a cold reader to infer which field to inspect. → Change the step to say: "Confirm that Issuer URL is:" followed by the existing URL.

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

@walker-tx walker-tx mentioned this pull request Aug 7, 2026
@svadrutk
svadrutk merged commit f62cb98 into main Aug 7, 2026
1 check passed
@svadrutk
svadrutk deleted the guide/issue-135-atlassian branch August 7, 2026 21:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Guide: Atlassian

2 participants