docs: add atomic_bomberman_lol example scaffold

[fazpu]

Summary

A worked example of a loopy-loop target project under examples/atomic_bomberman_lol/: a browser-playable multiplayer Atomic-Bomberman-inspired game with League-of-Legends-style QWER character abilities.

Config (loopy_loop_config.yaml)

• Real goal + slug (atomic-bomberman-lol)
• 9 concrete completion criteria (run command works, multiplayer interaction, grid/walls/pickups, bomb + chain explosion mechanics, 4+ characters with QWER kits and enforced cooldowns, authoritative game loop, test coverage, README, docs/characters.md kit spec)
• 4 stop criteria (unresolvable_error, paid-service-required, port-binding-infeasible, goal_check breakage cap)
• max_turns: 60, goal_check_consecutive_failures_cap: 3
• team_harness_agents: ["codex", "claude", "gemini"]
• Project-specific team_harness_system_prompt_extension documenting stack defaults + commit style + single-authoritative-state preference

Workflows (chained plan -> execute -> check rotation)

workflow	must_follow	role
planning	—	writes/updates PLAN.md only; never code
execution	planning	picks first [ ] task, implements + tests + commits, moves to ## Done
goal_check	execution	inspects repo against completion criteria and writes goal_check.json

Verified with

• loopy init generated the scaffold, loopy_loop_config.yaml then rewritten for the real project.
• loopy coordinator + POST /register dry-run returned action=run, workflow_id=planning, iteration=1 (confirms preflight + must_follow graph validates cleanly).
• loopy status and loopy stop exercised end-to-end. Dry-run state cleaned up before commit.

Test plan

• loopy coordinator boots against this config without preflight error
• First dispatch is planning
• Full loop run (requires authenticated codex/claude/gemini CLIs + OPENROUTER_API_KEY — left to follow-up)