gh-139497: Clarify dataclass inheritance documentation

Author: harjothkhara

Doc/library/dataclasses.rst

@@ -194,6 +194,9 @@ Module contents
      glossary entry for details.  Also see the
      :const:`KW_ONLY` section.
 
+     This setting only applies to fields defined in the class being decorated;
+     it does not affect inherited fields.
+
      Keyword-only fields are not included in :attr:`!__match_args__`.
 
     .. versionadded:: 3.10
@@ -682,6 +685,15 @@ must use :meth:`!object.__setattr__`.
 Inheritance
 -----------
 
+The :deco:`dataclass` decorator is not automatically applied to subclasses.
+If a subclass is not itself decorated, no new dataclass fields are collected
+and no dataclass methods are generated for it.  Instead, it inherits fields and
+methods through the normal method resolution order.  This can be significant
+with multiple dataclass bases because their fields are not combined.  Decorate
+the subclass to combine the fields of its dataclass bases as described below.  An
+undecorated subclass of a dataclass is nevertheless considered a dataclass by
+:func:`is_dataclass` because it inherits dataclass metadata from a base class.
+
 When the dataclass is being created by the :deco:`dataclass` decorator,
 it looks through all of the class's base classes in reverse MRO (that
 is, starting at :class:`object`) and, for each dataclass that it finds,