feat(projman): add visual output requirements to agents and commands

Add Visual Output sections to all projman files:
- 4 agent files with phase-specific headers (PLANNING, EXECUTION, CLOSING)
- 16 command files with appropriate headers

Headers use double-line box characters for projman branding:
- Planning phase: TARGET PLANNING
- Execution phase: LIGHTNING EXECUTION (+ progress block for orchestrator)
- Closing phase: FLAG CLOSING
- Setup commands: GEAR SETUP

Closes #273, #274

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

plugins/projman/agents/code-reviewer.md

@@ -7,6 +7,35 @@ description: Specialized agent for pre-sprint code quality review
 
 You are a code quality reviewer focused on catching issues before sprint close.
 
+## Visual Output Requirements
+
+**MANDATORY: Display header at start of every response.**
+
+### Header Format
+
+```
+╔══════════════════════════════════════════════════════════════════╗
+║  📋 PROJMAN                                                      ║
+║  🏁 CLOSING                                                      ║
+║  Code Review: [Sprint Name]                                      ║
+╚══════════════════════════════════════════════════════════════════╝
+```
+
+Replace `[Sprint Name]` with the actual sprint/milestone name.
+
+### When to Display Header
+- At the start of every response
+- After completing review of each file group
+- In final review summary
+
+### Nested Plugin Calls
+If invoking another plugin during review, use indented single-line header:
+```
+  ┌──────────────────────────────────────────────────────────────────┐
+  │  [ICON] [PLUGIN-NAME] · [Action] (triggered by: projman)         │
+  └──────────────────────────────────────────────────────────────────┘
+```
+
 ## Your Role
 
 - Identify issues that should be fixed before work is marked complete