feat: add handover documentation

[leoneperdigao]

Add new feature:

Project Handover Documentation (New!)

• 📁 Multi-Video Processing: Process entire directories of meeting recordings
• 👔 Executive Summary: Business-focused handover for stakeholders
• ⚙️ Technical Summary: Detailed technical documentation for engineers
• 📈 Visual Diagrams: Auto-generated Mermaid diagrams including:
  • Project timeline with milestones
  • System architecture and components
  • Team roles and responsibilities
  • Decision flow charts
• 🎨 Interactive HTML Report: Beautiful, searchable documentation with:
  • Side-by-side executive and technical views
  • Collapsible sections
  • Responsive design
  • Print-friendly styling
• 📝 Markdown Export: Separate markdown files for each persona
• 🔍 Intelligent Analysis: Cross-video analysis to identify:
  • Project themes and context
  • Key people and their roles
  • Technical components and relationships
  • Important decisions and risks

To fix the problem, we should remove the redundant assignment to the variable handover_pipeline on line 70 in examples.py. Since the value assigned there is immediately overwritten before any usage, it serves no purpose and can be safely deleted. We should only remove the assignment statement on line 70, leaving surrounding comments and code untouched to maintain the context of the examples and avoid any change in functionality or documentation.

To fix the "unused local variable" warning, rename the variable handover_pipeline on line 90 to a name that clearly indicates it is intentionally unused. CodeQL recommends names with unused in them (such as unused_handover_pipeline). This preserves the assignment (which may have side effects if the constructor does), but makes it clear to readers and static analysis tools that the variable is unused on purpose—likely for illustrative, documentation, or example purposes. Only change line 90 in the file examples.py as that's the assignment flagged; do not modify other places unless the variable is referenced elsewhere (it's not here).

---

To address this issue in the most straightforward way without altering existing functionality, we should remove the assignment to fast_pipeline on line 105 entirely. If future users want to follow the example, they can uncomment the sample code below as needed. There is no need to keep the assignment in the source, as there are no side effects or documentation purposes tied to it.

Edit the examples.py file:

• Delete the line fast_pipeline = HandoverPipeline(settings=parallel_settings) on line 105.
• No imports, method signatures, or additional definitions need to be changed; only this line is affected.

To fix the unused local variable, either remove the assignment to verbose_pipeline if it's not needed or, if it's provided for illustrative/sample purposes, rename the variable to an accepted unused variable format (e.g., _ or unused_verbose_pipeline). In this context, since its only purpose is demonstrative and actual use is commented out, the clearest fix is to rename it to indicate it's deliberately unused: change verbose_pipeline to _, showing it's an intentionally ignored variable. This is a minimal change that preserves the example but eliminates the warning.

No additional imports or methods are needed; this is a straightforward renaming on line 151.

To fix this issue without changing existing functionality, we should rename the unused variable silent_pipeline on line 156 to something that explicitly indicates it is intentionally unused, such as unused_silent_pipeline. This follows the naming convention recommended in the background section and will silence linter/static analysis warnings while preserving the instructive nature of the example code. No additional imports, definitions, or method changes are required.

To fix this problem, we should remove the unused Set import from the import statement on line 7. We need to delete Set from from typing import List, Optional, Set in src/call2action/handover_pipeline.py, leaving only the used imports (List, Optional). This change is minimal and will not affect existing functionality.

The best way to fix the problem is to remove the unused import statement. Specifically, you should delete the line from datetime import datetime at line 4 in src/call2action/html_generator.py. No other changes, updates, or replacements are necessary, as no code references this import.

---

To fix the problem, we should remove the unused import from line 6: specifically, delete List from from typing import Dict, List. This change should be made in the file src/call2action/html_generator.py. Only Dict is used, so the import statement should be revised to from typing import Dict. No other code changes or new imports are needed for this fix.

To fix this problem, we should ensure Jinja2 is configured to autoescape for HTML templates. The recommended way is to use the Jinja2 Environment class and initialize it with autoescape=select_autoescape(['html', 'xml']), using FileSystemLoader (or possibly BaseLoader for string templates). Since the report template is read from disk (not a file in a conventional templates directory), we can either:

• Load the template using FileSystemLoader (if we know the template filename).
• Use Environment with BaseLoader and from_string() for directly loaded template content.

The best fix, requiring minimal change, is to replace Template(self.template) with:

from jinja2 import Environment, select_autoescape, BaseLoader

env = Environment(
    loader=BaseLoader(),
    autoescape=select_autoescape(['html', 'xml'])
)
template = env.from_string(self.template)

This ensures automatic escaping for HTML templates.

The checks and imports must be added.
Changes to make:

• Add missing imports (Environment, select_autoescape, BaseLoader).
• Replace the use of Template(self.template) with an Environment-based template creation as above.

---

To fix the issue, remove the unused import of Union from the typing module in src/call2action/models.py. Specifically, edit line 6 so that only the used type annotations (Dict, List, Optional, and Tuple) are imported. No changes to functionality will occur by this removal, and all required imports for current usage will remain intact.

---