[workflow-style] Normalize Daily Go Function Namer issue-body header formatting

[Copilot]

The Daily Go Function Namer workflow was generating issue-body content with an h1 header, which violates the reporting guideline that reserves h1/h2 for issue titles. This update aligns its template and instructions with the established h3+ reporting pattern used by other daily reporting workflows.

• What changed

  • Updated the issue-body template header in .github/workflows/daily-function-namer.md from h1 to h3.
  • Added explicit header-level guidance in the issue creation section to enforce ### (or lower) headings in generated issue bodies.

• Workflow prompt alignment

  • Ensures generated reports follow the same markdown hierarchy expectations as other compliant reporting workflows.
  • Reduces formatting drift by encoding the rule directly where issue-body structure is defined.

-# 🏷️ Go Function Rename Plan
+### 🏷️ Go Function Rename Plan

[Copilot]

Pull request overview

Normalizes the Daily Go Function Namer workflow’s issue-body markdown so generated GitHub issues avoid H1/H2 headers and follow the repository’s reporting guideline (H3+ headings in issue bodies).

Changes:

• Updated the issue body template’s top header from # to ###.
• Added explicit guidance in the issue creation instructions to require ### (or lower) headings in issue bodies.

Show a summary per file

File	Description
.github/workflows/daily-function-namer.md	Adjusts the issue-body template header level and documents the H3+ requirement to prevent future formatting drift.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0