Diag Migrate

Bring one external diagnosis note into the vault, one note per pass. Same vault as /skill:diag-write (~/ops, self-describing) — the schema lives there, this skill adds the rewrite rules.

Step 1 — Derive frontmatter from content

• status: root cause confirmed and fix verified in the body → resolved; everything else → undetermined. The source folder's name is a hint, not a verdict — legacy 已解决 notes without a confirmed root cause migrate as undetermined.
• source: Oops prefix → oops, Ops → ops, anything else → ops. Strip the prefix from the title.
• date: from the note's content if present; otherwise the migration date.

Step 2 — Rewrite the body

• Fill ~/ops/template.md sections from the source: 排查过程 keeps the original trail verbatim (fenced outputs, trimmed to the lines that carry the signal); a 复现方法/稳定复现 section folds into 排查过程 as the red loop.
• 环境 missing in the source → write 未记录 (required only for fresh diagnoses, never invent it).
• Screenshots and referenced assets: copy into ~/ops/assets/, fix the paths — the vault stays self-contained. Links leaving the vault (external notes, docs) stay as-is with their original targets.
• Preserve the original's cross-note links as relative paths to the migrated entries.

Step 3 — Labels, index, commit