dora-check

# Delivery Metrics Check Assess delivery health using product-type-appropriate metrics. Check `product_type` from `.claude/diamonds/active.yml` to determine which assessment to run. **Product type routing** (v0.11.0): - **software**: Full DORA + APEX assessment (Parts 1-3 below) - **content_course, content_publication, content_media**: Content Delivery Assessment (Part 4 below) - **ai_tool**: AI Tool Assessment (Part 5 below) + DORA/APEX if code components exist - **service_offering**: Service Delivery Assessment (Part 6 below) --- ## Preflight: Read target canvas file(s) before any Write/Edit **Hard rule.** Before issuing `Write` or `Edit` against any `.claude/canvas/*.yml`, use the **Read tool** on that file in this session. Claude Code's Read-before-Write check requires the `Read` tool specifically — `cat`/`head`/`grep` via Bash do NOT satisfy it. **Edit vs Write — different cost profiles** (verified 2026-05-14): - **`Edit`** (exact-string replacement): `Read` with `limit: 1` satisfies the check at ~50 tokens. State-tracking is per-file, not per-byte — subsequent `Edit` calls work anywhere in the file. Use this for partial updates against large canvas files (e.g., `purpose.yml` at 800+ lines). - **`Write`** (full replacement): do a **full Read** first. Write obliterates the file; you should see what you're about to replace. The `limit:1` shortcut is *not* appropriate here. **ID-bearing entries — scan the ID space before assigning** (added 2026-05-15, v0.23.19): When...