Small fixes

Author: pablogsal

.github/CODEOWNERS

@@ -703,6 +703,7 @@ peps/pep-0826.rst  @savannahostrowski
 peps/pep-0827.rst  @1st1
 peps/pep-0828.rst  @ZeroIntensity
 peps/pep-0829.rst  @warsaw
+peps/pep-0830.rst  @pablogsal @Fidget-Spinner @savannahostrowski
 # ...
 peps/pep-2026.rst  @hugovk
 # ...

peps/pep-0830.rst

@@ -3,12 +3,12 @@ Title: Frame Pointers Everywhere: Enabling System-Level Observability for Python
 Author: Pablo Galindo Salgado <pablogsal@python.org>,
         Ken Jin <kenjin@python.org>,
         Savannah Ostrowski <savannah@python.org>,
-Discussions-To:
+Discussions-To: Pending
 Status: Draft
 Type: Standards Track
 Created: 14-Mar-2026
 Python-Version: 3.15
-Post-History:
+Post-History: Pending
 
 
 Abstract
@@ -920,6 +920,25 @@ Reference Implementation
 <https://github.com/pablogsal/cpython/tree/frame-pointers>`_
 
 
+Rejected Ideas
+==============
+
+This PEP rejects leaving frame pointers as a per-deployment opt-in because that
+does not provide a reliable default observability story for Python users, Linux
+distributions, or downstream tooling.  It also rejects treating DWARF-based or
+vendor-specific unwinding schemes as a sufficient general solution because they
+do not provide the same low-overhead, universally available stack walking path
+for kernel-assisted profiling and tracing.  The alternatives discussed in
+`Alternatives to Frame-Pointer Unwinding`_ remain useful in some contexts, but
+they do not remove the need for frame pointers as the default baseline.
+
+
+Change History
+==============
+
+None at this time.
+
+
 Footnotes
 =========