test: add a consumer smoke test that exercises delivery, not code - #9

Stacked on #5 (both touch the workflows); retargets to main once that merges. Port of EFCore.ComplexIndexes' test/consumer-smoke-test.sh, adapted for a runtime library.

Why

Every layer of the suite references the projects directly. A ProjectReference hides exactly what breaks for a consumer of the package: a satellite whose nuspec fails to declare the core package, a version range that lets NuGet resolve a different core than the one built here, a type public in the project and missing from the package, a plugin that registers through a project reference and not through the assembly a consumer restores. Each packs cleanly and restores cleanly, and the first person to notice is a consumer.

What

test/consumer-smoke-test.sh packs the four packages, restores them into throwaway projects created outside the repository (inside it, Directory.Build.props would apply), compiles real code against them, runs it, and asserts on content — printed output and translated SQL — never on the exit code alone.

Two consumers:

• core only — parse → canonical literal, Intersect/Overlaps, JSON round trip through AddRangeConverters(), StringSet canonical form and membership.
• CodoMetis.ValueRanges.EFCore.PostgreSQL.NodaTime — pulls all four through the nuspec chain; the chain is asserted from dotnet list package --include-transitive (each id present, at this version). Then ToQueryString() (never connects) for a BCL range predicate ("Period" @> DATE '2024-06-15'), a NodaTime range predicate ("Stay" @> DATE …) and a value-set predicate ("Tags" @> ARRAY['x']::text[]) — translations that only exist if the plugins registered from the packaged assemblies.

Load-bearing and carried over from EFCore.ComplexIndexes, where each was learned the hard way: NUGET_PACKAGES redirected to a private folder (NuGet resolves id+version from the global cache before any source, so a locally built 6.2.0 is otherwise shadowed by whatever 6.2.0 was restored before — including nuget.org's); package source mapping in the generated nuget.config (this repo's ids from the local feed only, everything else from nuget.org — restricting the whole restore to the feed fails with NU1101).

Wired into both workflows in both invocation modes: a consumer job on every PR that packs its own feed, and a step in the pack job and in the release gate that is handed the pre-built dist — the artifacts published are the artifacts tested. The script builds before it packs, so it works with or without GeneratePackageOnBuild (#7 removes it).

Verified

• Passes locally in both modes (own feed; pre-built dist).
• verify-the-guard (delivery): sabotaging the mechanism — the NodaTime satellite no longer calling UseValueRanges() — fails the run.
• actionlint clean on both workflows.

CLAUDE.md gets a paragraph so the private-cache and source-mapping choices don't get "simplified" away.

🤖 Generated with Claude Code