Several bases write their standalone VAE / text encoder into the shared
`metadata.vae` and `metadata.qwen3_encoder` fields but recall them into their
own params slot. The generic handlers did not account for that:

- `VAEModel` excluded z-image, flux2 and krea-2 but not anima, so an Anima
  image rendered a duplicate VAE row and additionally wrote its VAE into the
  shared `params.vae` slot, which no Anima graph reads.
- `Qwen3EncoderModel` had no base gate at all while dispatching hard into the
  Z-Image slots, so Anima and FLUX.2 Klein images pushed their encoder into
  `zImageQwen3EncoderModel` and cleared `zImageQwen3SourceModel` on the way.
- The Anima handlers gated only on the currently selected base, never on the
  image's own `metadata.model.base`, so a Krea-2 image recalled while Anima was
  selected wrote its VAE into the Anima slot.

Replace the growing `base !== 'x' && ...` chain with a documented
`BASES_WITH_DEDICATED_VAE_HANDLER` set, rename `Qwen3EncoderModel` to
`ZImageQwen3EncoderModel` and gate it on z-image, and harden both Anima handlers
with `assertMetadataModelBase` (plus a base assert on the VAE, which is
base-identified - the encoder is variant-identified, so it deliberately gets
none).

The same slot mismatch existed for FLUX.1, whose VAE lives in `params.fluxVAE`:
its recall silently landed in `params.vae` and had no effect on generation. Add
a dedicated `Flux1VAEModel` handler for it.

Finally, `AnimaVAEModel`, `AnimaQwen3EncoderModel`, `Flux1VAEModel` and the
three Z-Image handlers were missing from IMAGE_METADATA_ACTION_HANDLERS, so
those parameters had neither a row nor a per-parameter recall button. List them,
and add a guard test that diffs the UI list against the handler registry with an
explicit allowlist, so the list cannot drift behind again.

VAE and text-encoder handlers that read a shared metadata field
(`vae`, `qwen3_encoder`, `qwen3_source`) checked only the currently
selected base, not where the image came from. Viewing one model's
image while another base was selected could write a foreign model
into the live slot, and in the Z-Image case silently clear the
user's Qwen3 source selection.

All six affected handlers now assert `metadata.model.base` in
addition to the selected base.

Also widen the Anima VAE slot to FLUX VAEs. The Anima model loader
carries no `ui_model_base` on its VAE input and both `anima_l2i`
and `anima_i2l` branch explicitly on `FluxAutoEncoder`, so a
workflow-built Anima image may legitimately record one. This needs
a separate `isAnimaCompatibleVAEModelConfig`: `isAnimaVAEModelConfig`
also feeds Krea-2's VAE pool and must stay base-driven.

The Anima model loader takes any VAE the backend can decode with — an
Anima-base (Wan/QwenImage) VAE, a FLUX VAE, or a plain Wan VAE in the
16-channel A14B geometry. The frontend gated on base alone, so a
workflow-built Anima image recording a Wan VAE could not recall it and
recall silently left the stale VAE in place.

Gate on the backend geometry instead: isAnimaCompatibleVAEModelConfig
now also accepts Wan VAEs with latent_channels === 16, and rejects the
48-channel Wan2.2-VAE (TI2V-5B), which is the same AutoencoderKLWan
class but a different latent space. Submodels stay out — a main model's
bundled VAE carries no latent_channels, so its geometry is unverifiable.

Since latent_channels is lost in ModelIdentifierField, AnimaVAEModel now
gates on the full model config: parseModelConfig is split out of
parseModelIdentifier, which becomes a thin wrapper over it. The
resolution order (key, then hash, then name/base) and its fallthrough
behaviour are unchanged.

isAnimaVAEModelConfig stays base-driven — Krea-2 draws its own VAE pool
from it and must not be offered FLUX or Wan VAEs.

Addresses review 4987208275 on invoke-ai#9489.

Metadata handlers gate on the currently selected base, which they read
imperatively via `selectBase(store.getState())` inside `parse` — they have
to, because parsing also happens outside React, in recall-all and in
hotkeys. The datum hooks depended only on `[metadata, handler, store]`, so
a row carried the verdict of whichever base was selected when it mounted,
and the metadata viewer stays open across model switches. Opening Anima
metadata under another model and then recalling MainModel left the Anima
VAE and encoder rows hidden; switching away after a row appeared left a
live recall button pointed at a slot no longer in play.

The three hooks now subscribe to the selected base and reparse when it
changes.

That reparse is asynchronous, so a click can still land while a stale row
is on screen. Recalls therefore re-run the handler's own gate at click
time: `recallIfStillValid` parses again and dispatches only if the gate
still admits the metadata. It recalls the value the row displays, not the
reparsed one — a collection row owns a single item, while `parse` returns
the whole set.

Fixing the hooks alone would have changed nothing: `SingleMetadataParsed`
and `CollectionMetadataParsed` called `handler.recall` / `handler.recallOne`
directly and resolved the store themselves, and the hooks' `recall`,
`recallAll` and `recallOne` had no callers anywhere. The row components now
take the hook's validating callback instead, which is the only recall path
left outside `parsing.tsx`.

Tested through `recallIfStillValid`, which is exported as a plain function
for that purpose: it recalls under a matching base, does nothing after the
base moves on, does nothing when provenance fails, and passes the row's own
value through. The reparse half is not covered — the project has no
testing-library or DOM environment and does not do UI tests, so it would
need a new dev dependency to assert.

selectFluxVAEModels lost its last consumer when the FLUX.1 and Z-Image VAE
defaults moved to selectFlux1VAEModels. Removing the selector also leaves
isFluxVAEModelConfig unused, which knip flags in turn - both go.

…ance

Nothing reconciled params.animaVaeModel / params.animaQwen3EncoderModel when the
model list changed, so uninstalling a selected component left a dangling key that
only surfaced as a failed generation - both slots are required by buildAnimaGraph.
Add handleAnimaComponents, built on a pure getAnimaComponentUpdates mirroring the
Krea-2 sync, with the same native-over-fallback preference as the modelSelected
listener. A compatible FLUX/Wan VAE survives a refetch rather than being swapped
for the native one.

The generic VAEModel handler also gated on the selected base alone, so an image
from a dedicated-slot base viewed with no main model selected fell through to it
and offered a recall into the dead params.vae. Gate on the image's own base too.