STORY NOTES
===========

Premise
-------
Ace and Jack confront a duplicate listing and a one-issue publishing offset.
They repair the sequence and send ISSUE-005 through creation, FTP/Files, and
Gopher as a complete pre-flight test for NITETIME.NET.

Continuity
----------
This issue begins the garage action promised by ISSUE-004. Ace and Jack retain
their established appearance and roles: Ace keeps the process moving with
optimism, while Jack diagnoses faults and verifies each checkpoint.

The publishing errors are part of the public story. Success means ISSUE-005
exists in Files and appears once, in order, on Gopher. The comic depicts that
desired path as working; the actual archive package remains the machine-test
artifact that lets the external synchronization and publisher prove it.

Important visual details
------------------------
Release files form a pre-flight packet. FTP/Files and Gopher are checkpoints
on one physical line. The final aircraft combines old computers, file cabinets,
radio hardware, cables, wooden wings, and ordinary garage fabrication.

Easter eggs
-----------
The carved gopher prop returns wearing aviator goggles. ISSUE-005 visibly
contains comic.png, README.txt, MANIFEST.json, and SHA256SUMS.txt. The .net
mug remains on the opening workbench.

Possible future hooks
---------------------
If the publishing aircraft truly flies, the garage can turn from test facility
into mission control. Future releases may explore what NITETIME.NET transmits,
finds, or brings home once the distribution path is dependable.