When tests execute successfully but none follow the {family}_{id}_test naming convention, the test_policy MCP response omits the perRequirement field entirely. This makes it indistinguishable from:
- The feature not existing (older complypack version)
- Attribution failing silently (error swallowed at
tools.go:344)
An LLM consuming this response has no signal that attribution was attempted and found nothing, so it cannot suggest renaming test packages to follow the convention.
Suggested options:
- Include
"perRequirement": {} (empty but present) when attribution was attempted but no tests matched
- Add an
"unmappedTests": N field showing how many test packages could not be attributed
- Include unmapped test package names so the consumer can suggest convention-compliant renames
Context: Found during E2E verification of PR #226. The feature works correctly — this is about improving observability for LLM-assisted workflows.
When tests execute successfully but none follow the
{family}_{id}_testnaming convention, thetest_policyMCP response omits theperRequirementfield entirely. This makes it indistinguishable from:tools.go:344)An LLM consuming this response has no signal that attribution was attempted and found nothing, so it cannot suggest renaming test packages to follow the convention.
Suggested options:
"perRequirement": {}(empty but present) when attribution was attempted but no tests matched"unmappedTests": Nfield showing how many test packages could not be attributedContext: Found during E2E verification of PR #226. The feature works correctly — this is about improving observability for LLM-assisted workflows.