Harden the public API, fix Invoke constant arguments, add Use.From

[holonsoftFounder]

Summary

• Argument validation over the public configuration and generation API: ArgumentNullException for null setups, types, expressions, providers, factories and evaluators; ArgumentOutOfRangeException for negative counts in List, Collection, First, Random, Next; ArgumentException with the offending name for unknown properties, fields and methods, non-source types in Use(Type) and non-convention types in Register(Type).
• All 22 bare throw new InvalidOperationException() carry a message with the type and member they failed at.
• Bug fix: Invoke(c => c.Method("literal")) in the configuration stored the ConstantExpression itself as the argument. Untested so far, only the generation-time Invoke compiled the lambda. Constants arrive as their value now, captured variables are evaluated once, null is allowed.
• Use.From(() => value) and Use.From(ctx => ...) as Invoke argument markers, computed per object. Any other method call in the argument list is rejected with a message naming the options.
• Lambdas receiving the generation context (From, Source, Use.From) take a non-nullable IGenerationContext, so no more ctx!. A FuncSource built from such a lambda throws a clear InvalidOperationException when used outside a session.
• The never implemented Ctor(...) stub on the generic type builder is removed.
• GenerateDocumentationFile on, CS1591 suppressed, unresolved cref references fixed. .gitattributes with * text=auto.
• CI flake fixed: the shared stable sequence helper compared two short random-seed samples for equality of their multiset; for MyTestEnum with ten values and four draws this collides often enough to fail on Windows net9 on main after PR Add generic NumberSource<T> and NullableNumberSource<T> with min/max #5. Bools and enums skip that comparison now.
• ShouldNotBeEmpty() in front of ShouldAllBe on collections derived from filtering.
• Not done, on purpose: a non-nullable IGenerationContext in the IDataSource contract itself. Standalone use of a source has no context and the test suite calls Next(null) a few hundred times. The nullable parameter is the honest contract there; the ergonomic pain was in the lambdas, which are fixed.

Test plan

• 19 new tests: constant, captured variable, null, Use.From per object, Use.From with context, mixed with Use.Source, rejection messages; null and range checks across container, builders, conventions, session, generator, collection and selection; FuncSource without context; error messages carry member names
• dotnet build -c Release zero warnings with the documentation file on
• 832 tests green per framework on net8, net9, net10 (Windows)
• Manual run of a file based app: lambda per object, context lambda, rejection message, null setup

🤖 Generated with Claude Code