[Audit Logs] Add Resource History section to Audit Logs v2 page

[Sahidya]

Adds a new Resource History section to the Audit Logs v2 documentation page, covering both the dashboard experience and the History API endpoint.

What this adds

• Overview of Resource History — what it does, how it uses existing audit log entries, no additional configuration needed.
• Dashboard usage — step-by-step for viewing change history and side-by-side diffs from any audit log entry.
• API usage — full documentation of the GET .../logs/audit/{id}/history endpoint for account and organization scopes.

API section details

• Path parameter: {id} (the source audit log entry).
• Required query parameters: action_time, since, before.
• Optional query parameters: direction, limit, cursor.
• Required token permissions: Account Settings Read or Account Settings Write.
• history_status values documented: exact, approximate, unavailable.
• <APIRequest> component renders the request/response schema directly from the OpenAPI spec.

Also bumps the pinned api-schemas commit

src/util/api.ts is bumped from 082fe875… to 25d60329… so the History endpoint resolves in <APIRequest>. This matches the pending automated bot PR #31888. If #31888 lands first, this change becomes a no-op.

Validation

Ran locally against the full CI pipeline:

• pnpm run check (Astro + Worker tsc): 0 errors
• Prettier: pass
• pnpm run build with RUN_LINK_CHECK=true: 8,636 pages, all internal links valid

[cloudflare-docs-bot]

Review

⚠️ 3 warnings, 💡 1 suggestion found in commit 76500d3.

Fix in your agent

Fix the following review findings in PR #32078 (https://github.com/cloudflare/cloudflare-docs/pull/32078).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, fix all legitimate findings. For any you decide to skip,
post a comment on this PR with the finding ID and your reasoning.

---

## Code Review

### Warnings (1)

#### CR-743752e6d560 · Malformed aside closing marker
- **File:** `src/content/docs/fundamentals/account/account-security/audit-logs.mdx` line 173
- **Issue:** The closing `:::` for the `:::note[Required API token permissions]` aside is indented with two spaces (`  :::`). Starlight aside delimiters need to be at the start of a line; an indented closing marker can prevent the aside from closing correctly.
- **Fix:** Move the closing `:::` to the start of the line so it matches the opening delimiter and the aside renders correctly.

---

## Style Guide Review

### Warnings (2)

#### SG-d2169bc98d6c · Heading begins with -ing verb
- **File:** `src/content/docs/fundamentals/account/account-security/audit-logs.mdx` line 139
- **Issue:** Added heading `### Using Resource History in the dashboard` starts with `Using`
- **Fix:** Use imperative form: `### Use Resource History in the dashboard`

#### SG-3e01da80cea3 · Heading begins with -ing verb
- **File:** `src/content/docs/fundamentals/account/account-security/audit-logs.mdx` line 150
- **Issue:** Added heading `### Using Resource History via the API` starts with `Using`
- **Fix:** Use imperative form: `### Use Resource History via the API`

### Suggestions (1)

#### SG-7a9c95d55f99 · Bullet list has fewer than three items
- **File:** `src/content/docs/fundamentals/account/account-security/audit-logs.mdx` line 136
- **Issue:** Added bullet list under `### What Resource History gives you` contains only two items
- **Fix:** Consider writing the two items as prose instead of a bulleted list

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (1)

File	Issue
fundamentals/account/account-security/audit-logs.mdx line 173	Malformed aside closing marker — The closing ::: for the :::note[Required API token permissions] aside is indented with two spaces ( :::). Starlight aside delimiters need to be at the start of a line; an indented closing marker can prevent the aside from closing correctly. Fix: Move the closing ::: to the start of the line so it matches the opening delimiter and the aside renders correctly.

Conventions

_{No convention issues found.}

Style Guide Review

Warnings (2)

File	Issue
fundamentals/account/account-security/audit-logs.mdx line 139	Heading begins with -ing verb — Added heading ### Using Resource History in the dashboard starts with Using Fix: Use imperative form: ### Use Resource History in the dashboard
fundamentals/account/account-security/audit-logs.mdx line 150	Heading begins with -ing verb — Added heading ### Using Resource History via the API starts with Using Fix: Use imperative form: ### Use Resource History via the API

Suggestions (1)

File	Issue
fundamentals/account/account-security/audit-logs.mdx line 136	Bullet list has fewer than three items — Added bullet list under ### What Resource History gives you contains only two items Fix: Consider writing the two items as prose instead of a bulleted list

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.

[cf-ypark]

User can select a single entry to compare with the selected log. In other words, the user can change the previous log entry to compare with.

[cf-ypark]

UI doesn't show a warning banner for this. This is used more for internal investigation, so maybe we shouldn't even mention. I suggest we remove this line.

[cf-ypark]

Please see the other comment. User cannot select two entries freely. Once they pick the audit log entry, all they can change is the past entry to compare with.