release: 0.3.0 (#98)

* release: 0.3.0

The owner's decision, and his alone - immutable rule 12. This is the version
0.3.0-rc1 already carried, without the suffix, and the suffix is the whole
mechanical difference. The release workflow marks a release as a prerelease
when the TAG NAME carries a hyphen, which is what kept rc1 off the front page
and out of "latest". Dropping it is what puts this build there.

The entries that shipped as 0.3.0-rc1 were folded into the 0.3.0 section
rather than left beside it, on the owner's instruction. Somebody upgrading
from 0.2.0 needs one list of what changed rather than two, and the Breaking
list is only true read whole: the padding of a ZIP, a TAR.GZ and a WAV changed
after rc1 went out, so the two halves describe one delta from 0.2.0. The
merged section carries 67 entries - 9 Breaking, 22 Added, 5 Security, 14
Changed and 17 Fixed - under one heading of each kind. The [0.3.0-rc1] heading
goes with them and so does its link definition, because a definition left
behind points at a comparison nobody can reach from the document.

Both of the release gate's own conditions were run here and pass: the
changelog has a section for 0.3.0, and nothing is left under [Unreleased].

Outside internal/version the number has nine copies. Six are held by a guard
in this repository, one by a tool outside it, and two by nothing at all.

The Windows resource compiled into both binaries carries the version, and a
guard reads the COMPILED resource rather than the script beside it. Both
scripts were updated and both recompiled with windres, and each .syso lost
exactly sixteen bytes - four characters, twice over, two bytes apiece in
UTF-16. The numeric FILEVERSION fields were already 0,3,0,0 and did not move.

The about screen draws the version, so its stored picture and widget tree were
refreshed. One screen of twenty five was rewritten, which is what the writer
asking the guard's own verdict instead of comparing bytes was built to do. The
tree diff is one line and the text is 37 px narrower.

The site prints the version in its footer and in its JSON-LD block. Thirteen
pages, seventeen lines added and seventeen removed, every one of them carrying
the version and nothing else moved.

The README ships inside every release archive and its manifest example still
said 0.2.0, so that number had drifted through a whole release without being
noticed. Nothing holds it.

Folding the sections invalidated two mutation entries, both aimed at the rc1
link definitions. Both reported SKIP, which is the shape that reads as proven,
and the staleness check is the only thing that says otherwise. Repointed and
run: three mutations named by these guards, three caught.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* docs: the run lock has a second effect, on a run that fills the disk

Found on 2026-09-09 while closing 0.3.0, by the pre-release ritual reporting a
failure about a change that is an improvement.

The run lock moved the claim on the manifest name from after the last file to
before the first one, so the manifest has a place reserved whatever happens to
the directory afterwards. The entry describing that said what it does for two
runs competing for one directory and stopped there.

It does something else for a run nothing is competing with. Measured in a
container with room for twelve names, the same command through three binaries:
0.2.0 and 0.3.0-rc1 both end with exit code 5, print thirty files they could
not produce, write no manifest, and say that clearing the directory is a job by
hand. This release ends with the partial code 8 and writes a manifest, so
"tfg cleanup" can remove what the run left rather than leaving it to a person.

That is the better outcome and both codes follow the frozen table - what moved
is which of them the situation produces, and somebody's CI can be reading it.
The entry says so now.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Author: donislawdev

CHANGELOG.md

@@ -527,7 +527,7 @@ interrupted. One entry per file:
 ```json
 {
   "manifest_version": "1.0",
-  "tool": { "name": "testing-files-generator", "version": "0.2.0" },
+  "tool": { "name": "testing-files-generator", "version": "0.3.0" },
   "run": {
     "id": "run_b359aa8d94",
     "seed": 0,

README.md

@@ -50,12 +50,12 @@ BEGIN
         BEGIN
             VALUE "CompanyName", "DonislawDev"
             VALUE "FileDescription", "Generates test files for QA, from the command line"
-            VALUE "FileVersion", "0.3.0-rc1"
+            VALUE "FileVersion", "0.3.0"
             VALUE "InternalName", "tfg"
             VALUE "LegalCopyright", "Copyright (C) 2026 DonislawDev. GNU GPL version 3."
             VALUE "OriginalFilename", "tfg.exe"
             VALUE "ProductName", "Testing Files Generator"
-            VALUE "ProductVersion", "0.3.0-rc1"
+            VALUE "ProductVersion", "0.3.0"
         END
     END
     BLOCK "VarFileInfo"

cmd/tfg-gui/rsrc_windows_amd64.syso

@@ -30,7 +30,7 @@
 											<container size="820x39">
 												<widget pos="6,0" size="808x39" type="*widget.Label">
 													<widget size="808x39" type="*widget.RichText">
-														<text bold pos="6,6" size="317x27" textSize="20">Testing Files Generator 0.3.0-rc1</text>
+														<text bold pos="6,6" size="280x27" textSize="20">Testing Files Generator 0.3.0</text>
 													</widget>
 												</widget>
 											</container>

cmd/tfg/rsrc_windows_amd64.syso

@@ -49,12 +49,12 @@ BEGIN
         BEGIN
             VALUE "CompanyName", "DonislawDev"
             VALUE "FileDescription", "Generates test files for QA"
-            VALUE "FileVersion", "0.3.0-rc1"
+            VALUE "FileVersion", "0.3.0"
             VALUE "InternalName", "tfg-gui"
             VALUE "LegalCopyright", "Copyright (C) 2026 DonislawDev. GNU GPL version 3."
             VALUE "OriginalFilename", "tfg-gui.exe"
             VALUE "ProductName", "Testing Files Generator"
-            VALUE "ProductVersion", "0.3.0-rc1"
+            VALUE "ProductVersion", "0.3.0"
         END
     END
     BLOCK "VarFileInfo"

cmd/tfg/tfg.rc

@@ -7,25 +7,32 @@ package version
 // Version is written into every manifest. A manifest without it cannot
 // explain a hash mismatch after an upgrade.
 //
-// Set to 0.1.0 by the owner on 2026-08-02, raised to 0.2.0 on 2026-08-28 and
-// to 0.3.0-rc1 on 2026-09-03, every one of them by the owner. It stopped being
-// an internal number the day 0.1.0 was published: this is what somebody
-// compares their build against when a hash they stored months ago does not
-// match.
+// Set to 0.1.0 by the owner on 2026-08-02, raised to 0.2.0 on 2026-08-28, to
+// 0.3.0-rc1 on 2026-09-03 and to 0.3.0 on 2026-09-09, every one of them by the
+// owner. It stopped being an internal number the day 0.1.0 was published: this
+// is what somebody compares their build against when a hash they stored months
+// ago does not match.
 //
 // 0.2.0 was a minor bump that moved no bytes. This one moves them, and before
 // 1.0 the minor is where that goes - D11 and immutable rule 3 ask for a bump,
 // not for a particular digit. Six formats have different bytes under Go 1.27,
-// a log advances through time, a GIF moves, and a CSV quotes only the fields
-// that need it. The changelog lists each one and says whether there is a way
-// back to the old bytes.
+// a log advances through time, a GIF moves, a CSV quotes only the fields that
+// need it, and the padding of a ZIP, a TAR.GZ and a WAV is drawn eight bytes
+// at a time instead of one. The changelog lists each one and says whether
+// there is a way back to the old bytes.
 //
-// The suffix is not decoration and it is not spelled freely. The release
+// The absence of a suffix is a decision rather than tidying up. The release
 // workflow marks a release as a prerelease when the TAG NAME carries a hyphen,
-// so 0.3.0rc1 would have gone out as the latest stable release. The changelog
-// section has to be spelled the same way, because the workflow greps for a
-// heading naming exactly this string before it will build anything.
-const Version = "0.3.0-rc1"
+// which is what kept 0.3.0-rc1 off the front page and out of "latest" while it
+// was the newest tag. Dropping the suffix is what puts this build there, and
+// 0.3.0rc1 would have gone out as the latest stable release by accident.
+//
+// The changelog section has to be spelled the same way as this string, because
+// the workflow greps for a heading naming exactly it before it will build
+// anything. The entries that shipped as 0.3.0-rc1 were folded into the 0.3.0
+// section on 2026-09-09 for the same reason the version has one place: someone
+// upgrading from 0.2.0 needs one list of what changed, not two.
+const Version = "0.3.0"
 
 // LicenceNotice is what "tfg license" prints and what the window's about
 // screen shows.

internal/guard/testdata/screens/about.png

@@ -56,7 +56,7 @@ <h1>That page is not here</h1><p class="lead">The address you followed does not
 <footer class="footer">
   <div class="wrap footer-inner">
     <div class="footer-col">
-      <p class="footer-brand">Testing Files Generator 0.3.0-rc1</p>
+      <p class="footer-brand">Testing Files Generator 0.3.0</p>
       <p class="muted">Test files for QA, at any exact size, with a manifest that states how your system should react to each one.</p>
     </div>
     <div class="footer-col">