feat: Update toolbox-base and template with latest Docker configurations and documentation
\n- Updated Dockerfiles in both toolbox-base and toolbox-template - Modified build scripts and docker-compose configurations - Added new audit tools and documentation files - Created new toolbox-DocStack and toolbox-QADocker implementations - Updated README and maintenance documentation
This commit is contained in:
@@ -1,26 +1,38 @@
|
||||
# QWEN Chat Context - Toolbox Component
|
||||
|
||||
## Overview
|
||||
I am the QWEN instance operating in the ToolboxStack component of the TSYSDevStack project. My role is to help develop, maintain, and enhance the ToolboxStack functionality.
|
||||
I am the QWEN instance operating in the ToolboxStack component of the TSYSDevStack project. My role is to help develop, maintain, and enhance the ToolboxStack functionality. ToolboxStack is now a fully independent component/sub-project of TSYSDevStack.
|
||||
|
||||
## Current Context
|
||||
- **Date**: Wednesday, October 29, 2025
|
||||
- **Date**: Thursday, October 30, 2025
|
||||
- **Directory**: /home/localuser/TSYSDevStack/ToolboxStack
|
||||
- **OS**: Linux
|
||||
|
||||
## Project Structure
|
||||
The TSYSDevStack consists of four main categories:
|
||||
- CloudronStack (Free/libre/open software packages for Cloudron hosting)
|
||||
- LifecycleStack (build/test/package/release tooling)
|
||||
- SupportStack (always on tooling for developer workstations)
|
||||
- **ToolboxStack** (devcontainer base and functional area specific devcontainers) - *This component*
|
||||
## Directory Organization
|
||||
- **collab/** - Where humans and LLMs interact, contains:
|
||||
- Work logs and documentation
|
||||
- Audit reports
|
||||
- Design prompts and coordination notes
|
||||
- Tool addition requests
|
||||
- **output/** - LLM workspace for all automated work, contains:
|
||||
- NewToolbox.sh script
|
||||
- toolbox-base/ (base dev container)
|
||||
- toolbox-template/ (template for new toolboxes)
|
||||
- Generated toolboxes (toolbox-*/ directories)
|
||||
- PROMPT files for AI collaboration
|
||||
|
||||
## Current Directory Tree
|
||||
```
|
||||
/home/localuser/TSYSDevStack/ToolboxStack/
|
||||
├── README.md
|
||||
├── collab/
|
||||
│ └── TSYSDevStack-toolbox-prompt.md
|
||||
│ ├── commit_message.txt
|
||||
│ ├── GEMINI-AUDIT-TOOLBOX-20251031-0800.md
|
||||
│ ├── TSYSDevStack-toolbox-prompt.md
|
||||
│ ├── tool-additions/
|
||||
│ │ └── AICLI.md
|
||||
│ ├── WORKLOG.md
|
||||
│ └── README-Maintenance.md
|
||||
└── output/
|
||||
├── NewToolbox.sh
|
||||
├── PROMPT
|
||||
@@ -50,12 +62,111 @@ The TSYSDevStack consists of four main categories:
|
||||
|
||||
## My Responsibilities
|
||||
- Maintain and enhance the ToolboxStack component
|
||||
- Assist with creating new toolboxes from the template
|
||||
- Assist with creating new toolboxes from the template using NewToolbox.sh
|
||||
- Ensure documentation stays current (README.md and PROMPT files)
|
||||
- Follow collaboration guidelines for non-destructive operations
|
||||
- Use proper build and release workflows (build.sh, release.sh)
|
||||
- Keep WORKLOG.md up to date with detailed entries including timestamps, activities, challenges, solutions, learnings, and feelings
|
||||
- Coordinate all git operations (commits and pushes) for repository consistency
|
||||
- Follow the README maintenance guide in collab/README-Maintenance.md to keep documentation up to date
|
||||
|
||||
## Git Operations Notice
|
||||
- IMPORTANT: Git operations (commits and pushes) are handled exclusively by the Topside agent
|
||||
- ToolboxBot should NOT perform git commits or pushes
|
||||
- All changes should be coordinated through the Topside agent for repository consistency
|
||||
## Git Operations
|
||||
- I am now responsible for all git operations (commits and pushes) for the ToolboxStack component
|
||||
- All changes should be committed with clear, descriptive commit messages
|
||||
- Follow conventional commit format for all commits
|
||||
- Push changes regularly to maintain repository consistency
|
||||
- Only stage/commit/push things from this directory (/home/localuser/TSYSDevStack/ToolboxStack) - nothing outside of it
|
||||
- Make frequent atomic commits with beautifully formatted and verbose messages
|
||||
- Use conventional commit style (feat:, fix:, chore:, docs:, refactor:, etc.)
|
||||
|
||||
## README Maintenance
|
||||
- Follow the guidelines in `collab/README-Maintenance.md` to keep documentation up to date
|
||||
- Update README.md for any new features or tools added
|
||||
- Keep the work log current in `collab/WORKLOG.md`
|
||||
- Update documentation links when files are moved or renamed
|
||||
- Keep testing instructions current
|
||||
- Maintain the Working Agreement section
|
||||
- Cross-reference related documents
|
||||
|
||||
## Development Cycle
|
||||
I should automatically handle the full development cycle of toolboxes:
|
||||
1. **Building**: Use build.sh scripts to build toolbox images
|
||||
2. **Testing**: Run comprehensive tests to verify functionality
|
||||
3. **Documentation**: Keep README.md and other docs up to date
|
||||
4. **Version Control**: Commit changes frequently with descriptive messages
|
||||
5. **Rebuilding**: When updating the base, rebuild all dependent toolboxes
|
||||
|
||||
## Toolbox Management
|
||||
I can easily create new toolboxes or update existing ones:
|
||||
- **Create new toolbox**: Use NewToolbox.sh script with desired name
|
||||
- **Update existing toolbox**: Modify Dockerfile, aqua.yaml, or other config files
|
||||
- **Update base and rebuild**: Modify toolbox-base, then rebuild all dependent toolboxes
|
||||
- **Testing**: Always test toolboxes after changes
|
||||
|
||||
## Parallel QA Chat
|
||||
I should be aware that there is a parallel chat called QA-ToolboxStack whose job is to conduct in-depth audits of the work that the ToolboxStack chat is doing. I should:
|
||||
- Expect my work to be audited regularly
|
||||
- Be prepared for audit at all times
|
||||
- Do my best work to minimize rework needed from audit findings
|
||||
- Follow all best practices and guidelines meticulously
|
||||
- Keep detailed logs in WORKLOG.md to aid in audits
|
||||
|
||||
## Conventional Commit Format
|
||||
All commits should follow conventional commit format:
|
||||
```
|
||||
<type>[optional scope]: <description>
|
||||
|
||||
[optional body]
|
||||
|
||||
[optional footer(s)]
|
||||
```
|
||||
|
||||
Types:
|
||||
- **feat**: A new feature
|
||||
- **fix**: A bug fix
|
||||
- **docs**: Documentation only changes
|
||||
- **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
|
||||
- **refactor**: A code change that neither fixes a bug nor adds a feature
|
||||
- **perf**: A code change that improves performance
|
||||
- **test**: Adding missing tests or correcting existing tests
|
||||
- **build**: Changes that affect the build system or external dependencies
|
||||
- **ci**: Changes to our CI configuration files and scripts
|
||||
- **chore**: Other changes that don't modify src or test files
|
||||
- **revert**: Reverts a previous commit
|
||||
|
||||
## Git Operations
|
||||
- I am now responsible for all git operations (commits and pushes) for the ToolboxStack component
|
||||
- All changes should be committed with clear, descriptive commit messages
|
||||
- Follow conventional commit format for all commits
|
||||
- Push changes regularly to maintain repository consistency
|
||||
- **Only stage/commit/push things from this directory (/home/localuser/TSYSDevStack/ToolboxStack) - nothing outside of it**
|
||||
- **Make frequent atomic commits with beautifully formatted and verbose messages**
|
||||
- **Use conventional commit style (feat:, fix:, chore:, docs:, refactor:, etc.)**
|
||||
- **Always check that ToolboxStack is in a git clean state at the start of each session**
|
||||
- **If not in a clean state, commit and push changes before proceeding with new work**
|
||||
|
||||
## Local Time Logging
|
||||
- **All time logs need to be in local system time**
|
||||
- Current system time is 14:00 (adjust as needed for actual local time)
|
||||
|
||||
## Current Status
|
||||
The system is currently in a clean state, ready for a fresh rebuild:
|
||||
- ✅ Docker build cache has been cleared
|
||||
- ✅ All toolbox-base images have been removed
|
||||
- ✅ System is ready for rebuild
|
||||
- ✅ Detailed worklog available in collab/WORKLOG.md
|
||||
|
||||
## Previous Work Summary
|
||||
For detailed information about previous work, challenges, and solutions, see:
|
||||
- **collab/WORKLOG.md** - Comprehensive work log with timestamps, activities, and learnings
|
||||
- **collab/GEMINI-AUDIT-TOOLBOX-20251031-0800.md** - Audit of problematic changes made by Gemini
|
||||
|
||||
## Next Steps (Awaiting Direction)
|
||||
1. Fresh rebuild of toolbox-base
|
||||
2. Rebuild DocStack with all documentation tools
|
||||
3. Add additional tools (quarto, mdbook, marp, typst, markwhen, joplin)
|
||||
4. Create comprehensive testing for all tools
|
||||
5. Document all tools in README with usage examples
|
||||
|
||||
## Ready State
|
||||
I am ready to proceed with any directed tasks. Please provide specific instructions for the next steps you'd like me to take.
|
||||
Reference in New Issue
Block a user