merge: align dev branch with main

AGENTS.md

@@ -4,10 +4,6 @@
 
 OpenSpec is the source of truth. Superpowers is the default workflow. Keep changes small, scoped, and verified.
 
-## Communication
-
-All agent output, code comments, commit messages, documentation, and artifacts must be in **English** unless the user explicitly requests another language.
-
 ## Priority order
 
 1. Current user instruction
@@ -75,7 +71,6 @@ Do not:
 * Introduce new dependencies without clear justification.
 * Treat existing code as more authoritative than OpenSpec for intended behavior.
 * Decide product behavior silently when the spec is unclear.
-* Run `docker compose` commands (build, up, down, etc.) without explicit user approval and proper isolation (e.g., feature branches, separate worktrees, or staged rollouts). Docker Compose operations are deployment-level changes that can affect running services, shared volumes, and network state. Always ask first.
 
 If scope must change, propose an OpenSpec update first.
 
@@ -92,31 +87,6 @@ Do not claim completion without verification evidence.
 
 ## Git workflow
 
-### Branching strategy
-
-For every spec change or new functionality:
-
-1. Create a new branch from `dev` with a proper prefix:
-   - `feat/` for new features (e.g., `feat/tool-workshop`)
-   - `fix/` for bug fixes (e.g., `fix/terminal-tty`)
-   - `refactor/` for refactors (e.g., `refactor/api-cleanup`)
-   - `docs/` for documentation (e.g., `docs/api-guide`)
-   - `chore/` for maintenance (e.g., `chore/update-deps`)
-2. Branch name should reference the OpenSpec change name when applicable.
-3. Do not commit directly to `main` or `dev`.
-
-### Completion and merge
-
-When implementation is complete and verified:
-
-1. Ensure all tests pass and quality gates are met.
-2. Stage all changes with `git add -A`.
-3. Create a commit with a proper conventional commit message (see below).
-4. Switch to `dev`: `git checkout dev`.
-5. Merge the feature branch: `git merge --no-ff <branch-name>`.
-6. Push to remote: `git push origin dev`.
-7. Delete the local feature branch if desired: `git branch -d <branch-name>`.
-
 ### Auto-commit on spec completion
 
 When an OpenSpec change is fully implemented and all tasks are complete: