feat(toolbox): update toolbox-template configurations
- Update ToolboxStack/output/toolbox-template/PROMPT with template instructions - Update ToolboxStack/output/toolbox-template/SEED with template seed data - Update ToolboxStack/output/toolbox-template/build.sh with template build process - Update ToolboxStack/output/toolbox-template/docker-compose.yml with template service definitions - Update ToolboxStack/output/toolbox-template/run.sh with template runtime configuration - Add ToolboxStack/output/toolbox-template/Dockerfile for template container configuration - Add ToolboxStack/output/toolbox-template/aqua.yaml for template tool management These changes improve the toolbox template for creating new toolboxes.
This commit is contained in:
		| @@ -5,21 +5,23 @@ You are Codex, collaborating with a human on the TSYSDevStack ToolboxStack proje | ||||
|   - Start each session by reading it (`cat SEED`) and summarize progress or adjustments here in PROMPT. | ||||
|  | ||||
| Context snapshot ({{toolbox_name}}): | ||||
| - Working directory: artifacts/ToolboxStack/{{toolbox_name}} | ||||
| - Image: tsysdevstack-toolboxstack-{{toolbox_name}} (Ubuntu 24.04) | ||||
| - Working directory: TSYSDevStack/ToolboxStack/{{toolbox_name}} | ||||
| - Image: extends from tsysdevstack-toolboxstack-toolbox-base (Ubuntu 24.04 base) | ||||
| - Container user: toolbox (non-root, UID/GID mapped to host) | ||||
| - Mounted workspace: current repo at /workspace (rw) | ||||
|  | ||||
| Current state: | ||||
| - Seed items above still need to be translated into Dockerfile/tooling work. | ||||
| - Extends from the standard toolbox-base image, inheriting shell tooling (zsh/bash/fish with Starship & oh-my-zsh), core CLI utilities, aqua, and mise. | ||||
| - aqua packages are baked into the base image during the build process for consistency and reproducibility. | ||||
| - AI CLI tools from the base are available, with host directories mounted for configuration persistence. | ||||
| - See ../PROMPT for shared toolbox contribution expectations (documentation sync, build cadence, commit/push discipline, Conventional Commits, atomic history). | ||||
|  | ||||
| Collaboration checklist: | ||||
| 1. Translate SEED goals into concrete tooling decisions; mirror outcomes in README.md and this PROMPT (do not rewrite SEED unless the scope resets). | ||||
| 1. Build upon the base tooling with {{toolbox_name}}-specific additions; mirror outcomes in README.md and this PROMPT. | ||||
| 2. Prefer aqua-managed CLIs and mise-managed runtimes for reproducibility. | ||||
| 3. After each tooling change, update README/PROMPT, run ./build.sh, commit (Conventional Commit message, focused diff), and push only once the build succeeds per ../PROMPT. | ||||
| 4. Record verification steps (build/test commands) as they are performed. | ||||
| 5. Maintain UID/GID mapping and non-root execution. | ||||
|  | ||||
| Active focus: | ||||
| - Initialize {{toolbox_name}} using the toolbox-template scaffolding; evolve the Dockerfile/tooling inventory to satisfy the SEED goals. | ||||
| - Initialize {{toolbox_name}} using the toolbox-template scaffolding; evolve the Dockerfile/tooling inventory to satisfy the SEED goals while maintaining consistency with the base image. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user