Components

Each repair stores modular Markdown components.

Component definitions

Key	File	Title	Required
`summary`	`00-summary.md`	Summary	yes
`context`	`10-context.md`	Context	yes
`tool_call`	`20-tool-call.md`	Tool call or command	yes
`expected_behavior`	`30-expected-behavior.md`	Expected behavior	yes
`actual_behavior`	`40-actual-behavior.md`	Actual behavior	yes
`reproduction`	`50-reproduction.md`	Reproduction steps	yes
`impact`	`60-impact.md`	Impact	yes
`workaround`	`70-workaround.md`	Workaround	no
`diagnosis`	`80-diagnosis.md`	Diagnosis or hypothesis	no
`suggested_fix`	`90-suggested-fix.md`	Suggested fix	yes
`validation`	`95-validation.md`	Validation plan	no
`notes`	`99-notes.md`	Notes	no

Component	Content
`summary`	One-paragraph description of the failure or improvement.
`context`	What the agent was doing, relevant state, versions.
`tool_call`	Exact command or tool call attempted (redacted). Use `not applicable` for conceptual improvements.
`expected_behavior`	What should have happened.
`actual_behavior`	Actual error, rejection, or confusing output.
`reproduction`	Minimal steps to reproduce.
`impact`	Why it matters for agent or human workflow.
`workaround`	How the agent continued or why no workaround exists.
`diagnosis`	Root-cause hypothesis with uncertainty.
`suggested_fix`	Proposed code, docs, test, or prompt improvement.
`validation`	Tests or checks maintainers should run after fixing.
`notes`	Additional nonessential details.