doc: fix NEWS placement and cookbook example of purge requirement

Move the NEWS entry to the end of the 5.7.0 list, as entries follow the
order changes landed. Report in the cookbook example the output of the
env/base load, which auto-loads its requirements, and the auto-loaded
tag these requirements then carry in the module list. Also restore the
blank line removed from NEWS.rst, unrelated to this change.

Assisted-by: Claude:claude-fable-5-1
Signed-off-by: Xavier Delaruelle <xavier.delaruelle@cea.fr>

Author: xdelaruelle

NEWS.rst

@@ -251,9 +251,6 @@ Modules 5.7.0 (not yet released)
 * Doc: add the :ref:`user-guide` document that explains a selection of
   useful but lesser known features through practical examples and common
   use cases.
-* Keep non-sticky requirements of sticky modules loaded during a
-  :subcmd:`purge` and explicitly report why their unload is skipped according
-  to the :mconfig:`sticky_purge` configuration. (fix issue #582)
 * Init: fix command injection in Bash completion when module names contain
   shell meta-characters. Completion candidates were passed to ``compgen -W``
   which evaluates command substitution syntax. (fix `CVE-2026-85013`_ found
@@ -267,9 +264,13 @@ Modules 5.7.0 (not yet released)
   :mfcmd:`is-used` modulefile command or of the :subcmd:`unuse` sub-command
   is also resolved against the current working directory to recognize such
   entry whatever its form.
+* Keep non-sticky requirements of sticky modules loaded during a
+  :subcmd:`purge` and explicitly report why their unload is skipped according
+  to the :mconfig:`sticky_purge` configuration. (fix issue #582)
 
 .. _CVE-2026-85013: https://github.com/envmodules/modules/security/advisories/GHSA-8hrw-p88g-qhmg
 
+
 .. _5.6 release notes:
 
 Modules 5.6.2 (2026-09-07)

doc/source/cookbook/sticky-modules.rst

@@ -200,6 +200,8 @@ module remains loaded:
 
     :ps:`$` module config sticky_purge warning
     :ps:`$` module load env/base
+    Loading :sgrhi:`env/base`
+      :sgrin:`Loading requirement`: core compiler
     :ps:`$` module purge
     Unloading :sgrhi:`env/base`
       :sgrwa:`WARNING`: Unload of super-sticky module skipped
@@ -211,10 +213,10 @@ module remains loaded:
       :sgrwa:`WARNING`: Unload of super-sticky module requirement skipped
     :ps:`$` module list
     Currently Loaded Modulefiles:
-     1) core   2) compiler   3) :sgrss:`env/base`
+     1) :sgral:`core`   2) :sgral:`compiler`   3) :sgrss:`env/base`
 
     Key:
-    :sgrss:`super-sticky`
+    :sgral:`auto-loaded`  :sgrss:`super-sticky`
 
 Both requirements remain loaded even though they are not sticky themselves.
 The same protection applies to indirect requirements and to a forced purge