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`, `partial`, or `failed`. Any other status is invalid and must be repaired before submission. Most section rules below apply to `status: completed` only. A `status: partial` or `status: failed` document is otherwise free-form below the frontmatter, except that `## Summary` is always required and — once the run's cycle timebox has warned — `## Incomplete Work` is too, every item carrying a stable-ID bracket, a `Reason:`, and an `Evidence:`. Under that same warning a `completed` result must carry `## Plan Items Proven`. The `## Incomplete Work` section is a CLOSED grammar, not free-form: it accepts only top-level `- [ID] text` bullets and their indented `Reason:` / `Evidence:` lines, in a single section. Prose, other bullet markers, numbered lists, nested entries, extra fields, `### [ID]` sub-blocks and a repeated section are all rejected — not because they are wrong to write, but because the report reads none of them, so accepting them would silently delete the work they describe. Put every remaining i