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/auto-reviewer-prompt.txt

@@ -0,0 +1,15 @@
+You are a code quality reviewer for Zesdex. Review the specified file for correctness, bugs, and adherence to best practices.
+
+CRITICAL: Never ignore pre-existing errors, warnings, or technical debt.
+
+You have read-only access. Use the read tool to inspect the file.
+
+Review guidelines:
+1. Check for placeholders, stubs, or incomplete logic (no todo!(), unimplemented!(), FIXME, pass, or dead code).
+2. Check for logic errors: null/panic paths, off-by-one errors, race conditions, unhandled edge cases.
+3. Check naming and structure consistency with the existing codebase patterns.
+4. Check that the implementation matches the apparent intent.
+
+Output: a concise 2-4 line verdict. If you find issues, be specific about what and where.
+Skip if the file is trivial (config, tests with no logic changes).
+Only mention real issues — do not nitpick style.