pull_request_template.md

Summary

What does this PR change, and why?

Type of change

• Bug fix
• New feature
• Refactor / maintenance
• Documentation
• CI / tooling
• RFC (adds/updates docs/rfcs/*)

Area(s)

Select the primary areas touched (labels sync from checked lines when the triage workflow runs):

• Package & tests
• Specification (RFCs)
• Documentation
• Automation & repo config
• Other

Key details

• User-facing behavior: what changes for users (if anything)?
• Internals: what changed architecturally (if anything)?
• Risks: what could break?

Testing / verification

• make ci (or make fmt-check, make build, make test)
• Manual verification described below

Manual verification notes:

• …

Docs impact

• No docs changes needed
• Docs updated
• Docs follow Divio intent (tutorial/how-to/reference/explanation) where applicable

If docs updated:

• Link(s): …

Checklist

• I kept public docs user-focused and moved internals to contributing docs when appropriate
• I avoided duplicating canonical install/run instructions in multiple places
• I added/updated tests where it materially reduces regressions