fix(ci): require non-empty bug Reproduction

[Wibias]

Summary

• Bug reports now fail the issue-quality gate if either Summary or Reproduction is empty (not only when both are).
• Treat punctuation-only stand-ins like ... / … as empty so Open Codex Error #598-shaped reports cannot soft-pass with an ellipsis Reproduction.
• Soft-pass for substantial non-English freeform bodies without English Summary/Reproduction headings (Claude Desktop 3P Auto Mode classifier retries after 64-token Anthropic OAuth outputs #545) is unchanged.

Test plan

• node --test .github/scripts/issue-quality.test.cjs (86 pass)
• After merge + promote to main, open a throwaway bug with Summary filled and Reproduction ... and confirm Enforce issue quality closes it

Summary by CodeRabbit

• Bug Fixes

  • Improved issue validation to recognize punctuation-only or placeholder content as empty.
  • Bug reports with missing summaries or reproduction steps now receive specific guidance identifying the incomplete section.
  • Enhanced validation for incomplete feature-request goals.

• Tests

  • Added coverage for blank, placeholder, and punctuation-only bug report fields.
  • Updated validation tests to verify field-specific feedback.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3da8765f-93c5-4503-a432-c095d85e123c

📥 Commits

Reviewing files that changed from the base of the PR and between 855ed7a and 9a13344.

📒 Files selected for processing (2)

• .github/scripts/issue-quality.cjs
• .github/scripts/issue-quality.test.cjs

---

📝 Walkthrough

Walkthrough

Issue validation now treats punctuation-only content as empty and provides field-specific diagnostics when bug reports lack Summary or Reproduction content. Tests cover blank, placeholder, and ellipsis-only inputs.

Changes

Issue validation

Layer / File(s)	Summary
Broaden empty-content detection .github/scripts/issue-quality.cjs:376-381, .github/scripts/issue-quality.test.cjs:365-366	isEmpty() now classifies cleaned punctuation, symbols, and whitespace as empty; feature validation assertions accept either “too vague” or “missing or empty” reasons.
Add field-specific bug validation .github/scripts/issue-quality.cjs:648-658, .github/scripts/issue-quality.test.cjs:539-602	Bug validation emits separate guidance for missing Summary and Reproduction content, with tests covering blank, “No response”, and ellipsis-only values.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• lidge-jun/opencodex#423: Updates placeholder normalization used by empty-content detection.
• lidge-jun/opencodex#564: Changes bug validation handling for empty Summary and Reproduction fields.

Suggested labels: bug

Suggested reviewers: lidge-jun, ingwannu

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9a133444fd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restrict empty detection to known punctuation placeholders

This pattern classifies every punctuation- or symbol-only value as empty, not just stand-ins such as ... and ---. A concrete reproduction consisting of the problematic payload {}, [], /, or even an emoji is therefore rejected with Reproduction is empty; the enforcement path in .github/workflows/enforce-issue-quality.yml then closes the report. Match only known placeholder forms (such as ellipses or repeated dashes) rather than all Unicode punctuation and symbols.

Useful? React with 👍 / 👎.