release: close the changelog for 0.2.0 and raise the version (#17)

* release: the changelog closes for 0.2.0 and everything that says a version agrees

The owner raised the version on 2026-08-28 and asked for the changelog to be
put in order first, because the unreleased section had grown its four kinds in
the order they happened to be written: Breaking, Fixed, Added, Changed.

Breaking, Added, Changed, Fixed now, and closed into a dated 0.2.0 section with
nothing left under Unreleased. That is not tidying: the release workflow refuses
to build when a version has no section, and refuses again when anything is left
under Unreleased, because those are changes that would go out undescribed.

A minor bump rather than a major one, and here that is a claim about other
people's CI. What changed under Breaking is which names and sizes this tool
agrees to produce - a name Windows cannot store, two names a Mac keeps as one
file, a bare nul - not what it writes once it agrees. The machine answer is
internal/guard/testdata/generator-golden.json, which git says is byte for byte
the file v0.1.0 shipped with.

A version lives in five places and four of them are copies, so all four moved
together. internal/version is the one the owner sets. The two Windows resource
scripts carry it because a .rc cannot ask a Go constant, and their compiled
.syso files are committed because the toolchain links any it finds and runs no
generator - so both were rebuilt with windres, and the guard that reads the
version back out of the compiled resource is what would have caught it if only
the scripts had been edited. The site renders it from internal/version, so
web/public was regenerated: the diff is 29 lines and not one of them is
anything other than a version number.

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

* guard: the About screen's stored picture says 0.2.0 as well

The version is on that screen, so raising it made the stored tree and the
stored picture stale. Three CI jobs went red on one cause - the suite on ubuntu
and on windows, and the coverage gate, which runs the same suite. macOS passed,
because the screen guard is skipped there.

The diff is one line: "Testing Files Generator 0.1.0" becomes 0.2.0, in
about.xml, and about.png with it. Nothing else in any of the twenty five
screens moved.

Missed here because the version was checked against the places that carry it as
a NUMBER - internal/version, both resource scripts, the site - and the About
screen carries it as a sentence a person reads.

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

---------

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

Author: donislawdev

CHANGELOG.md

@@ -39,8 +39,8 @@
 1 ICON "../../internal/gui/icon/chickpea.ico"
 
 1 VERSIONINFO
-FILEVERSION 0,1,0,0
-PRODUCTVERSION 0,1,0,0
+FILEVERSION 0,2,0,0
+PRODUCTVERSION 0,2,0,0
 FILEOS 0x40004L
 FILETYPE 0x1L
 BEGIN
@@ -50,12 +50,12 @@ BEGIN
         BEGIN
             VALUE "CompanyName", "DonislawDev"
             VALUE "FileDescription", "Generates test files for QA, from the command line"
-            VALUE "FileVersion", "0.1.0"
+            VALUE "FileVersion", "0.2.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.1.0"
+            VALUE "ProductVersion", "0.2.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="280x27" textSize="20">Testing Files Generator 0.1.0</text>
+														<text bold pos="6,6" size="280x27" textSize="20">Testing Files Generator 0.2.0</text>
 													</widget>
 												</widget>
 											</container>

cmd/tfg/rsrc_windows_amd64.syso

@@ -38,8 +38,8 @@
  * the fourth number of FILEVERSION is a zero rather than a build counter.
  */
 1 VERSIONINFO
-FILEVERSION 0,1,0,0
-PRODUCTVERSION 0,1,0,0
+FILEVERSION 0,2,0,0
+PRODUCTVERSION 0,2,0,0
 FILEOS 0x40004L
 FILETYPE 0x1L
 BEGIN
@@ -49,12 +49,12 @@ BEGIN
         BEGIN
             VALUE "CompanyName", "DonislawDev"
             VALUE "FileDescription", "Generates test files for QA"
-            VALUE "FileVersion", "0.1.0"
+            VALUE "FileVersion", "0.2.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.1.0"
+            VALUE "ProductVersion", "0.2.0"
         END
     END
     BLOCK "VarFileInfo"

cmd/tfg/tfg.rc

@@ -7,12 +7,17 @@ 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. It is an internal number: nothing
-// has been released, the repository is private, and both changelogs keep
-// everything under [Unreleased] because there is no release to point at. What
-// it buys today is that a manifest found later says which line of the tool
-// produced it, which "0.0.0-dev" could not.
-const Version = "0.1.0"
+// Set to 0.1.0 by the owner on 2026-08-02 and raised to 0.2.0 by the owner on
+// 2026-08-28. 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.
+//
+// A minor bump rather than a major one, and here that is a claim about other
+// people's CI rather than a habit - D11 and immutable rule 3. What changed
+// under Breaking is which names and sizes this tool AGREES to produce, not what
+// it writes once it agrees. The machine answer to that is the golden hashes in
+// internal/guard/testdata, which are byte for byte the ones 0.1.0 shipped with.
+const Version = "0.2.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.1.0</p>
+      <p class="footer-brand">Testing Files Generator 0.2.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">

internal/guard/testdata/screens/about.xml

@@ -193,7 +193,7 @@ <h2>A real file of that format, at exactly the size you asked for</h2>
     through that and four other jobs it is built for.
   </p>
   <div class="cta">
-  <a class="button primary" href="https://github.com/donislawdev/TestingFilesGenerator/releases/latest">Download 0.1.0</a>
+  <a class="button primary" href="https://github.com/donislawdev/TestingFilesGenerator/releases/latest">Download 0.2.0</a>
   <a class="button ghost" href="https://github.com/donislawdev/TestingFilesGenerator">View the source</a>
 </div>
 <p class="cta-note">Free and open source, GPL-3.0. Nothing to sign up for. The binaries are not signed yet, so your system will warn you the first time - the release notes say what to expect.</p>
@@ -228,7 +228,7 @@ <h2>So which should you use?</h2>
 <footer class="footer">
   <div class="wrap footer-inner">
     <div class="footer-col">
-      <p class="footer-brand">Testing Files Generator 0.1.0</p>
+      <p class="footer-brand">Testing Files Generator 0.2.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">