Change:
The text will be adjusted in a future PR.
This github bug is slowing me down a bit:
Huh! I'm not seeing that.
I'm only seeing it every second time I try to pull the repo state (issues, PRs) into emacs, which seems to use a graphql API. Annoying. This used to work well...
Thanks!

Discussion:
1.3. <ins> The JSON value the JSONPath query is applied to is, by definition, a valid JSON value.  The parsing of a JSON text into a JSON value and what happens if a JSON text does not represent valid JSON are not defined by this specification.  Sections RFC8259 and RFC8259 of RFC8259 identify specific situations that may conform to the grammar for JSON texts but are not interoperable uses of JSON, as they may cause unpredictable behavior.  The present specification does not attempt to define predictable behavior for JSONPath queries in these situations. Specifically, the "Semantics" subsections of Sections name-selector, wildcard, filter-selector, and descendant-segment describe behavior that becomes unpredictable when the JSON value for one of the objects under consideration was constructed out of JSON text that exhibits multiple members for a single object that share the same member name ("duplicate names", see RFC8259).  Also, selecting a child by name (name-selector) and comparing strings (comparisons in Section filter- selector) assume these strings are sequences of Unicode scalar values, becoming unpredictable if they aren't (RFC8259). 1.4. </ins> A JSONPath expression is applied to a JSON value, the .  The output is a nodelist.

of zero or more segments each of which contains one or more selectors. <del> 1.3.1. </del> <ins> 1.4.1. </ins> The

in the context of the evaluation of a filter expression (described later). <del> 1.3.2. </del> <ins> 1.4.2. </ins> Segments can use the

various shorthands in terms of bracket notation.  Examples and descriptions use shorthands where convenient. <del> 1.3.3. </del> <ins> 1.4.3. </ins> A wildcard "*" (wildcard) in the expression "[*]" selects all children of an object or an array and in the expression "..[*]"

Filter expressions "?<boolean expr>" select certain children of an object or array as in <del> 1.3.4. </del> <ins> 1.4.4. </ins> tbl-overview provides a quick overview of the JSONPath syntax elements.

resource depletion and related errors are comparable to 500 type errors.) <del> The JSON value the JSONPath query is applied to is, by definition, a valid JSON value.  The parsing of a JSON text into a JSON value and what happens if a JSON text does not represent valid JSON are not defined by this specification.  Sections RFC8259 and RFC8259 of RFC8259 identify specific situations that may conform to the grammar for JSON texts but are not interoperable uses of JSON, as they may cause unpredictable behavior.  The present specification does not attempt to define predictable behavior for JSONPath queries in these situations. Specifically, the "Semantics" subsections of Sections name-selector, wildcard, filter-selector, and descendant-segment describe behavior that becomes unpredictable when the JSON value for one of the objects under consideration was constructed out of JSON text that exhibits multiple members for a single object that share the same member name ("duplicate names", see RFC8259).  Also, selecting a child by name (name-selector) and comparing strings (comparisons in Section filter- selector) assume these strings are sequences of Unicode scalar values, becoming unpredictable if they aren't (RFC8259). </del> 3.2. Syntactically, a JSONPath query consists of a root identifier ("$"),