Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

- Move file from docs/howto/ to docs/topics/ (parallels decision_points_as_bricks.md,
  addresses Diataxis how-to vs. explanation concern)
- Update mkdocs.yml nav: remove from howto, add to topics alongside
  decision_points_as_bricks.md
- Fix intro: add 'designed by humans, for humans' thesis and 'not a process
  bottleneck' clarification at top of document (threads at lines 68, 107)
- Add diagram scope clarification: make explicit that Decision Model = SSVC scope,
  Data Mapping and Use & Respond are adjacent but outside scope (thread at line 36)
- Fix 'layer' jargon: replace 'any layer of the model' with explicit enumeration
  of outcomes, decision points, decision table, and data mapping (thread at line 97)
- Fix Use & Respond contradiction: remove direct feedback link that conflicted
  with use.md documentation; restate as 'observing real-world results' (line 105)
- Add prepare.md hyperlink to Input Automation section (thread at line 113)
- Fix all relative links: bootstrap/ -> ../howto/bootstrap/ after file move

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Introduces the standard AI/autonomy term 'human-on-the-loop' in two places
to connect it explicitly to the 'human-scale bottleneck' concept:

- Introduction: adds one sentence defining the term after establishing that
  the decision table can be fully automated
- Conclusion: replaces the closing sentence with an explicit 'human-on-the-loop'
  framing that ties accountability to policy governance, not per-decision review

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>