Language: 中文 | English
- Confirm that the change fits CrewBee's Team-first direction.
- Keep changes focused and clearly scoped.
- Run type checks or build verification after changes.
- Keep documentation, contract models, and directory naming in sync to avoid framework drift.
- Team-related rules should be explicit and versionable.
- Prefer small, composable contract structures over large monolithic interfaces.
- Keep
src/corehost-agnostic; do not hard-code OpenCode-specific behavior there prematurely. - File-based Team templates live under
templates/teams/. During installation they are copied into the OpenCode config rootteams/directory and used as global Team sources. Runtime Team registrations come from both the globalcrewbee.jsonunder the OpenCode config root and the project.crewbee/crewbee.jsonunder the current worktree. Both sources must use the same loader / validator / projection / OpenCode config patch path; project sources gain priority only through higher source precedence. - Documentation under
docs/should have both Chinese and English versions for human understanding and project continuity.