Feat claude plugin

[atharvadeosthale]

This PR adds announcement blog, documentation, and changelog for the new Claude plugin for Appwrite.

[greptile-apps]

Greptile Summary

This PR adds the announcement blog post, changelog entry, and updated documentation for the new Appwrite plugin for Claude Code. The three content files are internally consistent — install commands match between the blog and docs, cross-step anchor links are correct, and the Resources section in the blog now includes the GitHub plugin source link.

Confidence Score: 5/5

This PR is safe to merge — it is a pure content addition (docs, blog, changelog, images) with no logic or runtime concerns.

All changes are Markdown/content files and static images. No logic errors, broken anchor references, or inconsistencies were found. Prior review concerns (missing plugin source link, anchor renames) are resolved in this revision.

No files require special attention.

Important Files Changed

Filename	Overview
src/routes/blog/post/announcing-appwrite-claude-code-plugin/+page.markdoc	New blog post announcing the Claude Code plugin; content is clear, commands are consistent with the docs, and the Resources section now includes the plugin GitHub link.
src/routes/docs/tooling/ai/ai-dev-tools/claude-code/+page.markdoc	Adds a new Step 1 for the Appwrite plugin, shifts existing steps to 2–5; cross-step anchor links (step-3, step-4) are internally consistent.
src/routes/changelog/(entries)/2026-04-20.markdoc	New changelog entry for the Claude Code plugin; links correctly to the announcement blog post.
.optimize-cache.json	Cache updated with SHA hashes for the two new images; no issues.

_{Reviews (2): Last reviewed commit: "add link to github" | Re-trigger Greptile}

[greptile-apps]

Renamed anchors may break existing external links

The section IDs #step-2, #step-3, and #step-4 have been renamed to #step-3, #step-4, and #step-5 respectively. Any external pages, bookmarks, or documentation that linked directly to these anchors will now silently land on the wrong section or scroll to the top of the page. Consider whether redirect aliases are needed, or at least verify that no other pages in the site link to the old anchors before merging.