Noctuary 2.0.1

The near layer survives a preset change. A journey ran for twelve minutes without a single
event in the near field, on a preset whose pack should have brought one. Two faults met to make
that, and both are fixed.

Applying a preset begins by putting everything in its scope back to its default, so that what the
preset does not mention is not left over from what played before. The near layer was in that
scope. It should never have been: it is a bank of its own with its own selector, kept across sound
presets on purpose, and not one preset in the library carries a single fore_* key. Picking a
preset by hand applies at the Sound scope, which excludes it; a host's program change and every
journey step apply at Full, which did not. So the foreground was switched off, silently, every
time the piece moved on. What a preset clears is now a narrower question than what it may set:
a preset that names a near key still sets it.

The second half: the call that fetches the foreground a pack's artist table gives a preset stood
only at the end of the by-hand path. A crossfade never reached it, and a journey step crossfades.
It now sits on the path both take, so Auto works from a host and from a journey as it always did
from the browser. The offline renderer follows: --near-auto acted on the first step of a journey
and no other, which meant a render of a journey was not the take you heard.

Three checks were added and one rewritten. The self test witnesses that a full preset leaves the
layer standing, that everything outside it is still cleared, and that a preset naming the layer
still sets it. The host test measures both halves through the plugin: that a program change brings
the foreground its pack gives the preset, and that a program bringing none leaves the one that is
playing alone.

Nothing else changed. The instrument, the 14592 presets and the sample library are those of 2.0.0.