I retained your changes to .test-env and my recent changes.  They
might be trying to solve the same problem though, and maybe you can
remove yours now.  My changes make it so that the indexer and conduit
built during CI tests use the SDK with the changes made in the PR
under test.  The previous situation was horrible - you would make
changes to the SDK, but those changes were not used by the
indexer/conduit that were built while testing your changes!  That
might be what you were dealing with too.

chore: frontend: seed localnet with frac-delegation data

feat: frontend frac delegation

The PR workflow pins CI_E2E_FILENAME to a commit hash, so its block data
is frozen and cannot surface encoding changes in go-algorand. New block or
transaction fields are fatal rather than ignorable, because the SDK decodes
with ErrorIfNoField set, so an unknown map key aborts block import. The
unit tests cannot catch it either: they encode and decode with the same SDK
structs, which round-trips regardless of what algod puts on the wire.

feat: fractional user delegation, using the gGov registry

Conflicts in the election ready-check and results mapping resolved by keeping
this branch's wording (veto, terms.items) alongside the incoming branch's logic
(trim-based candidate-name fallback, allBodiesPresent gate). assignmentWarnings
stays a named binding: the page-level Callout in ManagePeriodDetail reads it.