chore: remove CI-enforced checks from Flue style review

[mvvmm]

Summary

Removes Flue style-guide review rules that duplicate issues already caught by failing CI/build steps. This keeps agent review focused on style and conventions that CI does not reliably enforce.

Removed checks include MDX syntax parse failures, missing component imports or import placement failures, invalid DashButton routes, schema/build-validated required component props, and schema-validated frontmatter fields such as required title and numeric sidebar.order.

Kept checks include style-only link wording/path conventions, image parent-directory guidance, pcx_content_type/description expectations not currently schema-enforced, and component usage preferences such as TypeScriptExample, PackageManagers, and DashButton for dashboard navigation.

Also adds .flue/AGENTS.md with the policy for future review rules: do not add agent findings for issues already reliably caught by CI.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
*	@cloudflare/product-owners
*.ts	@cloudflare/content-engineering, @kodster28

[cloudflare-docs-bot]

Review

⏸️ Automatic reviews for this PR are paused.

This PR has already received 2 automatic reviews. To run another review, a codeowner can comment /review or /full-review.

Tip: Keep PRs in draft mode until they are ready for review — the bot skips draft PRs automatically.

---

✅ No style-guide issues found in commit 1ee10c7.

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.

[ask-bonk]

One minor suggestion posted.

• LOW — .agents/references/style-guide.md line 19: the <zone> placeholder example should be <ZONE_ID> to match the repository convention for variable placeholders (ALL_CAPS_UNDERSCORES).

[ask-bonk]

PR #31287 reviewed.

Labels applied: documentation, content:edit

Summary:
The PR is a focused clarification to the agent style guide reference that correctly scopes the angle bracket escaping rule to literal characters in prose/tables/headings and exempts valid JSX component tags. Good change.

One issue found:

• LOW — .agents/references/style-guide.md line 19: the <zone> placeholder example should be <ZONE_ID> to match the repository's own ALL_CAPS_UNDERSCORES convention for variable placeholders documented later in the same file.

An inline suggestion has been posted on the PR to address this.

github run

[mvvmm]

/bonk review

[ask-bonk]

No issues found. The table format clearly scopes the escaping rule to literal characters and correctly exempts valid JSX syntax.

[ask-bonk]

Review posted on PR #31287.

I reviewed the current diff (commit 898c7bc) and found no issues. The table format is clean, the scope clarification is accurate, and the file passes Prettier formatting. The prior feedback about the <zone> placeholder example was already addressed by the author when they converted the blockquote into a table column in commit 2/3.

github run

[mvvmm]

/review

[github-actions]

Preview URL: https://d9a5f83c.preview.developers.cloudflare.com
Preview Branch URL: https://agents-clarify-angle-bracket-rule.preview.developers.cloudflare.com

[hacyberglobal]

Update files