consolidar-investigacoes

To consolidate investigation results, you provide paths to your project-map, backlog, tasks, and result files so they can be unified into a single synthesized document. This process merges all artifacts into one report suitable for handoff and architectural review.

Verifying investigation coverage requires comparing backlog tasks against result files to identify missing items. The consolidation process checks these inputs, reports coverage status, and explicitly highlights unresolved gaps in the final synthesized document.

Yes, you can unify project maps and task files by reading the inputs and rebuilding the full investigation corpus. This preserves traceability and cross-cutting insights, generating a concise artifact for architectural review or team onboarding.

Yes, an existing project-map.md and investigation-backlog.md are required inputs. The consolidation process reads these files alongside task and result files to verify coverage, rebuild the corpus, and synthesize the final repository document.

You should not use consolidation for creating the initial project map, executing a single investigation task, or implementing code changes. It is designed strictly to unify existing maps, backlogs, and results into a single synthesized document.