add rules, guidelines, fix HTML code, move compressed tarball in inventory

By changing the _inventory_order_ of the compressed tarball from
**100000** to **1415926535**, the compressed tarball will land at
the top of the secondary file list and remain still easy to find.

Updated the `manifest.numbers` spreadsheet and rebuilt
the `.entry.json` files.

Added `next/` directory to hold the next IOCCC rules and guidelines.
Added `next/README.md` that `bin/gen-top-html.sh` uses to form
the `next/index.html` file.

Added _Rules and Guidelines_ link to the sidenav bar to link to the
`next/index.html` file.

Added _IOCCC Rules_ as `next/rules.md` that `bin/gen-top-html.sh`
uses to form the `next/rules.html` file.

Added _IOCCC Guidelines_ as `next/guidelines.md` that `bin/gen-top-html.sh`
uses to form the `next/guidelines.html` file.

Changed `bin/gen-top-html.sh` VERSION from "1.2.4 2024-04-13"
to "1.3 2024-04-14".

Prevent `pandoc(1)` from interpreting the commented out language
of a markdown code block as a code class.  So a markdown such as:

````
``` <!---sh-->
...
```
````

that produced HTML of the form:

```html
<pre class="&lt;!---sh--&gt;"><code>...</code></pre>
```

will now produce HTML of the form:

```html
<pre><code>...</code></pre>
```

NOTE: Before when the language of a markdown code block
was not commented, the HTML produced by `pandoc(1)` was
oddly indented with extra whitespace on the first line
of the code block.  While commenting out the language
of the code block removed some of the odd intending,
it left a weird class in the HTML pre block that
surrounded the HTML code block.  This hack prevents
`pandoc(1)` from assigning a class to the HTML pre block.

Changed `in/md2html.sh` VERSION from "1.2.1 2024-04-13"
to "1.3 2024-04-14".

Added `make gen_sitemap` to end of both `make www` and `make
quick_www` in top level Makefile.

Ram `make www` to test under macOS and to perform the above.

**IMPORTANT NOTE**: The current `next/rules.md` and `next/guidelines.md`
are simply the 2020 IOCCC Rules and Guidelines converted into
markdown form.  There are **NOT** the Rules and Guidelines that
will be used the IOCCC MOCK, nor the next IOCCC.

TODO: Improve the `bin/gen-status.sh` tool to modify the top of the
      `next/rules.md` and `next/guidelines.md` files to keep them
      in sync with the _contest_status_ as found in `status.json`.

TODO: Improve the look and feel of the `next/rules.md` and
      `next/guidelines.md` markdown files.

1990/pjr/index.html

@@ -88,6 +88,7 @@
     <div class="sidenav">
       <a href="../../news.html">IOCCC News</a>
       <a href="../../status.html">Contest status</a>
+      <a href="../../next/index.html">Rules and Guidelines</a>
       <a href="../../faq.html#submit">How to enter the IOCCC</a>
       <a href="../../faq.html">FAQ</a>
     </div>
@@ -141,24 +142,24 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
 <!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
 
 <h2 id="to-build">To build:</h2>
-<pre class="&lt;!---sh--&gt;"><code>    make all</code></pre>
+<pre><code>    make all</code></pre>
 <p>There is an <a href="#alternate-code">alternate version</a> that does something different
 that can be used if your compiler is incapable of compiling <code>X=g()...</code> in
 <code>main()</code>. It can be used for another purpose too.</p>
 <h2 id="to-use">To use:</h2>
-<pre class="&lt;!---sh--&gt;"><code>    ./pjr</code></pre>
+<pre><code>    ./pjr</code></pre>
 <h2 id="alternate-code">Alternate code:</h2>
 <p>Note that some compilers will be unable to compile the expression <code>X=g()...</code> in
 <code>main()</code> due to lack of temporary stack space. One might want to try replacing
 <code>main()</code> with:</p>
-<pre class="&lt;!---c--&gt;"><code>    main(){X=s().v().o().o().l().S().d().l().i().o().w().N();}</code></pre>
+<pre><code>    main(){X=s().v().o().o().l().S().d().l().i().o().w().N();}</code></pre>
 <p>if this is a problem, which is what this alternate code is.</p>
 <p>NOTE: it prints something else and it is what the author suggested one try as
 well.</p>
 <h3 id="alternate-build">Alternate build:</h3>
-<pre class="&lt;!---sh--&gt;"><code>    make alt</code></pre>
+<pre><code>    make alt</code></pre>
 <h3 id="alternate-use">Alternate use:</h3>
-<pre class="&lt;!---sh--&gt;"><code>    ./pjr.alt</code></pre>
+<pre><code>    ./pjr.alt</code></pre>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>This program prints out a string. Can you figure out how
 it is done?</p>
@@ -175,7 +176,7 @@ alphabetical character from a to z is printed out as its
 opposite:</p>
 <pre><code>    a-&gt;z b-&gt;y c-&gt;x etc</code></pre>
 <p>To encode a new string input the string as it is meant to come out:</p>
-<pre class="&lt;!---c--&gt;"><code>    X=s().v().o().o().l().S().d().l().i().o().w().N();</code></pre>
+<pre><code>    X=s().v().o().o().l().S().d().l().i().o().w().N();</code></pre>
 <p>Note: <code>S()</code> represents a space and <code>N()</code> a newline. This will now
 produce…</p>
 <pre><code>    hello world</code></pre>
@@ -209,10 +210,10 @@ to the reader to find out what it is.</p>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1990/pjr/Makefile">Makefile</a> - entry Makefile</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1990/pjr/pjr.alt.c">pjr.alt.c</a> - alternative source</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1990/pjr/pjr.orig.c">pjr.orig.c</a> - original source</li>
-<li><a href="1990_pjr.tar.bz2">1990_pjr.tar.bz2</a> - download entry tarball</li>
 </ul>
 <h2 id="secondary-files">Secondary files</h2>
 <ul>
+<li><a href="1990_pjr.tar.bz2">1990_pjr.tar.bz2</a> - download entry tarball</li>
 <li><a href="index.html">index.html</a> - this web page</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1990/pjr/README.md">README.md</a> - markdown source for this web page</li>
 <li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1990/pjr/.entry.json">.entry.json</a> - description of entry in JSON</li>