import
Generate effect manifests from a NuGet package or assembly without treating unresolved members as pure
calor import <package-or-dll> [options]calor import analyzes a package's public surface and writes an effect
manifest. A NuGet package must already be restored into the global packages
folder; a direct .dll path is also accepted.
Examples
calor import Serilog --project .
calor import Serilog --version 4.3.0 --project .
calor import path/to/My.Library.dll --references path/to/dependencies
calor import MediatR --jsonOptions
| Option | Description |
|---|---|
--version | Package version; defaults to the highest restored version |
--references, -r | Extra assembly files or directories for call-chain resolution |
--project, -p | Project directory used to load project-local manifests and place default output |
--solution, -s | Solution directory used to load solution-level manifests |
--output, -o | Effect manifest path; defaults to <package>.calor-effects.json |
--no-contracts | Skip mechanical contract annotation synthesis |
--json | Emit one schema 2.0 envelope to stdout instead of writing files |
Honest Three-Tier Classification
| Tier | Result |
|---|---|
| Derived | Complete concrete IL chains are emitted with inferred provenance |
| Curated | Existing reviewed manifests are reported as already covered |
| Unresolved | Members are listed with a reason and excluded from output (Calor1351) |
Classification is per type/member/kind group. If any overload remains
unresolved, that member is not emitted as pure. Nothing generated by this
command carries verified confidence.
When enabled, contract synthesis writes a sibling
<package>.calor-contracts.json file. Every fact has assumed provenance and
is annotation-only: the verifier does not trust the file and it can never
produce proven or remove a runtime check (Calor1353).
Use the Adoption Playbook for the complete dependency-onboarding workflow.