[VarshithaPamisetty]

Description of changes:

Step 3 of the batch DynamoDB operations page served TypeScript client code (client.mutations.batchCreatePost) to all nine platforms, because the section had no InlineFilter at all. Added Swift, Android, and Flutter examples using raw GraphQL, and scoped the existing TypeScript example to the JS platforms.

Two schema defects the examples exposed. The Post model had no authorization rule at any level, so neither amplify/data/resource.ts block could be deployed: .transform() fails with "Model Post is missing authorization rules". And Step 1 declared the mutation argument as content while the handler reads ctx.args.contents and every client call passes contents. Both are fixed, and the deployed schema now matches the page.

The custom operation is renamed BatchCreatePost to batchCreatePost, with the handler file renamed to match, so it follows the convention used by every other custom operation in the Gen2 data docs.

The parent custom business logic page carried the same comments, two of which were inaccurate: // arguments that this query accepts and // return type of the query both sat on the likePost mutation, and // 3. set the function has the handler read "has" for "as". Those comments restate what the adjacent code already says, so they are removed rather than corrected. The highlight-* renderer directives are kept, since TokenList.tsx parses them to produce the highlight affordance.

Checks

• yarn build succeeds with no errors
• Deployed the page's schema to a sandbox and ran all three documents against the live AppSync endpoint; the responses deserialize into the Kotlin, Swift, and Dart types shown
• Ran the accessibility scan locally on both changed pages across all nine platforms, light and dark: 36 scans, no violations

Refs #8267

[mergify]

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.