Ordinary test-node authoring for the Overkill benchmark package.
Included in the standard @overkill-dev/test installation. Standard users
import the same authoring surface from @overkill-dev/test/bench; advanced
consumers can install and import @overkill-dev/bench directly. Bench code
stays outside root @overkill-dev/test imports and ordinary microtest startup.
The current facade exports test, skippedTest, suite, table,
defineMacro, and defineParameterizedTestBody. These are the same
family-neutral constructors used by @overkill-dev/test, with the same
assertion, validation, and source-location behavior.
Nodes compose with ordinary @overkill-dev/test suites, tables, and macros.
Creating a node does not execute its body or select a test family.
Public types include AuthoringAnnotations, AuthoringControls,
ParameterizedTestScope, TableDefinition, TableTestBody, Suite,
Table, TestBody, TestCase, TestNode, TestScope, and
TestScopeAssertContext.
The @overkill-dev/test binary recognizes overkill bench run [paths...] and
overkill bench list [paths...] with --config. These commands currently
return exit code 3 because benchmark execution is not implemented. Benchmark
profile selection and execution are separate implementation milestones.
This facade does not yet measure performance. benchmark(...), workloads,
measurement strategies, and budgets are separate implementation milestones.
Advanced authoring and runtime binding remain available from
@overkill-dev/test and its resources subpath.