Context
From PR #115 review. The fullRegistryV0 / fullRegistryV1 helpers in structural-validation.test.ts only feed the new write-quality assertions (bodySchema, actionDescription on risky operations). The existing invariants (type naming, description presence, etc.) still iterate allTypes from the default registry only, so opt-in toolsets are excluded from those checks.
Files
tests/registry/structural-validation.test.ts (lines 35-40)
Proposed fix
Extend all structural invariants to iterate over the full registry (including opt-in toolsets). This may require adjusting some assertions that assume default-only behavior.
Priority
Low — opt-in toolsets are covered by their own domain-specific tests. This is about making the structural contract exhaustive.
Context
From PR #115 review. The
fullRegistryV0/fullRegistryV1helpers instructural-validation.test.tsonly feed the new write-quality assertions (bodySchema, actionDescription on risky operations). The existing invariants (type naming, description presence, etc.) still iterateallTypesfrom the default registry only, so opt-in toolsets are excluded from those checks.Files
tests/registry/structural-validation.test.ts(lines 35-40)Proposed fix
Extend all structural invariants to iterate over the full registry (including opt-in toolsets). This may require adjusting some assertions that assume default-only behavior.
Priority
Low — opt-in toolsets are covered by their own domain-specific tests. This is about making the structural contract exhaustive.