Align Deep Scan worker draft guidance with the MCP input schema

[soyeon-oai]

Deep Scan workers construct draft payloads using persisted-artifact fields such as scope.includePaths, scope.excludePaths, coverage.scanId, coverage.mode, and coverage.inventoryStrategy. The MCP tool rejects these fields, requiring the worker to retry before it can save progress.

Reproduction: run a Deep Scan against a small repository and inspect the first record_codex_security_scan_draft invocation.

Expected: worker instructions and examples produce a valid semantic draft on the first attempt.

[su-jin1425]

Hi, I’d like to work on this issue. I’ll review the Deep Scan worker guidance and MCP schema, identify the invalid draft fields, and update the guidance/examples with regression coverage. I’ll share my plan ASAP. Please confirm before I start investigating and implementing a fix.