Repository navigation
Document live Confluence validation - #38
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follows merged PR #37 with the environment-status evidence gathered after the real Acme
Confluence page became available.
live-validated;
already_currentrefresh;No production code, schema, API, relationship, assessment, or PR C behavior changes.
Live evidence
The external link was exercised and resolved to the intended Atlassian page continuation. Browser
checks at 1440px, 1024px, and 390px reported zero console errors.
Credential finding
The application adapter remains read-only and implements only the two documented Confluence GET
requests. A read-only call to Confluence's permitted-operations endpoint showed that the currently
configured local Atlassian credential can also update and delete the page. The documentation
therefore does not claim end-to-end least privilege: replacing or restricting that credential
is optional future hardening and is not a PR B blocker for the current demo environment.
Verification
successalready_currentgit diff --checkBoundary confirmations