SimpleDeFence 0.1.3 beta

SimpleDeFence 0.1.3 beta

Everything on main since 0.1.2, in one installer. 0.1.2 remains usable; this
release adds no fix that makes it urgent to replace.

Changes

• A configuration that is present but refused now says so. Three things can make
  the service decline a config file it can plainly see: it cannot be opened at
  all (an ACL, or another process holding it), it fails its authentication tag
  (altered, truncated, or written under a different key), or it is in the
  superseded format on an installation that has already migrated away from it,
  which is refused as a downgrade rather than accepted. All three used to hand
  back exactly what a first run gets - default settings - with no log line and a
  status display reporting a healthy firewall. The firewall actually in force
  was not the configured one, and nothing anywhere said so. Each case is now
  written to the log, naming what was found and noting that the file was left
  alone, and raises a degraded state so the interface says the firewall is
  running on defaults rather than on your settings. The wording is translated
  into all sixteen interface languages.
• The file is still never rewritten or deleted in any of those cases, so a
  configuration refused for a reason you can fix stays there to be fixed.
• A configuration the pre-3.0 XML reader throws on is reported the same way. It
  throws rather than falling back, and that exception used to be caught and
  discarded, which is the same silence by a different route.
• The update descriptor advertises this release, so 0.1.2 installations will be
  offered it.

Verified

• The test suite passes: 209 tests, six of them new and covering each ending the
  configuration reader can reach, including the one where a file is present but
  locked - previously indistinguishable from no file at all.
• CI is green on the commit this installer was built from, across both toolchains
  and both configurations.
• The installer in this release was built from that same commit and reports
  version 0.1.3.

Not verified

• This installer has not been installed on a machine. 0.1.2's install and
  uninstall cycle was exercised end to end; nothing in this release touches the
  installer, the service lifecycle, or the control pipe, but that is reasoning
  rather than a test run.
• The new degraded-state banner has not been watched appearing in front of a
  live service holding a genuinely unreadable configuration. What is covered is
  the layer below it: the reader's verdict, under test, for each way a file can
  be refused.

Known issues

• On a standard user account the GUI runs unprivileged and cannot command the
  service; it says so and offers to restart elevated.
• The installer is not code-signed.