Remove the rules about DartDoc comments in the language specification

Author: eernstg

specification/dartLangSpec.tex

@@ -41,6 +41,11 @@
 % version of the language which will actually be specified by the next stable
 % release of this document.
 %
+% Sep 2025
+% - Remove the rules about scoping with DartDoc comments. This topic is now
+%   handled by each of the tools that process those comments in any way, and
+%   this document only specifies the syntax of DartDoc comments.
+%
 % Jul 2025
 % - Clarify that operator `[]` and `[]=` are included in the `void` allowlist
 %   rule about formal parameters of type `void`, and so are setters.
@@ -23420,25 +23425,14 @@ \subsubsection{Comments}
 \LMHash{}%
 \IndexCustom{Documentation comments}{documentation comments}
 are comments that begin with the tokens \code{///} or \code{/**}.
-Documentation comments are intended to be processed by
-a tool that produces human readable documentation.
-
-\LMHash{}%
-The current scope for a documentation comment immediately preceding
-the declaration of a class $C$ is the
-\IndexCustom{body scope}{scope!for statement body}
-of $C$.
-
-\LMHash{}%
-The current scope for a documentation comment immediately preceding
-the declaration of a non-redirecting generative constructor $k$
-with initializing formals is the formal parameter initializer scope of $k$
-(\ref{generativeConstructors}).
 
-\LMHash{}%
-Otherwise, the current scope for a documentation comment immediately preceding
-the declaration of a function $f$ is the formal parameter scope of $f$
-(\ref{formalParameters}).
+\rationale{%
+  Documentation comments are intended to be processed by
+  a tool that produces human readable documentation.
+  However, this document does not place any constraints
+  on the interpretation or use of documentation comments,
+  that is determined by each of the relevant tools.%
+}
 
 
 \subsection{Operator Precedence}