SFTOSS32 v1.05 - KNOWN ISSUES AND DEFERRED WORK
===============================================

1. BODY-TO-TEARLINE DISPLAY SPACING
-----------------------------------
SFToss32 emits two true empty packet lines before the outbound tearline.
Inspection of the generated packet confirmed the correct bytes. On the tested
production route, downstream hub/import/display processing removed the blank
lines, so the tearline displayed immediately after the final body line.

This is cosmetic and does not affect routing, threading, private attributes,
delivery or message-base safety. No nonblank placeholder is forced into FTN
messages. The downstream normalization point remains to be identified.

2. INTERNAL BUILD LABEL
-----------------------
The exact promoted executable identifies itself as "v1.05 Beta 5" in startup
logs and SFTOSS.BSY. This was retained deliberately so the release-review
package contains the exact production-tested binary. The network tearline is
"--- sftoss32 1.05".

3. WINDOWS XP FIELD TEST
------------------------
The target baseline is Windows XP SP2 through Windows 10 32-bit. The exact
v1.05 executable was live-tested on Windows 7 32-bit. An earlier build was
reported working on XP SP2, but this exact binary still needs an XP field test.

4. OTHER DEFERRED ITEMS
-----------------------
- Packet splitting for unusually large outbound scans.
- TOSSER.LOG and processed-file rotation.
- Broader CP437/Unicode conversion policy.
- Authentic Spitfire IDX name-CRC algorithm research. The current source uses
  a placeholder CRC-32 for FromWhoCRC and ToWhoCRC.
- Full write-ahead journaling for instantaneous power loss.
- Console-close, logoff and shutdown cleanup were implemented but not each
  individually live-triggered; Ctrl+C cleanup passed on Windows 7.

These items are documented rather than silently assumed. None invalidated the
completed production message, privacy, threading or safety tests.
