fix(orchestrator): refresh structured output after verify revision - #536

…ult (#537)

Follow-up to #536. `runConsensusCore()` tracks the parsed value so an accepted
verify revision can replace `output` and `structured` together, but the same
loop backs the standalone `runConsensus()`, where several proposer answers may
be joined into one string and no parsed value corresponds to the answer. That
path was returning a `structured` field the public `ConsensusResult` never
declared.

Drop it at the public boundary, and cover both halves of the verify contract:
an accepted revision replaces the pair, a rejected one preserves it. Credit
green3sf in CONTRIBUTORS.md for #536.

#546)

The published body was the changelog section and nothing else, so a reader
of a release page could not tell which packages shipped, how to install
them, or who contributed. green3sf landed #536 and #541 in 1.16.1 and the
release page credited nobody.

Three deterministic sections now follow the changelog section:

- `## Packages` names every workspace version and reports the ones this
  release left alone, derived by comparing the release commit's manifests
  against its first parent.
- `## Thanks` credits contributors from outside the project, resolved from
  the commits between the previous release tag and the release commit. Bot
  commits and the maintainer's own are excluded, and the section is omitted
  when nothing remains. Names are plain rather than mentions, because a
  published body that mentions an account notifies it.
- `## Install` is copy-pasteable.

The whole body is still composed before anything reaches the npm registry,
so a malformed changelog or an inconsistent manifest set keeps failing
ahead of publication rather than after it.

The previous tag is resolved from the release commit's first parent rather
than from HEAD. On an idempotent re-run this release's tag already exists,
and describing from HEAD would report an empty range and silently drop
every contributor from the body.