The local expectations point is the one I would push further. A skill file can say stop for approval before migrations, but that is advice the model can drop once the context gets long. The harness is where the rule can be enforced: the migration tool refuses to run without an approval record. So skills describe the policy and the harness holds it. It also gives you something measurable for the abstain and seek evidence principle, an abstention rate per run, instead of hoping it shows up.