contracts/common.md#principled-implementation The package root is resolved through @nestia/sdk/package.json from the consumer's project, so the source path is the installed package's, not a workspace layout, and the descriptor returns only a name and a source directory.
contracts/common.md#clear-and-simple-design One function returning two properties; the transform itself is native.
contracts/common.md#prohibited-implementation-shortcuts The resolution goes through the package manifest, as the development rules require, and nothing is patched.
contracts/common.md#meaningful-documentation The comment states what the descriptor returns.
contracts/portability.md#os-neutral-implementation createRequire anchors package resolution to the consumer project's package.json; Node resolution yields the installed manifest's native pathname and path.dirname/path.resolve derive the contributor source without a workspace-specific separator or shell lookup.
@nestia/sdkttsc plugin descriptor.Points ttsc at this package's own Go source (
native/sdk, packagesdk). Because that package is notpackage main, ttsc classifies it as a linked transform and statically links it into the@nestia/corehost binary as a contributor — but only for projects that actually depend on@nestia/sdk. A project depending on@nestia/corealone never links, compiles, or ships any of this SDK transform code.