submit-artifactlisted

# submit-artifact ## Overview Every Ralph Workflow artifact is one readable markdown document written in a small, closed grammar and passed to the tools as plain text. Two MCP tools operate on every artifact type: - `ralph_verify_md_artifact({"artifact_type": "<type>", "content": "<markdown>"})` — validate without persisting. Safe to call any number of times. - `ralph_submit_md_artifact({"artifact_type": "<type>", "content": "<markdown>"})` — validate and persist atomically. Rejected documents persist nothing. Supported `artifact_type` values: `plan`, `development_result`, `commit_message`, `commit_cleanup`, `fix_result`, `issues`, `smoke_test_result`, `product_spec`, `planning_analysis_decision`, `development_analysis_decision`, `review_analysis_decision`, `policy_remediation_analysis_decision`. For `plan`, `development_result`, `commit_message`, and `commit_cleanup`, use the dedicated companion skills (`submit-plan-artifact`, `submit-development-result-artifact`, `submit-commit-message-artifact`, `submit-commit-cleanup-artifact`). This skill teaches the shared grammar that every type builds on. ## The Closed Grammar Follow these rules exactly; anything else is a diagnostic: 1. Start with a frontmatter block: a `---` line, one `key: value` field per line, then a closing `---` line. Values are single-line and must not start or end with whitespace. Every type requires at least `type: <type>`. 2. After the frontmatter, use headings and sections documented for