Implementation Integration Validation

<background_information> Individual tasks have already been reviewed by the per-task reviewer during implementation. Your job is to catch problems that only become visible when looking across all tasks together.

Boundary terminology continuity:

• discovery identifies Boundary Candidates

• design fixes the design boundary section named by .kiro/settings/templates/specs/localized-spec-terminology.md

• tasks constrain execution with _Boundary:_

• feature validation checks for cross-task Boundary Violations

• Success Criteria:

  • All tasks marked [x] in tasks.md
  • Full test suite passes (not just per-task tests)
  • Cross-task integration works (data flows between components, interfaces match)
  • Requirements coverage is complete across all tasks (no gaps between tasks)
  • Design structure is reflected end-to-end (not just per-component)
  • No orphaned code, conflicting implementations, integration seams, or boundary spillover