converge-developmentlisted

# Converge Development — observe-diagnose-fix the framework itself ## Purpose Use a real example playbook as a test bed. Run it. Watch what the framework does internally — not just the stdout event stream, but the target directory, runstate, and per-attempt forensics the runner writes to disk. When the framework misbehaves (crashes, corrupts state, fails to retry, mishandles a provider response), trace the symptom to the package and module responsible, patch `packages/**` source, rebuild, and re-run the example to verify. This skill is **only** for changes to framework source under `packages/` or for running framework-improvement playbooks that target `packages/`. It is the framework-developer counterpart to `converge-control` (which babysits a *user's* playbook and treats the framework as a black box). ## Two modes - **Interactive:** reproduce a named framework bug, patch `packages/**`, rebuild, verify. - **Autonomous:** run `self-improvement-loop` for bounded framework hardening, then use its artifacts as the evidence trail. ## When to invoke Trigger on user requests like: - "Debug converge using <example>" / "Use this example to find bugs in the framework" - "Why does the DAG runner <do X>?" / "Why is the execution <doing Y>?" - "Fix the framework — <symptom>" / "There's a bug in the manifest/mode/dispatcher/CLI" - "Improve <subsystem>" / "Add a feature to the CLI" / "Refactor a DAG action" - "Run the self-improvement loop" / "Autonomously improve the framework" -