governance(#255): enforce required related-work field and disable bla…

[Anirudh77715]

Linked issue

Related #255
Related #299

Existing related work reviewed

Issues/PRs reviewed: #255 (governance proposal), #299 (initial rollout)

Overlap assessment

• Classification: complementary follow-up
• Overlapping items: governance: add advisory intake checks #299 created the issue templates with the related_work field as optional
• Why this is not duplicate/superseded: governance: add advisory intake checks #299 added the field but did not enforce it. **Proposal:** This issue defines the contribution-intake framework we intend to adopt to reduce PR firehose and improve quality/signal. #255 explicitly requires contributors to document related work. This PR tightens enforcement — 4 one-line YAML edits with no functional overlap.

Why this PR should proceed

#255 states: "Issue form requires links to related existing issues/PRs." Currently the field exists but is optional, and blank issues bypass templates entirely. These two gaps allow contributors to skip the research-first requirement.

Note: proposed_track is intentionally left optional per CONTRIBUTING.md — track labels are assigned by maintainers.

Summary

• What changed:
  • related_work validation set to required: true in bug_report.yml, feature_task.yml, question_blocker.yml
  • blank_issues_enabled set to false in config.yml — all issues must now use structured templates
• Why: enforces the research-first intake policy defined in **Proposal:** This issue defines the contribution-intake framework we intend to adopt to reduce PR firehose and improve quality/signal. #255. Blank issues allowed contributors to bypass required fields entirely.

# In all 3 issue templates
-      required: false
+      required: true

# In config.yml
-blank_issues_enabled: true
+blank_issues_enabled: false