SFToss32 v1.07 Beta 1 - Test Plan
=====================================

TEST 1 - Loader and read-only diagnostics
1. Back up the existing installation.
2. Run SFTOSS32.EXE and confirm v1.07 Beta 1.
3. Run SFTOSS32.EXE -check.
GO: CFG, links, message bases, routes, and node status pass.

TEST 2 - Legacy CFG compatibility
1. Use a known-good flat single-link CFG.
2. Run -check, one supervised -toss, and one supervised -scan.
GO: behavior matches the pre-v1.07 single-link workflow.

TEST 3 - Multi-link parsing
1. Run -check with two or more named links.
2. Confirm AKA, hub, OUTDIR, password state, zones, and AREA count per link.
3. Confirm a no-password link omits PKTPW entirely.
GO: every summary and route matches the CFG.

TEST 4 - Inbound ownership and foreign-packet safety
1. Place a local-address packet and retain a foreign-address packet as control.
2. Run -toss once.
GO: local packet imports through the correct link; foreign packet is untouched.

TEST 5 - Outbound echomail isolation
1. Post one local message in an AREA owned by one link.
2. Pause mailer pickup and run -scan once.
GO: only that link publishes, with correct header, AREA, SEEN-BY, and PATH.

TEST 6 - NetMail zone routing
1. Create NetMail to a zone uniquely owned by one link.
2. Run -scan once.
GO: only that link publishes; message retains its true destination and has no
AREA, SEEN-BY, or PATH.

TEST 7 - Simultaneous links
1. Queue one message for each of two links.
2. Run one -scan.
GO: each link publishes independently into its own OUTDIR.

TEST 8 - Node and instance locks
1. Keep one caller online and start -scan.
2. While it waits, start a second -scan.
GO: first waits and aborts after five minutes if still busy; second is rejected
by SFTOSS.BSY; no mail is exported.

TEST 9 - UNKNOWN retry
1. Toss a local packet containing one known and one unmapped AREA.
2. Confirm known mail imports and unknown mail is saved under UNKNOWN.
3. Add the AREA uniquely to SFMCONF.DAT and one link, run -check, then -toss.
GO: saved mail imports and is removed only after a successful commit.

Run -check after every supervised write test and review TOSSER.LOG before
restoring automation.
