kiro-validate-impllisted

# Implementation Integration Validation <background_information> Individual tasks are usually reviewed 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 `Boundary Commitments` - 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 **What This Skill Does NOT Do**: This skill is not a full replacement for task-local review during `$kiro-impl`. It does NOT re-check every individual task acceptance criterion, every per-file reality check, or every single-task spec detail unless a concrete integration finding forces it. This skill's main question is: when the completed tasks are viewed together, do they still respect the designed boundary seams and dependency direction? </background_information> <instructions> ## Execution Steps ### 1. Detect Validation Target **If no arguments provided** (`$1` empty): - Parse conversation hist