Point the documentation at 0.1.0a8, and stop calling released work unreleased

[FlagshipDev]

The image 0.1.0a8 is published and this repository's own documentation was still pinning
0.1.0a7 and describing two shipped features as unbuilt. Both halves are fixed together because
they fail together: published-surface.json is recorded from the image, the pins name the image,
and a tree with one moved and not the other is red.

published-surface.json now records 28 commands read from ghcr.io/easybytehub/hullwork:0.1.0a8,
up from 26.

Pins moved: README.md, docker-compose.yml, docs/install.md, PRIVACY.md. Anyone following
the install instructions before this pulled the previous release.

Three documents described as pending what had just shipped:

• README.md said only the first of the three signal rows was in a release. Two are. Its error
  tracker row described Sentry's route as not landed yet; it now describes both routes together,
  with the gap they share — neither verifies a signature — rather than framing it as Sentry's alone.
• docs/status.md had spent a day naming the dependency signal's state and deliberately not its
  command, because a command a reader cannot run is an invitation to type it and be told it does
  not exist. It is nameable now for one reason: it is in an image you can pull. What the name does
  not say has been added — four real third-party repositories measured before release, one clean
  verdict, and that ratio is the feature rather than a defect in it. A tool that answered all four
  would be lying about three.
• docs/what-hullwork-is.md likewise, with the note that the rule did not soften when the release
  landed: the row changed because the artefact did.

The guard was checked by putting one pin back to 0.1.0a7: it fails naming the document and the
stale version.

Signed-off-by: Javier Miralles Rancaño 68760931+FlagshipDev@users.noreply.github.com