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-agent-task-a-00.txt

@@ -310,6 +310,33 @@ Table of Contents
    execution parameters that govern how the workflow should be
    processed.
 
+                  +-----------+
+                  |  Task A   |
+                  |  (ingest) |
+                  +-----+-----+
+                       / \
+                      /   \
+                     v     v
+              +---------+ +---------+
+              | Task B  | | Task C  |
+              | (parse) | |(enrich) |
+              +----+----+ +----+----+
+                    \         /
+                     \       /
+                      v     v
+                  +-----------+
+                  |  Task D   |
+                  |  (merge)  |
+                  +-----+-----+
+                        |
+                        v
+                  +-----------+
+                  |  Task E   |
+                  |  (report) |
+                  +-----------+
+
+     Figure 1: Example Agent Task DAG Structure
+
    Task nodes within the DAG represent atomic units of work that can
    be executed by autonomous agents. Each task node MUST specify its
    execution requirements, including required agent capabilities,
@@ -386,6 +413,18 @@ Table of Contents
    alternate execution paths depending on the configured failure
    handling policies.
 
+   +---------+  deps met  +-------+  assign  +----------+
+   | Pending |----------->| Ready |--------->|Executing |
+   +---------+            +---+---+          +----+--+--+
+                              |                   |  |
+                              | skip          fail|  |ok
+                              v                   v  v
+                          +--------+       +------+--+---+
+                          |Skipped |       |Failed|Compl.|
+                          +--------+       +------+------+
+
+    Figure 2: Task Node Execution State Transitions
+
    Integration with existing agent protocols occurs through
    standardized interfaces that abstract the underlying communication
    mechanisms. The framework MUST support protocol-agnostic bindings