feat: API specs update for version latest

[appwrite-specifications]

This PR contains API specification updates for version latest.

[greptile-apps]

Confidence Score: 4/5

The PR should not merge until the 2.3.0 contract is published under a stable numbered release path and included in the repository’s release listing.

Findings

1.  Missing Stable 2.3 Contract ▶

Fix with agent prompt

### Issue 1
specs/latest/open-api3-latest.json:4
This changes the moving contract to version 2.3.0, but the repository has no corresponding `specs/2.3.x/open-api3-2.3.x.json` artifact and still lists 2.2.x as the newest archived release. As a result, consumers cannot pin the 2.3 contract for reproducible SDK generation. Please publish the numbered 2.3.x artifact and update the release listing with this promotion.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The PR advances the moving unified OpenAPI contract to 2.3.0 and adds or revises account recovery, domain administration, messaging, TablesDB, project-policy, platform, and manager-resource definitions. The corresponding immutable 2.3.x contract artifact and release listing are missing, leaving consumers unable to pin the newly published contract version.

_{Reviews (1) · Last reviewed commit: "chore: update API specs and SDK examples"}

[greptile-apps]

Missing Stable 2.3 Contract

This changes the moving contract to version 2.3.0, but the repository has no corresponding specs/2.3.x/open-api3-2.3.x.json artifact and still lists 2.2.x as the newest archived release. As a result, consumers cannot pin the 2.3 contract for reproducible SDK generation. Please publish the numbered 2.3.x artifact and update the release listing with this promotion.

Knowledge Base Used:

• Published API contract artifacts
• Contract version progression

Prompt To Fix With AI

This is a comment left during a code review.
Path: specs/latest/open-api3-latest.json
Line: 4

Comment:
**Missing Stable 2.3 Contract**

This changes the moving contract to version 2.3.0, but the repository has no corresponding `specs/2.3.x/open-api3-2.3.x.json` artifact and still lists 2.2.x as the newest archived release. As a result, consumers cannot pin the 2.3 contract for reproducible SDK generation. Please publish the numbered 2.3.x artifact and update the release listing with this promotion.

**Knowledge Base Used:**
- [Published API contract artifacts](https://app.greptile.com/appwrite/-/custom-context/knowledge-base/appwrite/specs/-/docs/api-contract-artifacts.md)
- [Contract version progression](https://app.greptile.com/appwrite/-/custom-context/knowledge-base/appwrite/specs/-/docs/contract-version-progression.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[ChiragAgg5k]

The numbered 2.3.x artifact is generated by a separate run pinned to the 2.3.0 release tag (appwrite-labs/cloud#6061); it opens its own PR, and the README "Available Versions" row is added with it. This PR only refreshes latest.

[greptile-apps]

That context resolves the concern. Since the numbered 2.3.x artifact and the README version entry are intentionally produced by the separate PR from the pinned 2.3.0 release run, this PR is correctly scoped to refresh only latest. I’m withdrawing the finding.