docs(codegen): drop the meta-commentary about the removed rationale

Author: thedavidmeister

src/lib/LibCodeGen.sol

@@ -23,18 +23,10 @@ string constant NEWLINE_DUE_TO_MAX_LENGTH = "\n    ";
 /// as strings that can be concatenated into complete Solidity files and written
 /// to disk by the caller.
 library LibCodeGen {
-    /// The file prefix for autogenerated files: the license, the pragma, and a
-    /// note that the file is generated and must not be hand-edited. The pragma
-    /// is `^` as the generated code is expected to be imported into some
-    /// concrete contract with `pragma =` version.
-    ///
-    /// Deliberately says nothing about WHY the file is committed. Generated
-    /// files are committed; that is a fact about the repo, not something each
-    /// file needs to argue, and the circular-dependency explanation this used
-    /// to carry is true of a pointers file and false of the other generated
-    /// files repos write — an alias lib is committed because it IS the source
-    /// consumers import. Saying nothing is true of all of them, which is what
-    /// makes this prefix usable by every writer with nothing to parameterise.
+    /// The file prefix for autogenerated files outlines the license, pragma,
+    /// and a note about the file being autogenerated. The pragma is ^ as the
+    /// generated code is expected to be imported into some concrete contract
+    /// with pragma = version.
     function filePrefix() internal pure returns (string memory) {
         //REUSE-IgnoreStart
         return string.concat(

test/lib/LibCodeGen.filePrefix.t.sol

@@ -20,12 +20,6 @@ contract LibCodeGenFilePrefixTest is Test {
     /// change here rewrites committed files org wide. Pinned exactly so that
     /// lands as a deliberate, reviewable diff rather than a surprise on the
     /// next regeneration.
-    ///
-    /// It says nothing about why the file is committed. Generated files are
-    /// committed; that is a fact about the repo rather than something each file
-    /// argues, and the circular-dependency explanation this used to carry was
-    /// true of a pointers file and false of an alias lib, which is committed
-    /// because it IS the source consumers import.
     function testFilePrefixExact() external pure {
         //REUSE-IgnoreStart
         assertEq(