Six-seat zuss (8/9 seats), written under the blindness clause of
PREREG_v41-release-replicate.md 3a(3): methodology only, no session
values. Majority locks Option (a) - crop-shape is NOT part of the
synthetic-control hypothesis, because a synthetic crop null cannot
calibrate or gate the Falcon crop/SHAPE path (non-transfer); the interim
raw-line ruling becomes permanent under it. The minority Option (b) draft
(matched synthetic null family + planted-shape positive control with a
numeric fire condition) is kept in full with the founder decision
criterion, because the split is real. Takes force only as a dated
pre-registration after the release-replicate decision, in the ruled order.

Security Impact: document only, explicitly not in force; no rule changes
until adopted.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Moving pool state to a single accountInformation read on the registry left two
gaps where a pool the bulk request missed stayed missed.

`processPoolData` fell back on the presence of the entry, not on what it held. A
pool whose state came back partial decodes to `{}`, which is truthy, so it kept
the empty entry and returned no lastPayout - which the Status column renders as
"Payouts stopped".

`algodVer` lost its fallback entirely. It came off LocalPoolInfo, and
StakingPoolInfo now reads it only from the bulk map; the per-pool read inside the
metrics query keeps lastPayout and discards the algodVer it fetched. Any pool the
map lacks reported its node version as "--" for the rest of the session.

Both now gate on `isPoolGlobalStateComplete`. It tests lastPayout rather than the
field being displayed, because lastPayout is written when the pool is created -
stakingPool.algo.ts sets it to the creation round as the first epoch's baseline -
so every pool has one and its absence can only mean an incomplete read. Gating on
algodVer instead would have been wrong: it is only written once the node daemon
reports in, and 88 of MainNet's 283 pools legitimately have none, so keying on it
would re-read a third of all pools on every visit and still show "--".

The 1020 fixture claimed a missing lastPayout stood for "a pool that has never
paid out", which the contract does not do. It now models the case that does
occur - a pool whose daemon has never reported, so no algodVer - and the tests
around it cover the fallback firing on an incomplete entry and staying put on a
complete one.

Conflict in frac-delegation-sdk/src/registry/sdkReader.ts (imports only):
the incoming dual ESM/CJS build rewrote relative specifiers to carry .js,
while this branch added a FracInstanceCommitteeStanding type import for
getInstanceCommitteeStandings. Kept both — .js specifiers throughout,
including the new type import.

Docs: Add Transaction concepts page and examples

The /pools/$committeeId page from the design: how much of a committee's voting
power sits in staking pools and which pools those are, ranked, with the
AlgoQuarters behind each pool's power and how much of that stake voted. The
committee is the route rather than component state, so a composition is
linkable and shareable; /pools redirects to the current window. Retires the
stub href on the committee detail card, and lifts that card's composition bar
into a component the two share.

Serving it the way the card already did would have cost 373 algod requests
against a 62-instance registry: getExistingInstances is a box-map read plus an
existence lookup per instance, then a snapshot read per instance, then an
AlgoQuarters read per instance. So the registry now answers the whole question
itself.

logInstanceCommittees pages over its own instance ID range - dense, since
lastInstanceNumId only increments and instances boxes are never removed - and
inner-calls each instance's new getCommitteeStanding, which joins the committee
snapshot with its AlgoQuarters ledger where both boxes already are. That join
has to happen on the instance: committeeAq is keyed by the numeric ID only the
snapshot yields, so an outside caller cannot start the second read until the
first lands. Deleted instance apps are skipped on chain via app_params_get
rather than failing the page, which is what removes the per-instance existence
lookup the SDK was doing. An instance that never synced the committee is
reported with committeeNumId 0 rather than dropped, so absence stays provable.
373 requests become 2.

getInstanceCommittee is the singular counterpart, and the reason the struct
lands in the registry's ARC-56 - SDKs decode the log payload from generated
types instead of a hand-maintained copy, the same arrangement
logAccountVotingRecords already has. Page size is 32, from the same
unnamed-reference accounting as the existing paged log readers.

Two figures on the page are honest approximations of what the design asked
for. The liquid-vs-Reti filter reads the instance name, because FracInstance
records no kind; it is only offered when both buckets are populated and carries
a TODO for the contract-side fix. Turnout is AlgoQuarters-weighted - the share
of a pool's stake that cast an internal ballot in the newest period the
committee has opened - because a member-count percentage would need a read per
member.

The e2e spec added here has not run. Every contracts e2e spec currently dies in
algokit's composer with "Not an address", on an untouched checkout as much as
on this branch. scripts/verify-instance-committees.ts covers the same ground
with no vitest in the way, and passes against LocalNet.