CI(body): Allow normal markdown body

.github/workflows/pr-message.yml

@@ -74,28 +74,19 @@ jobs:
               return;
             }
 
-            if (body.length > 0) {
-              const invalidLines = body
-                .split("\n")
-                .map((line, index) => ({ line, number: index + 1 }))
-                .filter(({ line }) => !/^- .+/.test(line));
+            const conflictMarkerRe =
+              /^<{7}(?: .*)?$[\s\S]*^={7}$[\s\S]*^>{7}(?: .*)?$/m;
 
-              if (invalidLines.length > 0) {
-                core.setFailed(
-                  [
-                    "Invalid PR body.",
-                    "",
-                    'If PR body is present, every line must start with "- ".',
-                    "Blank lines are not allowed.",
-                    "",
-                    "Invalid lines:",
-                    ...invalidLines.map(
-                      ({ number, line }) => `  line ${number}: ${line || "<blank line>"}`
-                    ),
-                  ].join("\n")
-                );
-                return;
-              }
+            if (conflictMarkerRe.test(body)) {
+              core.setFailed(
+                [
+                  "Invalid PR body.",
+                  "",
+                  "The body appears to contain unresolved merge conflict markers.",
+                  "Please resolve the conflict markers before opening or updating the PR.",
+                ].join("\n")
+              );
+              return;
             }
 
             core.info("PR title and body look good.");

AGENTS.md

@@ -54,7 +54,7 @@ make release
 ## Git And PRs
 
 - Use Conventional Commits for commit messages and PR titles.
-- Keep PR bodies compatible with `.github/workflows/pr-message.yml`: each line starts with `- `, no blank lines, no `Co-authored-by:` trailers.
+- Keep PR bodies compatible with `.github/workflows/pr-message.yml`: use concise GitHub Markdown, and do not include `Co-authored-by:` trailers or unresolved conflict markers.
 - Keep PR bodies short and focused on summary, validation, impact, related issues, and notes.
 - Check PR CI before requesting review or merge.