Initialize and document the deployed testnet registry contract

[priscaenoch]

Problem

The explorer/registry contract is deployed to testnet (CBKPNRQ4D3KTAAE7MMJ4HL6JNF2J2EBG2PSSRW4YHOMHTRHUU734CFWJ) but init(admin, max_events) has not been invoked, so the registry and event ledger are not usable: submit_event, register_contract, and the admin-gated functions require an admin that is not yet set. The deployment records the contract ID but not its initialization state.

What needs to be done

• Document the post-deploy initialization flow in DEPLOYMENTS.md: the init call, the chosen admin address, and the max_events value.
• Add the init invocation to build-and-deploy.sh (or a separate initialize.sh) using the Stellar CLI, guarded so it is not re-run against an already-initialised contract.
• Execute init against the deployed testnet contract and record the resulting state (admin, max_events) in DEPLOYMENTS.md.

Files

• DEPLOYMENTS.md
• build-and-deploy.sh (or new initialize.sh)

Acceptance deliverables

• The deployed registry contract is initialized on testnet with a documented admin and max_events.
• The initialization step is scripted and idempotent.

Tests to pass

• A dry-run of the init script against a freshly deployed contract succeeds and is a no-op on an already-initialised one.

[grantfox-oss]

🦊 GrantFox — @dreamgenies has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #3)
2. Your PR will be reviewed by the octraban maintainers

Good luck! Track your progress on GrantFox.