docs(plugin): a request for the operator's approval gets its own "Approval requested" section (#4084)

A session's go-ahead request sat inside a completion list as "Blocked by the
permission check", and the operator read it as a fault rather than a question
waiting on them. The reporting-back skill now puts any action held for a yes
under a section headed "Approval requested", near the top of whatever reply
it is: each change numbered so part can be approved, why it needs them, how
it is undone, and what happens after. The Asks table gains an Approval row,
and the completion report's "Needs you" points at the section.

test_reporting_back_skill pins the heading and the row. Plugin version minted:
2026.09.15.1921.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01821k5B3Ysecp9fNYs92Kuy

tests/test_reporting_back_skill.py

@@ -38,6 +38,16 @@ def test_the_completion_report_keeps_its_sections():
         assert section in text, f"the completion report lost its {section!r} section"
 
 
+def test_a_request_for_approval_has_its_own_named_section():
+    """The operator, 2026-09-15 (#4084): a session's go-ahead request sat inside
+    a completion list as "Blocked by the permission check", and read as a
+    fault rather than a question waiting on them. The heading is what they
+    scan for, so it is pinned by name."""
+    text = _text()
+    assert "Approval requested" in text
+    assert "| **Approval**" in text, "the Asks table lost its Approval row"
+
+
 def test_placement_comes_from_the_record():
     """The failure this milestone started from: a placement written from memory
     reads exactly like a real one when it is wrong."""