Build a troubleshooting decision tree from these approved rules only.
For each node, include the question, allowed action, source rule ID and
stop/escalation boundary. Preserve missing-source and failed-check paths.
Leave unsupported cases unresolved with a focused question.
Do not invent resets, external writes, integrations or account controls.
Provide editable source/file, readable path list and a few cases that
should expose a missing or incorrect branch.

---

Trace [case] through the tree and name the source rule at each decision.
Identify any action not supplied by the rules. Keep a stop state stopped
until the required source or check exists. Do not interpret choosing a
route as evidence that its action was performed or the issue resolved.

---

Branch [ID] continues after [stop condition], but rule [ID] says [exact
boundary]. Restore the stop/escalation path and update the text path
list. Keep confirmed branches unchanged. Repeat the awkward case and
state what was actually checked. Do not invent a workaround or claim
the real system was repaired because the local diagram now looks right.
