feat(live-graph): add human approval wait state and transient retry p…

[varunsood189]

Capability

Users can park high-stakes live-graph tasks in a non-blocking WAITING human-approval state, resume or cancel them with human_approval_granted / human_approval_denied, and apply a RetryPolicy that retries transient failures (for example HTTP 429) while immediately failing permanent errors.

Evidence subsection: README.md → Live Graph Extension: Human Approval & Transient Retry Policy.

Proof

• I added one evidence subsection to README.md.
• It contains the exact prompt or API request.
• It contains the graph and ordered event trace.
• It contains the actual final result and evidence.
• It identifies every agent/provider assignment.
• It shows an adversarial failure before the fix and the same attack failing afterward.
• It includes commands that reproduce the result from a fresh checkout.

Boundaries

• glc_v3 still owns all provider credentials and model routing.
• Memory authorization happens before retrieval.
• No .env, credentials, personal memory, databases, or unrestricted local paths are committed.
• uv run ruff check . passes.
• uv run pytest -q passes.

Test results

Verified from a fresh local checkout of this PR branch:

$ uv run ruff check .
All checks passed!

$ uv run pytest -q
49 passed

Extension-focused reproduction:

uv sync
uv run pytest tests/test_live_graph_extension.py

[theschoolofai]

Requesting changes: the PR checklist is entirely unchecked and does not provide the required S13 evidence or test results.