Add ASCII art figures to all 6 generated Internet-Drafts

Each draft gets 2 illustrative figures:
- ABVP: architecture components + verification workflow
- ATD: example DAG structure + execution state transitions
- HITL: primitive framework overview + approval workflow sequence
- AEM/PPALP: federated learning architecture + aggregation flow
- RARP: cross-domain architecture + two-phase rollback protocol
- APAE: layered architecture + cross-domain provenance tracking

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

data/reports/generated-drafts/draft-ai-primitives-for-00.txt

@@ -308,6 +308,32 @@ Table of Contents
    these primitives to be composed into comprehensive oversight
    systems tailored to specific operational requirements.
 
+   +-----------------------+
+   |  AI Agent Decision    |
+   |       Loop            |
+   +-----------+-----------+
+               |
+               v
+   +-----------+-----------+
+   |   Decision Point      |
+   |    Evaluator          |
+   +-----------+-----------+
+          /    |    \
+         /     |     \
+        v      v      v
+   +------+ +------+ +---------+
+   |Appro-| |Over- | |Explain- |
+   | val  | |ride  | |ability  |
+   +--+---+ +--+---+ +----+----+
+      |        |           |
+      v        v           v
+   +--+--------+-----+  +-+--------+
+   | Human Operator   |  | Audit   |
+   | Interface        |  | Log     |
+   +------------------+  +---------+
+
+   Figure 1: HITL Primitive Framework Overview
+
    At the architectural level, HITL primitives integrate with agent
    systems through well-defined decision points where human
    intervention may be required. These decision points are identified
@@ -355,6 +381,24 @@ Table of Contents
    preserving operational efficiency through selective intervention
    points.
 
+   Agent       HITL Middleware     Human Operator
+     |              |                   |
+     |--action----->|                   |
+     |  request     |--approval req---->|
+     |              |  +context, risk   |
+     |              |                   |
+     |              |<---approve/deny---|
+     |              |  +auth token      |
+     |<--result-----|                   |
+     |  proceed     |                   |
+     |  or halt     |                   |
+     |              |                   |
+     |  [timeout]   |                   |
+     |<--fallback---|                   |
+     |              |                   |
+
+    Figure 2: Approval Workflow Sequence
+
    The core approval request structure MUST include the proposed
    action description, associated risk assessment, relevant context
    for human evaluation, and expected execution timeline. Each