[RELEASE] Orchestration capture: workflows + sub-agents per session (carries #5008)

[vivekchand]

Publishes #5008 to PyPI: every session now shows the Workflow runs + sub-agents it spawned — the context each child was handed, what it replied, and the tool it is on right now — in the Activity feed (session filter chips + per-block badges) and the Sessions transcript viewer (Orchestration panel). Claude Code adapter half already merged in clawmetry-pro #147 (0.7.x line).

🤖 Generated with Claude Code

[8090-software-factory]

✅ Drift Bot (ClawMetry): no drift detected

Drift Bot analyzed the changed files against this project's blueprints and requirements and found no drift.

[vivekchand]

blocked on author decision — skipping (auto-mergeability sweep)

The required CI checks (Syntax & Lint, PR build, E2E Gate, Cross-repo handoff, C6 gate) all failed in 2 seconds, consistent with the GitHub Actions billing lock described in #5009's thread. No code issue found. Unblocks as soon as the billing lock is resolved and CI is re-run.

---

Generated by Claude Code

[vivekchand]

Blocker: phantom CI cascade from main regression (not a real test failure)

All check runs on this PR complete in 2-3 seconds with no runner assigned — classic concurrency-cancellation phantoms. The E2E Gate (required) is failing the same way (completed at 03:24:52Z after 2 seconds, run ID 32315242601 — no runner ever ran).

Root cause: main CI went red after PR #5008 merged (~2026-08-19T23:53 UTC). Until that regression is identified and fixed on main, re-triggering CI here will keep producing the same phantom failures.

To unblock:

1. Find what broke on main after feat(orchestration): workflows + sub-agents fully captured per session — context, replies, live status #5008 merged (check the CI run on the merge commit)
2. Fix main → once main CI is green, re-trigger this PR's CI

This PR itself (drift-bot ✅, no merge conflicts) is ready to merge once the main CI regression is resolved.

---

Generated by Claude Code

[8090-software-factory]

✅ Drift Bot (ClawMetry): no drift detected

Drift Bot analyzed the changed files against this project's blueprints and requirements and found no drift.