Move 4137, 4302 and 4315 to Ready at telecon

Author: jwakely

xml/issue4137.xml

@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='utf-8' standalone='no'?>
 <!DOCTYPE issue SYSTEM "lwg-issue.dtd">
 
-<issue num="4137" status="New">
+<issue num="4137" status="Ready">
 <title>Fix <i>Mandates</i>, <i>Preconditions</i>, and <i>Complexity</i> elements of [linalg] algorithms</title>
 <section><sref ref="[linalg.algs.blas2]"/><sref ref="[linalg.algs.blas3]"/></section>
 <submitter>Mark Hoemmen</submitter>
@@ -347,6 +347,8 @@ template&lt;class ExecutionPolicy,
 <note>LWG telecon 2025-10-10; Fix proposed resolution after review</note>
 <p>Add missing `()` in one place and change `(0, 1)` to `()` in another.</p>
 
+<note>LWG telecon 2025-10-10; Status &rarr; Ready</note>
+
 </discussion>
 
 <resolution>

xml/issue4302.xml

@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='utf-8' standalone='no'?>
 <!DOCTYPE issue SYSTEM "lwg-issue.dtd">
 
-<issue num="4302" status="New">
+<issue num="4302" status="Ready">
 <title>Problematic `vector_sum_of_squares` wording</title>
 <section><sref ref="[linalg.algs.blas1.ssq]"/></section>
 <submitter>Mark Hoemmen</submitter>
@@ -61,6 +61,9 @@ about QoI of `vector_two_norm` should already know what to do. If
 somebody cares sufficiently, they can propose it back for C++29 and
 think about how to make it work for generic number types.
 </p>
+
+<note>LWG telecon 2025-10-10; Status &rarr; Ready</note>
+
 </discussion>
 
 <resolution>

xml/issue4315.xml

@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='utf-8' standalone='no'?>
 <!DOCTYPE issue SYSTEM "lwg-issue.dtd">
 
-<issue num="4315" status="New">
+<issue num="4315" status="Ready">
 <title>Insufficient specification of `vector_two_norm` and `matrix_frob_norm`</title>
 <section>
 <sref ref="[linalg.algs.blas1.nrm2]"/>
@@ -131,6 +131,8 @@ this later so want to make it ill-formed, not something that is statically
 checkable as part of the API.
 </p>
 
+<note>LWG telecon 2025-10-10; Status &rarr; Ready</note>
+
 </discussion>
 
 <resolution>