2024/ferguson1 bug fix, make goto complete (149)

A bug was discovered in prog.c (now prog.alt2.c, see below) that has
been fixed. It was not a critical bug but it came about when juggling
things during development, and fixing it means there should now only be
one place where an event might not trigger (or actually it's an event
within an event that does not trigger - polymorphism related).

The prog.c is the goto complete version - what was once prog.goto.max.c
(git status is confused however - it shows that that file is now
prog.alt2.c but actually prog.alt2.c is what prog.c was). For practical
reasons (and to make the judges not weep and curse me quite as much)
this was not the prog.c but since some others have made corrections to
their winning code I have decided to do the same thing here. It was a
hassle to juggle between the different versions and I ran out of the
number of files allowed - that is what I mean by practical reasons.

The prog.c has maintained its thematic 4666 bytes, after some formatting
updates.

Typo fixes were made in some of the supplementary C files.

Makefile updated so that one can compile prog.alt2.c.

.entry.json, index.html and obfuscation.html were all updated.

The judges' remarks were slightly corrected. It is not 134 (now 149)
jumps that occurs but rather gotos. The jumps can be over 1000, in fact
one test run was over 1400, although shorter games can be fewer (though
still a lot).

Other errors in documentation that were artefacts from earlier stages in
development were also corrected, although I'm sure there are more (the
ones that were discovered were ones near to stats that had to be
updated).

2024/ferguson1/printer.c

@@ -9,16 +9,6 @@
  * Using the macro (identical except it uses puts() on some of the strings that
  * are unencrypted) from prog.c we will print out every string
  * at every location in the order it occurs.
- *
- * IMPORTANT NOTE: as some strings have a marker that indicates to not be
- * encrypted but the marker is not in the data file itself, the bytecount.c
- * might be better in that it uses the data source file.  However for my own
- * purposes I have this tool too. This tool, to prevent display problems, checks
- * for specific known locations where it should not decrypt anything due to not
- * being encrypted (the '%' ones notwithstanding), and if it is that number it
- * will print it out with puts() instead (can't be printf() as it has %
- * conversions). A BEL byte also is unencrypted (if it's the first character of
- * the string it's skipped and printed without encrypting it).
  */
 #include <string.h>
 #include <stdio.h>
@@ -32,7 +22,6 @@
  */
 #define Z(x) (x)*BLOCKSIZE
 #define V(x) puts(&y[Z(x)]);
-static char *p;
 static char *y;
 static char *filename = "data";
 static size_t len;