A migration from a pre-PM venv carries the extras that venv held (matrix,
fal, ...) into PM's first generation. Those reached sync_venv as if the user
had requested them, so one that no longer builds (python-olm's vendored
libolm without a working cmake/C++ compiler) failed the whole sync. No
facts.json was written, the old venv is never deleted, and every later
`hermes update` re-scanned it, re-carried the same extra and failed the
same way: one optional extra bricked updates for good.
sync_venv now takes `carried`, the entries of `extras` that were carried
rather than asked for. When the sync fails with a build or resolver verdict,
pm.carried_extras proves core plus the requested extras build without them,
re-adds each carried extra on top of what fits, and syncs without the ones
that do not. A build verdict is recorded in declined-extras.json (with the
reason, so a later lazy-install refusal names the cause instead of a
`--without` nobody ran) and the operator is told which extra was left out and
to run `hermes pm install --extra NAME` to add it back. A download failure is
left out of this update but not recorded. Requested extras and core still
fail loudly. Both legacy callers (the source-launch sync and the historical
takeover) pass the carried list.
The streamed uv tail also keeps the build-backend marker now: a native
build's traceback runs past the 2000-character tail, so the failure read as a
fetch error instead of a BuildFailure verdict (this also hid plugin build
verdicts from plugin eviction).
Also fixes committed_venv's docstring: PM never deletes the in-tree venv.