fix many internal links

Fixed a number of internal links that need to
go to the GitHub site.

Ran `make www` to perform the above.

2004/jdalbec/index.html

@@ -434,16 +434,16 @@ the <a href="https://en.wikipedia.org/wiki/Isotope">isotopes</a> of
 last digit. Four common elements could also be written as isotopes of these two
 elements: <code>He=Np(2)</code>, <code>Li=Pu(2)</code>, <code>Ta=Np(3)</code>, <code>W=Pu(3)</code>. To get other isotopes,
 just change the last digit to a number greater than 3.</p>
-<p>The build file runs <a href="jdalbec.c">jdalbec.c</a> through the C preprocessor to
+<p>The build file runs <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/jdalbec/jdalbec.c">jdalbec.c</a> through the C preprocessor to
 generate <code>jdalbec2.c</code> which is edited with <code>ed(1)</code> (NOTE: this was
 changed to <code>sed(1)</code> by the judges) to correct spacing
 problems caused by some preprocessors. (I know you dislike
 Perl, but hopefully <code>ed(1)</code> is more common on POSIX systems than
 Perl.) The build file then compiles <code>jdalbec2.c]</code> and removes the
 <code>jdalbec2.c</code> file.</p>
-<p>I don’t think I’m abusing the <a href="Makefile">Makefile</a> since I’m only using
+<p>I don’t think I’m abusing the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/jdalbec/Makefile">Makefile</a> since I’m only using
 147 characters including white space and the <code>#!</code> line and the
-commented-out <code>-Wall -pedantic</code> options. The <a href="../../2004/rules.txt">rules for the
+commented-out <code>-Wall -pedantic</code> options. The <a href="../rules.txt">rules for the
 16th IOCCC</a> specifically allowed build files up to 521
 characters long so my build file would have been well within
 those limits. (What typo?)</p>
@@ -481,7 +481,7 @@ line 3 because the compiler doesn’t recognize <code>??=</code> as a trigraph
 step on Mac OS X 10.1.5 generates lots of errors in “smart
 mode” because the “smart” preprocessor expects a valid C
 program as input. The preprocessor then falls back to “basic
-mode” and preprocesses <a href="jdalbec.c">jdalbec.c</a> successfully without warnings,
+mode” and preprocesses <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/jdalbec/jdalbec.c">jdalbec.c</a> successfully without warnings,
 even when I give it the <code>-Wall -pedantic</code> options. It inserts
 a lot of extra spaces into the preprocessed output which is
 why I had to add the <code>ed(1)</code> step to the build file so that my
@@ -500,7 +500,7 @@ it if you run into this feature (e.g. <code>1 22</code> instead of <code>122</c
 <p>Note: you may want to be sure you have a limit on stack size before trying this.
 I ran it on Debian GNU/Linux and discovered that I did not have a limit on stack
 size. Fortunately the OS killed the process after a while. This is consistent
-with the output of <a href="../../1996/schweikh3/schweikh3.c">1996/schweikh3</a> which reports
+with the output of <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh3/schweikh3.c">1996/schweikh3</a> which reports
 <code>malloc lied!  Killed by SIGKILL</code>.</p>
 <p>Arguments matching <code>/(?:.){10,}/</code> will produce visually incorrect
 results (e.g., generation 1 starting from 1111111111 will