retry/transaction statements can have on fail

Fixes #1157

lang/spec.html

@@ -7877,9 +7877,6 @@ <h3>Statements</h3>
    | break-stmt
    | stmt-with-on-fail
    | fail-stmt
-   | retry-stmt
-   | transaction-stmt
-   | retry-transaction-stmt
    | rollback-stmt
    | panic-stmt
    | return-stmt
@@ -7889,11 +7886,14 @@ <h3>Statements</h3>
 <pre
 class="grammar">
 regular-compound-stmt :=
-  do-stmt
-  | match-stmt
-  | foreach-stmt
-  | while-stmt
-  | lock-stmt
+   do-stmt
+   | match-stmt
+   | foreach-stmt
+   | while-stmt
+   | lock-stmt
+   | retry-stmt
+   | transaction-stmt
+   | retry-transaction-stmt
 </pre>
 <p>
 A <code>regular-compound-stmt</code> can be combined with an
@@ -9738,6 +9738,10 @@ <h4>On fail clause</h4>
 or a <code>fail</code> statement may cause control to transfer to the
 <code>on-fail-cause</code>. If so, the <code>statement-block</code> is executed;
 otherwise the <code>statement-block</code> is not executed.
+When the regular-compound-stmt is itself a failure handling statement,
+then only failure of that regular-compound-stmt itself causes control to
+transfer to the <code>on-fail-clause</code>; a failure <em>within</em> that
+regular-compound-stmt will be handled by that regular-compound-statement.
 </p>
 <p>
 If there is a <code>typed-binding-pattern</code>, then it is matched to the
@@ -11676,6 +11680,8 @@ <h3>Summary of changes from 2023R1 to 2024R1</h3>
 <li>A query-select-expr can construct a stream without explicitly specififying
 the <code>stream</code> keyword.</li>
 <li>It is no longer allowed for a lock statement to contain a sync-send-action or a receive-action.</li>
+<li>A <code>retry</code> or <code>transaction</code> statement may now have an <code>on fail</code>
+clause.</li>
 </ol>
 </section>
 <section>