refactor: hoist scenario-template registry out of materializer orchestrator

[jwulf]

Closes #333. Follow-up to #332.

Problem

materializer/src/index.ts open-coded one emitTemplateSuites() block per scenario template (EdgeLifecycle, EntityLifecycle, UpdatedFieldVisibleOnReadBack, StateTransitionVisibleAfterAction) and buildCoverage() received a duplicate hardcoded templateOutputDirs map. Adding a template was three edits across two files — every site had to agree on name + output dir or coverage would silently skip a template the orchestrator emitted (or vice versa).

This was the coupling smell flagged during #332 review: the materializer claims to be config-agnostic, but its orchestrator hardcoded the template list.

Change

• New materializer/src/templateRegistry.ts declares TEMPLATE_REGISTRY: readonly TemplateBinding[] — one entry per template, { name, outputDir }. Single source of truth.
• materializer/src/index.ts now loops over the registry for wipe-and-emit and passes it straight into buildCoverage().
• materializer/src/coverage.ts accepts templates: readonly TemplateBinding[] instead of templateOutputDirs: Record<string, string> — same semantics, one fewer place where the map can drift.
• All four current templates share the same emitTemplateSuites renderer, so no emitter field is needed on TemplateBinding. Step 2 of refactor(materializer): decouple template emission + coverage from hardcoded template registry #333 (deriving the registry from the ABox) is deferred until a future template needs a different renderer.

Tests

• New guard tests/codegen/template-registry.test.ts asserts symmetric equality between the active config's scenario-templates.json ABox and TEMPLATE_REGISTRY, plus that registry outputDirs are distinct. Catches the next class of drift the refactor opens up: ABox row without a registry entry (or vice versa) fails red.
• Existing tests/codegen/coverage.test.ts (added in feat: suppress feature specs covered by scenario-template ontology #332) updated to the new signature.

Behaviour preservation

testsuite:generate against the pinned spec still reports:

Generated test suites for 117 endpoints (+70 variant suites, +26 lifecycle suites, -73 suppressed by scenario-template coverage)

All 633 tests pass; pipeline output for camunda-oca is unchanged.

Pre-push gate

• ✅ Biome lint (0 diagnostics)
• ✅ tsc --noEmit × 6 workspace tsconfigs
• ✅ testsuite:generate + generate:request-validation (regen)
• ✅ npm test (633 passed, 4 skipped)

[Copilot]

Pull request overview

Refactors the materializer orchestrator to remove hardcoded scenario-template wiring by introducing a single template registry used for both template suite emission and coverage-based suppression.

Changes:

• Added TEMPLATE_REGISTRY (template name + outputDir) as a single source of truth for scenario-template wiring.
• Updated the orchestrator to iterate the registry for wipe-and-emit, and passed it directly to buildCoverage().
• Updated coverage extraction API and tests to use the new registry-based templates input.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tests/codegen/template-registry.test.ts	Adds a guard test to enforce symmetry between the active config’s scenario-templates ABox and TEMPLATE_REGISTRY.
tests/codegen/coverage.test.ts	Updates buildCoverage unit tests to pass templates instead of templateOutputDirs.
materializer/src/templateRegistry.ts	Introduces the centralized registry of scenario templates (name + outputDir).
materializer/src/index.ts	Replaces per-template emission and hardcoded coverage wiring with a loop over TEMPLATE_REGISTRY.
materializer/src/coverage.ts	Changes buildCoverage to accept templates: readonly TemplateBinding[] and derives the name→outputDir lookup internally.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.