submit-development-result-artifactlisted

# submit-development-result-artifact ## Overview A development result is one markdown document (`artifact_type: "development_result"`) reporting what was done, which files changed, and — as stable-ID list items — the proof that plan steps and analysis fixes were actually addressed. Submit with `ralph_submit_md_artifact`; pre-check with `ralph_verify_md_artifact`. ## Document Shape Frontmatter: `type: development_result` and exactly one closed-vocabulary status: `completed` or `partial`. Any other status is invalid and must be repaired before submission. The section rules below apply to `status: completed` only. A `status: partial` document is free-form below the frontmatter: no section is required or shaped, and no proof is demanded. Write whatever best hands your unfinished work to the next iteration — `## Summary`, `## Next Steps` and `## Continuation` (your session ID) are read when present and are the most useful things to include. | Section | Required (`completed`) | Items | |---|---|---| | `## Summary` | yes | exactly 1 | | `## Files Changed` | yes | 1+ (one file per item) | | `## Plan Items Proven` | no | one per plan step proven | | `## Next Steps` | no | exactly 1 | | `## Continuation` | no | exactly 1: the prior session ID | | `## Analysis Items Addressed` | no | one per analysis fix addressed | ## ID-Based Proof References Proof entries reference other artifacts by their stable item IDs — the ID goes in the `[ID]` slot and the proof is the item text: - `#