# Migration to 0.6.2 — risks name harms

One structural walk. The firmness contract applies: never touch a
human's content bytes beyond the mechanical move described; surface
any conflict.

## 1. Remove `Validation question` sections from `docs/risks/*.md`

The section is removed from the risk-file shape (see the amended
`risks-README.md`): risk files name harms; demands live in ADRs;
managed-ness is computed (coverage table + judged conformance). Per
risk file:

- an EMPTY or `TODO` question section: delete it outright (it was a
  hole in a field that no longer exists — the file may thereby reach
  zero holes and clear its `dds-stub` marker).
- an AUTHORED question: do not discard human content silently — move
  the text into the file's `Current state` as a dated note
  ("legacy validation question, retired <date>: …") OR, where the
  question's demands plainly restate a covering ADR's Rule, delete it
  and say so in the migration commit body. Ambiguous cases are
  surfaced, not decided.

## 2. Re-verify stub markers

After the removals, re-run the marker rule (marker present iff holes
remain) — question-`TODO`s were holes; their removal may clear files.