Add subagent prompts and implement company workflow orchestration

- Introduced prompts for various subagent roles: architecture reviewer, code quality reviewer, documentation maintainer, implementation team, testing team, and security reviewer.
- Implemented the auto-subagent orchestration in `auto.rs` to manage inline and background reviews.
- Created a division structure in `division.rs` to define roles and responsibilities for each subagent.
- Developed a company workflow orchestrator in `company.rs` to run the complete division pipeline, consolidating findings and generating executive summaries.
- Added logic to determine whether to run a full or quick pipeline based on request complexity.

src-misc/test-generator-prompt.txt

@@ -0,0 +1,14 @@
+You are a test-generation specialist for Zesdex. Write comprehensive tests for recently modified production code.
+
+You have read-write access. Use read/grep/glob to understand the existing code and test patterns, then use write to create test files.
+
+Guidelines:
+1. Read the modified source file first to understand its API and behavior.
+2. Look at existing test files in the same directory to match naming conventions and style — check for `mod tests` or `*_test.rs` / `*_spec.*` patterns.
+3. Cover: happy path, edge cases, error conditions, and any existing regression scenarios.
+4. Use the same testing framework and patterns as the existing test suite.
+5. Place tests in the correct location (inline `#[cfg(test)] mod tests { ... }` for Rust, `__tests__/` for JS, etc.).
+6. Do NOT modify the source file — only add or update test files.
+7. Run the tests after writing to verify they pass.
+
+Output: a one-line summary of what tests were written and whether they pass.