[CaffeinatedCoder]

Closes #230

Stacked on #236 (fix/generic-or-ref-overload-refused-2-3-1, #226), which is stacked on #218. Both touch ValueObjectDeclaration.cs and ClosedSetTypes.cs. Merge in order: #218, then #236, then this PR. This PR also answers the sweep's finding against #218 on #205: a set's base class's private Parse(string) was refused.

Problem

The base-member checks that 2.3.1 added read every member of every base, whatever its accessibility:

• Declared over SelfAndBases in ValueObjectDeclaration.GeneratedMembersDeclaredByHand (A base record's public implementation of a generated member is kept as the value object's, or crashes the aspect #197)
• InheritedSeams (A base record's explicit Create from another project leaves two rule sets #195)
• the base loop of ValueObjectComparableAspect.HandWrittenComparisonMembers (An inherited CompareTo(TSelf) is not seen: EF Core orders by the column, and < overflows the stack #194)
• the method lines of ClosedSetTypes.GeneratedMembersDeclaredByHand (A closed set over a base class that declares a generated member fails with a Metalama error, or its ToString() is replaced #205)

C# hides a base's private member from the derived type, so it stands in for no generated member. Yet a base record's private MaxValue, Parse, TryFrom or CompareTo(object) failed the build with CMTK1011 or CMTK1008, where 2.3.0 generated the value object. A set's base class's private Parse(string) failed the same way.

Change

• Each base check counts only a member the type can see (IsAccessibleFrom, Metalama 2026.1). MembersNamed and MethodsWithSignature take the type that looks (seenFrom), and InheritedSeams, the comparable aspect's base loop and the closed set's base reads filter the same way. The closed set's field and property line read Accessibility != Private before and now reads the same as the rest.
• A value object nested in its base record sees the base's private members, as C# does, so it stays refused. A library's private and internal members were never listed and still build.
• Generators README (a sentence each under "Write your own members" and "Rules for a closed set"), design/aspects.md, two claims, a CHANGELOG line. No decision record: decision 121 refuses a member "wherever the value object reaches it", and a private one isn't reached.

Tests

• BaseMemberAccessibility (new) is the input class's catalogue, built in BuildOutcomeTests' consumer. It crosses 6 accessibilities (private, private protected, protected, internal, protected internal, public) with every name the checks read: Value, From, MinValue, MaxValue, Parse/TryParse over string, span and UTF-8, ToString(string?, IFormatProvider?), TryFormat, CompareTo(object), CompareTo(TSelf), TryFrom, Revalidate, and a set's Parse, TryParse and Match. The 19 private rows build. The 80 others and the nested row are refused naming the base. A library's hidden members build.
• InheritedMembersTests: over a base with every private name, each generated member is what a call reaches. That covers MaxValue == int.MaxValue, parsing, formatting, the ordering without [HandWrittenOrdering], TryFrom(-1) is none, Revalidate, and a set's Parse, TryParse and Match.
• Reverted: the 19 private rows fail, and the test project's own build refuses its three types. Counting only a base's public members fails the 76 protected and internal rows and the nested one.
• Locally through tools/BuildVerdict: Generators.Tests 1371 passed, Conventions.Tests 2016, Samples 150.

🤖 Generated with Claude Code