Skill: Create Test Project

Build a minimal compiled test project whose annotated samples reproduce the flow a rule or approximation is checked against. The compiled model is the deliverable; its sources sit alongside it

Inputs

From the caller; if omitted, fall back to the default. Ask only when a required input is missing and has no sensible default

• What to test <spec> — a rule's requirements, or the package's methods to exercise
• Project root <project-root> — the real sources the requirements point into. Default: current directory
• Tracking file <tracking-file> — the rule or approximation file this test serves. Default: .opentaint/tracking/rules/lib/<name>.yaml or .opentaint/tracking/approximations/<name>.yaml
• Test project <test-project> — sources. Default: .opentaint/test-projects/<name> (a rule project holds a sinks/ and/or sources/ sub-project under it)
• Compiled output <test-compiled> — the model. Default: .opentaint/test-compiled/<name> (one model per sub-project: <name>/sinks, <name>/sources)
• Dependencies — exact Maven coordinates the samples need; default: the dependencies list in <tracking-file>; with no tracking file, derive them from the project's build.gradle/pom.xml

<name> is the package (<package-kebab>) for a rule, or the dataflow approximation unit (<package-kebab>-dataflow, e.g. reactor-core-publisher-dataflow) for an approximation; the two never share a folder

Workflow