docs(base-contracts): fix Sepolia batch sender address

[kriss39]

What changed? Why?

One row on specifications/reference/base-contracts no longer matches what is on chain:

• Base Sepolia → Batch Sender: 0x6CDEbe94…3E47 → 0xfc56E727…8bA3. Sepolia SystemConfig.batcherHash() returns 0xfc56e727…, and that is the only address posting to the 0xff…84532 batch inbox right now.

Notes to reviewers

The mainnet AggregateVerifier change this PR used to carry is now in master via #2030 (0xeF9eCeA1…, which is what gameImpls(621) returns today), so it was dropped in the merge.

It is a read-only eth_call you can repeat:

# Sepolia SystemConfig 0xf272670e…6194, batcherHash()
cast call 0xf272670eb55e895584501d564AfEB048bEd26194 'batcherHash()(bytes32)' --rpc-url <sepolia>

Rebased on master after #2003. The Sepolia AggregateVerifier from #2003 (0xd702aaE6…) already matches gameImpls(621), so it is untouched. An earlier revision also removed the Sepolia FaultDisputeGame (Kona) row as a duplicate; that was wrong, 0x6dDBa09b… is registered for both game type 0 and game type 8, so the row stays.

The mainnet Batch Sender (0x5050f69a…) already matches batcherHash(). I left SystemDictator and the mainnet legacy OptimismMintableERC20Factory alone since those are judgement calls rather than wrong values.

How has it been tested?

node scripts/lint-mdx.js docs/specifications/reference/base-contracts.mdx and node scripts/validate-docs-structure.js pass.

Screenshots

N/A (table cell edits only)

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/2	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 1 Sum 2