fix(rfc2967): clarify rules around config-dependent generated files
@@ -51,7 +51,10 @@ predicated on:
1. Certain languages will necessarily emit different anchors under different
build configurations (C/C++ are particularly subject to this).
1. Generated source files must incorporate the build configuration into root in
- some fashion, if relevant.
+ some fashion, if the content of the generated files depends on the
+ configuration. This is a clarification of the current requirement that file
+ nodes omit the signature field and that each unique node have a unique
+ vname.
1. The relevant information should be in a form which is readily available for
filtering and display.
