Normalize report prompt style across daily/weekly workflows (h3+ headers + details guidance)

[Copilot]

The workflow-style normalizer identified widespread report prompt hierarchy drift: many daily/weekly workflows still used h1/h2 in prompt instructions, and a subset lacked explicit progressive-disclosure guidance. This PR normalizes those prompt conventions so generated reports align with repository markdown hierarchy expectations.

• Scope: targeted daily/weekly workflow prompts

  • Updated the non-compliant daily/weekly workflow markdown prompts from the normalizer output (excluding upstream-managed source: workflows).
  • Regenerated corresponding .lock.yml files via workflow recompilation.

• Header hierarchy normalization

  • In prompt bodies, demoted report-structure headings from h1/h2 to h3/h4 patterns to enforce “h3 or lower” output guidance.
  • Applied this normalization consistently across the affected workflow set.

• Progressive disclosure completion

  • Added explicit <details><summary><b>Details</b></summary> guidance to workflows in scope that were missing details guidance.

Example of the normalization pattern applied:

### Summary

List findings under `### Findings` and use progressive disclosure for long sections:

<details><summary><b>Details</b></summary>

...items...

</details>

[github-actions]

🤖 PR Triage

Field	Value
Category	chore
Risk	🟡 Medium
Score	50/100 (impact:20, urgency:12, quality:18)
Action	📦 batch_review
Batch	chore-cleanup

Rationale: Large formatting/style normalization across 110 workflow files (draft). Mechanically consistent change but high file-count makes review effort significant. Batch with similar chore PRs.

Generated by 🔧 PR Triage Agent · 242.5 AIC · ⌖ 9.07 AIC · ⊞ 5.6K · ◷