update rules & guidelines

Improved Rule 1.

Added Guidelines for Rule 1.

Improved Rule 3.

Added missing Guidelines for Rule 3.

Reordered guidelines sections under the "General Guidelines".

Set level 2 for "General Guidelines" subsections.

Changed IOCCC Rules to version **29.11 2025-11-30**.
Changed IOCCC Guidelines to version **29.03 2025-11-30**.

Ran `make quick_www` to perform the above.

next/rules.html

@@ -480,7 +480,7 @@ granted provided this copyright and notice are included in its entirety
 and remains unaltered. All other uses <strong>MUST</strong> receive prior permission in
 writing by <a href="../contact.html">contacting the judges</a>.</p>
 <h2 id="rules-version">Rules Version</h2>
-<p>These IOCCC Rules are version <strong>29.10 2025-11-30</strong>.</p>
+<p>These IOCCC Rules are version <strong>29.11 2025-11-30</strong>.</p>
 <p>Reminder: be SURE to read the <a href="guidelines.html">IOCCC guidelines</a>.</p>
 <div id="rule0">
 <h2 id="rule-0---dates">Rule 0 - Dates</h2>
@@ -494,13 +494,16 @@ allowing people to <a href="submit.html">upload submissions</a>.</p>
 when people will no longer be allowed to upload submissions.</p>
 <p>The above <strong>dates and times may change <em>AT ANY TIME</em></strong> until the <a href="../status.html">contest status</a> is <strong>open</strong>.</p>
 <p>The above timestamps are in “<em>YYYY-MM-DD HH:MM:SS.micros UTC</em>” format.</p>
-<p>See <a href="../quick-start.html#enter">entering the IOCCC</a>.</p>
+<p>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>.</p>
 <p>See
 FAQ on “<a href="../faq.html#feedback">How can I comment or make a suggestion on IOCCC rules, guidelines and tools?</a>”.</p>
 <div id="rule1">
+<div id="rule1-c">
 <h2 id="rule-1---c-program">Rule 1 - C program</h2>
 </div>
-<p>Your submission <strong>MUST</strong> be a C program that does NOT <code>#include</code> data files.</p>
+</div>
+<p>Your submission <strong>MUST</strong> be a C program.</p>
+<p>See the <a href="guidelines.html#guidelines-for-rule-1---c-program">Guidelines for Rule 1 - C program</a>.</p>
 <div id="rule2">
 <div id="rule2-size-restrictions">
 <div id="rule2-size">
@@ -526,8 +529,6 @@ During development this can be checked using <code>iocccsize(1)</code>:</p>
 </div>
 <p>The overall maximum size of your <code>prog.c</code> program source <strong>MUST NOT</strong>
 exceed <strong>4993</strong> bytes.</p>
-<p><strong>NOTE</strong>: by default <code>iocccsize</code> will only report the rule 2b size, unless the
-code surpasses the limit.</p>
 <p>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>.</p>
 <div id="rule2b">
 <div id="rule2b-net-size">
@@ -550,16 +551,9 @@ Use mkiocccentry</a>.</p>
 <p>You <strong>MUST</strong> register, using a valid email address, in order to submit
 to the IOCCC. You may register while the contest is <strong>pending</strong> or <strong>open</strong>.</p>
 <p>A few days after registering, you’ll receive your UUID username and
-temporary password, which you <strong>MUST</strong> change within 14 days. If you
-fail to change it in a timely manner, you’ll need to
-<a href="../contact.html">contact the Judges</a> by email to request a reset.</p>
-<p>It can take a few days to process your registration and for the server to
-email your details, therefore make sure to allow yourself ample time to
-register and submit your entries; <strong>DO NOT WAIT UNTIL THE FINAL DAYS</strong>
-to register! The judges are <strong>NOT</strong> responsible for delayed or lost
-email or for those who wait until the last minute to try to register!</p>
+temporary password, which you <strong>MUST</strong> change within 14 days.</p>
+<p>See <a href="register.html">How to register for the IOCCC</a>.</p>
 <p>See <a href="../quick-start.html#enter">Entering the IOCCC: the bare minimum you need to know</a>.</p>
-<p>See <a href="rules.html#rule8">Rule 8 - Submitting requirements</a>.</p>
 <p>See <a href="guidelines.html#guideline-3---register">Guidelines for Rule 3 - Register for the IOCCC</a>.</p>
 <div id="rule4">
 <div id="rule4-required-files">
@@ -664,8 +658,9 @@ owner(s) to its use. If you submit <strong>ANY</strong> content that is owned by
 <strong>MUST</strong> detail that ownership, i.e., who owns what, and document the permission
 you obtained from them in your <code>remarks.md</code> file.</p>
 <p>You are permitted to use tools to write your code.</p>
-<p>See <a href="rules.html#rule16-anonymous-judging">Rule 16 - Anonymous Judging</a>.</p>
-<p>See <a href="guidelines.html#guideline-7---original-work">Guidelines for Rule 7 - Original Work</a>.</p>
+<p>See <a href="rules.html#rule16-anonymous-judging">Rule 16 - Anonymous Judging</a>,
+and
+<a href="guidelines.html#guideline-7---original-work">Guidelines for Rule 7 - Original Work</a>.</p>
 <div id="rule8">
 <div id="rule8-submitting-requirements">
 <h2 id="rule-8---submitting-requirements">Rule 8 - Submitting requirements</h2>
@@ -682,7 +677,6 @@ and resubmit. In order to avoid potential packaging errors, it is <strong>highly
 recommended</strong> to use <code>mkiocccentry(1)</code>, <strong>AND</strong> to check from time to time the
 status on the submit server, to see if any tests run by the server failed to
 validate your submission.</p>
-<p>Do <strong>NOT</strong> register more than one account!</p>
 <p>See
 <a href="rules.html#rule3-register">Rule 3 - Registering for the IOCCC</a>,
 <a href="rules.html#rule15-gnu-makefile">Rule 15 - GNU Makefile</a>,
@@ -740,8 +734,7 @@ is rejected.</p>
 version, <strong>PLEASE</strong> indicate that in your <code>remarks.md</code> file of your non-rule
 abusing version so that the Judges don’t think you uploaded a duplicate into a
 wrong slot by mistake.</p>
-<p>See <a href="guidelines.html#guideline-11---abuse">Guidelines for Rule 11 - Legal rule
-abuse</a>.</p>
+<p>See <a href="guidelines.html#guideline-11---abuse">Guidelines for Rule 11 - Legal rule abuse</a>.</p>
 <div id="rule12">
 <div id="rule12-utf8">
 <h2 id="rule-12---utf-8">Rule 12 - UTF-8</h2>