Integration fixes to make workflow.py available in user projects:
1. Bundle automation/ directory in installer
- Add automation/ to build_installer.py copy process
- Ensures workflow.py is available in generated projects
- Pre-commit hook can now actually call workflow.py
2. Update pre-commit hook comment
- Change from "planned feature...does not yet exist"
- Update to "provides non-blocking vote status reporting"
- Accurately describes current implementation
Verified:
- automation/workflow.py present in install bundle
- workflow.py executes successfully from bundle
- Pre-commit hook comment matches reality
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Major documentation improvements:
1. Add CLAUDE.md
- Comprehensive guide for AI assistants working in this repo
- Repository architecture and directory structure
- Common development commands and workflows
- Build system explanation
- Key concepts and design philosophy
2. Restructure DESIGN.md
- Clarify three directory contexts: CascadingDev Repo, Install Bundle, User Project
- Add clear section headers and visual separation
- Mark future/unimplemented features with 🚧 emoji
- Document undocumented wins: META system and Ramble providers
- Add comprehensive Ramble documentation (mock and claude providers)
- Document template META system with code examples
3. Fix setup_project.py
- Correct error message path (was scripts/hooks/pre-commit, now assets/hooks/pre-commit)
These changes address confusion between tooling source, distribution bundle, and
generated user projects while highlighting sophisticated features like the
self-describing template system and multi-provider Ramble GUI.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
rob