Convert the Fire Inspector to a News Vendor

Check for the weekend calculation with $g.batch

Create a logbook property for remembering visits, and the
visit_interval property, plus the status property, and a busy property.

Inspect only stores where the player is connected

Make sure the store is valid and open

Make sure the visit is not premature

Be careful to insure the player is still connected when their
turn comes.

Should the 'news visit' routine be called by the 'start'
routine?

The 'visit_due' routine makes sure a visit is not premature

Should there be an 'update_logbook' AFTER the visit, rather than
updating in the 'visit_due' routine?

For the visit, the news vendors should enter the stores from the
street and leave via the street

The response/reply scheme needs to be more general than the fire
inspector. A design for the conversation structure is needed. There should
be one for speaking to players, and one for speaking to other
news agents. See the <a href="./news-agent-speech.txt">requirements document</a>

A design for the news data structure is needed. It must include
dates, topics, and news.

Everyone might need to @create a child of $g.Newspaper_Agent

There will be a GeGeneric News Object with object number
#8965  (Generic News Object). We have created children of this, named, for
example News-1880-A for the first part of 1880.

The news will be stored as a list of lists in the .stories
property.

The format of the stories is stored in
$g.gen_news_object.stories

Column
Year: integer (range 1880 to 1886)
Month: integer (range 1 to 12, 0 if no month)
Day: integer (range 1 to 31, 0 if no day)
Headline: string (required to be non-empty)
Story: string (possibly empty)
Topics: Primary, Secondary, Tertiary, Person, Place