SFPCKUSR32 v0.4.0 Beta 1 - Testing and Bug Reports
==================================================

This is a public beta for manual offline use. The safest first run is a
read-only preview on a current backup or recoverable copy.

RECOMMENDED TEST
----------------

1. Close every Spitfire node and maintenance utility.
2. Confirm the old SFPCKUSR.COM has been renamed or removed.
3. Run:

       SFPCKUSR.EXE /DEL /DRYRUN

4. Review the candidate list and confirm zero errors.
5. On a recoverable copy, run:

       SFPCKUSR.EXE /DEL

6. Require verified backup, complete commit, post-write PASS, released lock,
   zero errors, and exit code 0.
7. Start one node and test a normal caller login and message access.
8. Repeat with the real rule intended for routine maintenance.

PLEASE INCLUDE IN A REPORT
--------------------------

* Windows version and whether it is 32-bit or 64-bit.
* Spitfire version and node count.
* Exact SFPCKUSR.EXE command line.
* The complete SFPCKUSR32_REPORT.TXT section for that run.
* Number of users before, selected, removed, and retained.
* Whether the backup, commit, and post-write verification passed.
* Whether normal login and message access worked afterward.
* Any SFTOSS.BSY or *.SFPNEW file left behind.

Review logs before posting them publicly because caller names and paths may be
included.

VALIDATION STATUS
-----------------

The complete fixture suite passed for dry runs and writes using deleted-only,
/SEC, /OLD, OR, and AND rules; default and custom backups; exact DAT/PTR/LMR
compaction; no-op writes; active-caller and lock refusal; malformed-file
refusal; user #1 protection; and forced rollback.

Production validation by the project owner completed successfully for both
/DEL and /OLD=365. The /DEL run removed 12 of 200 records; the /OLD=365 run
removed 58 of 188 records. Both ended with verified backup, complete commit,
post-write PASS, zero warnings, zero errors, and exit code 0.

An outside sysop also completed a real deleted-record pack successfully,
removing 9 of 47 records with verified backup, complete commit, post-write
PASS, zero warnings, zero errors, and exit code 0.

The Beta 1 executable changes release-label and help/report wording only. The
validated selection, backup, packing, verification, and rollback logic is
unchanged from the closed-beta build.
