Add Cloud OAuth consent changelog

[atharva-appwrite]

Summary

• Add a changelog entry for the Appwrite Cloud OAuth consent redesign with RAR resource binding
• Explain the read-only permission summary and authorization_details-based project and organization selection

Verification

• Verified wording against ../console PR #3101/#3102 implementation and PR metadata
• Not run: local formatter/checks unavailable because bun and node_modules are not installed in this environment

[appwrite]

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)

Site	Status	Logs	Preview	QR
website 69d7f2670014e24571ca	Ready	View Logs	Preview URL

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)

Site	Status	Logs	Preview	QR
website 68496a17000f03d62013	Processing	View Logs	Preview URL

---

Tip

Ephemeral API keys are generated automatically for each function execution

[greptile-apps]

Greptile Summary

This PR adds a single changelog entry announcing that Appwrite Cloud's OAuth consent screen now displays a read-only permission summary and supports Rich Authorization Requests (RAR) with authorization_details-based project/organization resource binding.

• The entry's prose is clear and technically accurate, covering both the UX improvement (read-only scope summary) and the RAR feature (authorization_details resource selection).
• The file is missing a cover image in the frontmatter and has no corresponding image asset, while nearly all comparable changelog entries include one — particularly important here since the change is a visual consent-screen redesign.
• There is no closing {% arrow_link %} component pointing to docs, a blog post, or the console, which is the conventional pattern for entries of this type.

Confidence Score: 4/5

Safe to merge — this is a documentation-only change with no runtime impact; the two gaps are cosmetic and can be addressed in a follow-up.

The changelog content is accurate and well-written. The only gaps are a missing cover hero image (present in virtually all comparable entries) and the absence of an {% arrow_link %} component for reader follow-through — both are presentational concerns with no functional effect on the site.

Only src/routes/changelog/(entries)/2026-07-03.markdoc is changed. It would benefit from a cover image asset added under src/images/changelog/ and a closing arrow link to related documentation or an announcement.

Important Files Changed

Filename	Overview
src/routes/changelog/(entries)/2026-07-03.markdoc	New changelog entry for Cloud OAuth consent redesign with RAR support; missing a cover image present in most similar entries, and no {% arrow_link %} pointing to docs or an announcement.

_{Reviews (1): Last reviewed commit: "Add Cloud OAuth consent changelog" | Re-trigger Greptile}

[greptile-apps]

Missing cover image in frontmatter

Almost every changelog entry that describes a UI or product change includes a cover field (e.g. cover: /images/changelog/2025-07-03.avif) and a corresponding image file under src/images/changelog/. This entry has no cover field and no matching image exists in the repo. Because this particular change is a visual consent-screen redesign, a cover screenshot would be especially helpful for readers — without it the entry will render without a hero image while all surrounding entries have one.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

No follow-up link for readers

Most changelog entries close with an {% arrow_link %} component pointing to a blog post, docs page, or Discord discussion so readers can explore further. This entry ends without one. If there is a related docs page, blog post, or console deep-link for the new consent flow, adding an {% arrow_link %} would match the existing pattern and give readers a clear next step.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!