Wigo 1.0.1

[carsso]

Five things, four of them found by people using 1.0.0.

Merging this publishes the release. VERSION is 1.0.1 and no v1.0.1
tag exists, so once the CI is green on master the tag, the GitHub release with
the three .deb, and the multi-arch image follow on their own.

What is in it

A host's own status reaches its timeline. Only Down and Up ever wrote a
host level row, so a machine that never stopped answering had an empty band and
the screen said nothing known over that window about one it had been watching
for a month. Diagnosed against a real fleet: the host timeline answered 0
changes where the probe timeline answered 5.

The whole tree is walked rather than the host being updated — a master of
masters sees the hosts two levels down only inside their trees, and hooking the
update alone left exactly those with an empty band.

The history of the hosts that push. They cannot be asked anything, so they
had no graphs at all and the API answered a 501 explaining why. Their
measurements arrive with every push and were dropped; they are kept now, under
the name they came from. Only newer ones: a client pushes every ten seconds for
a probe that runs every minute, and writing each arrival stored one measurement
six times.

The screen says which setting is refusing a change. It printed set
AllowWriteActions in [Http] whatever the reason, so a push client that had
simply not set AllowRemoteControl sent its operator editing the wrong file on
the wrong machine.

The timeline tooltip no longer shrinks towards the right edge. An
absolutely positioned box with only a left offset is squeezed into whatever room
is left beside it: the same tooltip measured 556px wide on the left of the band
and 192 on the right, wrapping into twice the height.

needrestart looks at services, and names them. It ran with -k alone, so it
only ever checked the kernel, and answered restart not required on the exit
code that means the opposite.

Two bugs the live runs caught

RecomputeStatus zeroed its field before building it back up, and a concurrent
reader recorded that nought as a real transition to ERROR. And the memory of
where each host stood was lost on restart, cutting every band with a fresh
never watched — it is read back from the database now.

Host.Status is still written without synchronisation. This makes it a single
assignment, so a reader sees the old value or the new one rather than an
intermediate, but the formal race predates this and is not addressed here.