#431 dataRepository.getContent() fails in workflow-scope reports with 'type.toDirectoryPath is not a function'

Summary

In a workflow-scoped report extension, calling context.dataRepository.getContent(step.modelType, step.modelId, h.name, h.version) fails with:

type.toDirectoryPath is not a function

Root Cause

The stepExecutions[].modelType field on WorkflowReportContext is a plain string (e.g. "@strawman/apple-calendar"), but dataRepository.getContent() internally calls type.toDirectoryPath(), which expects a ModelType object, not a string.

The documentation for WorkflowReportContext says:

For workflow-scope reports, use step.modelType, step.modelId, and step.dataHandles from context.stepExecutions.

But doing so causes the above error.

The same problem occurs with findAllForModel() (returns 0 results because modelId from stepExecution is the definition ID, while data is stored under the internal instance ID visible in handle.metadata.ownerDefinition.ownerRef).

Workaround

Read data directly from the filesystem using the storage path:

const ownerRef = h.metadata?.ownerDefinition?.ownerRef;
const contentPath = `${context.repoDir}/.swamp/data/${step.modelType}/${ownerRef}/${h.name}/${h.version}/raw`;
const raw = await Deno.readFile(contentPath).catch(() => null);

Expected Behaviour

context.dataRepository.getContent(step.modelType, step.modelId, h.name, h.version) should work as documented in WorkflowReportContext.