@opovid/spec

Optional use-case authoring and compilation support for Opovid.

Compiled scenario tasks carry use-case, scenario, example, step, and resolver metadata into user.timeline(). That makes the debugging-first timeline reports explain both the executable task and the source scenario step. See ../../../docs/execution-timeline.md for the reporting model.

Install

npm install @opovid/spec @opovid/core

Use

import {
  autoRegister,
  compileUseCase,
  compileUseCaseScenario,
  createRegistry,
  questionBinding,
  registerInto,
  scenario,
  step,
  taskBinding,
  useCase,
  validateUseCase,
} from "@opovid/spec";

Preferred flow:

1. Start with direct User tests.
2. Add spec only when scenario prose and gap reporting are useful.
3. Prefer auto-registered bindings over hand-built registries when your domain modules can expose them.

The root README and docs/tdd-support.md explain the intended workflow in detail.

Use validateUseCase(...) for a dry run when you want missing registry entries to fail fast at suite startup.

Use compileUseCaseScenario(...) when you want to run one named scenario from a larger UseCaseSpec without compiling the rest.