Move Makefile.entry to Makefile.example

The file template/entry/Makefile.entry was moved to
next/Makefile.example. This matches the mkiocccentry repo in filename
and where it was before (template/entry) is not the right place as that
is for the template of making submissions into a winning entry whereas
next/ is for the next contest. The next/ seems like the most logical
place because the example file could be updated per contest for whatever
reason, perhaps by adding the year in it (or not). On the other hand,
the try.sh in template/entry is for submitters too but since the
bin/cvt-submission.sh script will copy the template files to a winning
entry if it does not exist it is left in template/entry, even if this
might not be ideal.

The references to the old Makefile.entry have been updated to
Makefile.example in the new path/filename.

Other changes had to be made too including updates to
bin/cvt-submission.sh. That script should be checked to make sure
everything is okay but as I have no way to test it that might have to be
done by the judges though I think it is okay.

Html files that have been changed that might need to be checked are:

0.    faq.html (this one especially should be checked)
1.    next/guidelines.html (though the judges will be checking this more)
2.    next/rules.html (though the judges will be checking this more)

For the faq.html file, the Makefile.example and try.sh/try.alt.sh
scripts should be downloaded, not linked to on GitHub and it needs to be
clear that one should use the Makefile.example from the website (this
repo) rather than the out of date mkiocccentry repo.

For the guidelines and rules, and especially the guidelines, any files
linked should also be downloaded and not linked to GitHub. The text
should be clear already but it might be good to have a quick pass. The
judges will be going over these files before the next contest too. The
files should be downloaded here too, not linked to GitHub as submitters
need to download the files to make use of.

The thanks-for-help.html file was slightly modified but should be fine
too. In this case the GitHub file should be linked to.

The version of the rules and guidelines are from an earlier date of when
they were last modified for the above changes (as this was worked on
over a number of days).

next/guidelines.html

@@ -465,7 +465,7 @@ writing by <a href="../contact.html">contacting the judges</a>.</p>
 </div>
 </div>
 <p class="leftbar">
-These <a href="guidelines.html">IOCCC guidelines</a> are version <strong>28.21 2024-11-27</strong>.
+These <a href="guidelines.html">IOCCC guidelines</a> are version <strong>28.23 2024-12-01</strong>.
 </p>
 <p><strong>IMPORTANT</strong>: Be <strong>SURE</strong> to read the <a href="rules.html">IOCCC rules</a>.</p>
 <p>Jump to: <a href="#">top</a></p>
@@ -551,11 +551,9 @@ repo</a>.
 to account for the new <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a> tools.
 </p>
 <p class="leftbar">
-An <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example">example
-Makefile</a>
-is now available from the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry
-repo</a> <strong>and you are encouraged to use
-it</strong>.
+You <strong>are encouraged</strong> to use <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">this
+Makefile.example</a>,
+rather than the one at the <code>mkiocccentry</code> repo.
 </p>
 <p class="leftbar">
 The IOCCC submission URL, <a href="../status.html#open">when the IOCCC is open</a>, is
@@ -941,15 +939,14 @@ that’s OK too!
 <h1 id="makefiles">Makefiles</h1>
 </div>
 <p class="leftbar">
-<p>We <strong>recommend</strong> that you use the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example">example
-Makefile</a>
-from the <a href="https://github.com/ioccc-src/mkiocccentry">IOCCC mkiocccentry repo</a>,
+<p>We <strong>recommend</strong> that you use the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example
+Makefile</a>,
 renamed as <code>Makefile</code> of course, as the starting point for your submission’s
 required <code>Makefile</code>. Feel free to modify the <code>Makefile</code> to suit your obfuscated
 needs.</p>
 <p class="leftbar">
 The rest of this section will assume that you are using some variant of the
-<a href="https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example">example Makefile</a>,
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example Makefile</a>,
 renamed as <code>Makefile</code> of course.
 </p>
 <p class="leftbar">
@@ -1092,19 +1089,23 @@ Again, please note that in macOS, <code>/usr/bin/gcc</code> is actually <code>cl
 </div>
 <p class="leftbar">
 We <strong>LIKE</strong> submissions that use an edited variant of the
-<a href="https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example">example Makefile</a>,
+<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example Makefile</a>,
 renamed as <code>Makefile</code> of course. This makes it easier for the <a href="../judges.html">IOCCC Judges</a>
 to test your submission. And if your submissions wins, it makes it easier to integrate it into
 the <a href="https://www.ioccc.org/index.html">Official IOCCC winner website</a>.
 </p>
 <p class="leftbar">
 We <strong>LIKE</strong> submissions that use an edited version of the
-<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/template/entry/try.sh">try.sh</a> template script (and if you have alternate code,
-the same applies with the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/template/entry/try.alt.sh">try.alt.sh</a>
-template script). Of course, it is
-quite possible that only one invocation is possible, so it is not necessarily
-detrimental to your submission if you do not include one, though we do like
-interesting and creative uses of submissions. See also the
+<a href="try.sh">try.sh</a> example script (and if you have alternate code,
+the same applies with the <a href="try.alt.sh">try.alt.sh</a>
+example script). Of course, it is quite possible that only one invocation is
+possible, so it is not necessarily detrimental to your submission if you do not
+include one, though we do like interesting and creative uses of submissions. See
+also the
+</p>
+<p class="leftbar">
+You might wish to add <code>./try.sh</code>, and if you have alternate code,
+<code>./try.alt.sh</code>, to the <code>try</code> rule in the Makefile you submit. See also the
 FAQ on “<a href="../faq.html#try_scripts">submitting try.sh and try.alt.sh scripts</a>”.
 </p>
 <p>Doing masses of <code>#define</code>s to obscure the source has become ‘old’. We
@@ -1339,7 +1340,7 @@ they do not work as documented.</p>
 is NOT the smallest C source file that when compiled and run, dumps core:</p>
 <pre><code>    main;</code></pre>
 <p class="leftbar">
-Unless you specify <code>-fwritable-strings</code> (see <code>COTHER</code> in the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example">example
+Unless you specify <code>-fwritable-strings</code> (see <code>COTHER</code> in the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example
 Makefile</a>)
 do not assume this sort of code will work:
 </p>
@@ -1347,6 +1348,9 @@ do not assume this sort of code will work:
     ...
     T[14] = &#39;;&#39;;    /* modifying a string requires: -fwritable-strings */</code></pre>
 <p class="leftbar">
+Even so, one should probably not assume that this is universally accepted.
+</p>
+<p class="leftbar">
 Initialized char arrays are OK to write over. For instance, this is OK:
 </p>
 <pre><code>    char b[] = &quot;Is this OK&quot;;
@@ -1559,7 +1563,7 @@ CPU, we might just try your submission on that emulator as well :-)
 <p class="leftbar">
 If your submission <strong>MUST</strong> run only on a 64-bit or 32-bit architecture,
 then you <strong>MUST</strong> specify the <code>-arch</code> on your command line
-(see <code>ARCH</code> in the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/Makefile.example">example
+(see <code>ARCH</code> in the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example
 Makefile</a>). Do not assume a processor word size without specifying <code>-arch</code>. For example:
 </p>
 <pre><code>    ARCH= -m64</code></pre>