fix(dev): prevent empty documentation quality report issues

[Copilot]

The dev workflow was creating issues with an empty body (bodyLength=1). The agent called create_issue without populating the report content, producing useless daily reports.

Three root causes:

• strict: false — no enforcement on safe-output tool call structure, letting the agent emit an empty body
• Missing toolsets — no toolsets: [default] under tools.github, likely limiting search_issues availability
• No body template — the prompt said "compile a report" but never specified what the body must contain

Changes

• dev.md: strict: false → strict: true
• dev.md: added toolsets: [default] under tools.github
• dev.md: replaced vague 4-point requirements list with explicit 3-step process and a required Markdown body template (Summary → Issues Found table → Documentation Gaps → Could-Be-Closed → Recommendations); agent must either fill all sections or call noop
• dev.lock.yml: recompiled
• compiler_validators.go: moved validateSafeOutputsStepsShellExpansion into the always-error validation table, removing the strict-mode conditional — dangerous shell expansion patterns in safe-outputs.steps scripts are now always a compilation error regardless of the strict frontmatter flag

# before
strict: false
tools:
  github:
    mode: gh-proxy

# after
strict: true
tools:
  github:
    mode: gh-proxy
    toolsets:
      - default

[pelikhan]

@copilot always enforce safeoutputs structure, regardless of strict state.

[Copilot]

@copilot always enforce safeoutputs structure, regardless of strict state.

Done in 6e74b8b. Moved validateSafeOutputsStepsShellExpansion into the always-error validation table in compiler_validators.go, removing the strict-mode conditional. Shell expansion violations in safe-outputs.steps scripts are now always a compilation error regardless of the strict frontmatter flag.