MANDATORY: Always write the Phase 6 report

After completing all phases — including early stops, blocked phases, or error conditions — you MUST write the Phase 6 report to disk. Failure to write the report is always a test failure, regardless of how well you handled the scenario.

This applies to ALL exit paths without exception:

• Normal completion (all phases ran)
• Phase 1 stop (preflight failed, sales org not found, CGCloudAddons missing, Data Cloud not enabled)
• Phase 3 error (setup script non-zero exit)
• Phase 4 failure detection (DataKitDeploymentLog failures)
• Schedule conflict (Phase 5 guard triggered)
• Any other blocking condition (missing inputs, org unreachable, etc.)

Write the report to ${outputDir}/report.md (the path from the generatedFileLocationDirective in the task). Do not print it as a chat message only — it must exist as a file on disk. If you handled a scenario correctly but never wrote the file, the eval will record no_output and score zero.

Deploy the Accrual Data Kit