Note

Medium Risk
Changes remote config decode, persistence inputs, and signature-verification interaction for RC Container responses; behavior is covered by new tests but alters when corrupt inline blobs vs invalid config fail requests.

Overview
RC Container parsing is split from remote-config semantics. RCContainer now only structurally indexes wire-order elements and elementsByChecksum; it no longer treats element 0 as config, requires a config element, or rejects payloads whose checksum does not match during parse. Checksum verification moves onto RCContainer.Element via validateChecksum() / isChecksumValid().

Remote config owns validation policy through a new RemoteConfigContainer type (also the HTTP response body for /v2/config). It requires a first element, validates only the config element’s checksum, and exposes remaining elements as inlineContentElements without checksum enforcement at decode time—so structurally valid but corrupt inline blobs can still be returned while a bad config fails decoding. RemoteConfigManager, fetch results, and signature context now use configElement / RemoteConfigContainer instead of RCContainer.config.

Signature verification behavior shifts for inline corruption: tests now expect a corrupted non-config payload not to fail the HTTP response (signing still uses the config checksum), whereas config checksum mismatch still fails typed parsing.

^{Reviewed by Cursor Bugbot for commit f87390e. Bugbot is set up for automated code reviews on this repo. Configure here.}