feat(docs): standardize README.md files across all stacks

- Update top-level README.md with AI collaboration section and working agreement
- Standardize all stack README.md files (CloudronStack, LifecycleStack, SupportStack, ToolboxStack) with consistent structure:
  - Add Working Agreement section with consistent items across all stacks
  - Add AI Agent section identifying the responsible bot for each stack
  - Add License section with reference to main LICENSE file
  - Add Quick Start section where missing
- Create missing LifecycleStack/collab directory with .gitkeep file
- Add top-level QWEN.md file for tracking Topside agent work
- Add top-level commit-template.txt and configure git to use it
- Ensure consistent formatting and content across all documentation
- Fix CloudronStack README title to match project structure

This commit ensures all README files follow the same structure and
contain necessary information for coordination between different
Qwen agents working on each stack.

README.md

@@ -37,10 +37,21 @@
 
 ---
 
+## 🤖 AI Collaboration
+This project uses Qwen AI agents for development and maintenance:
+- **Topside**: Manages top-level README.md and directory structure
+- **CloudronBot**: Handles CloudronStack documentation and packaging
+- **LifecycleBot**: Manages LifecycleStack workflows
+- **SupportBot**: Maintains SupportStack operations
+- **ToolboxBot**: Handles ToolboxStack workspace management
+
+---
+
 ## 🧭 Working Agreement
 - **Stacks stay in sync.** When you add or modify automation, update both the relevant stack README and any linked prompts/docs.
 - **Collab vs Output.** Use `collab/` for planning and prompts, keep runnable artifacts under `output/`.
 - **Document forward.** New workflows should land alongside tests and a short entry in the appropriate README table.
+- **AI Agent Coordination.** Use Qwen agents for documentation updates, code changes, and maintaining consistency across stacks.
 
 ---