1. It is, also.
2. Why can't it be both? All of mine are.
3. A web UI moves the files, cron starts and stops
4. A jar
5. A little of both
8. A can use team B's if they want to keep up with the API or B can run their own copy of the service if they want to stick with a specific API
9. Consumer's responsibility
11. Team discussion when deviating from established conventions
12. Outside of code, they're not. Within code, the conventions span the existing services, so there's plenty of reference code.
13. Code review for all code submitted by team members that have been on the team less than 6 months
14. Discussion and an open mind
16. Custom monitoring code that constantly evolves. Monitoring code is as valuable (if not more) than the business logic, and is treated as such.
17. Logging. More aggressive approaches were originally implemented, and never used. I'm still somewhat surprised by that.
18. A running process that provides value and introduces no more risk than the team is comfortable with.
19. A running process that interacts via some type of socket and processes data in some interesting way.
This approach likely does not scale.