[Imran2210]

Overview

This PR completes the carryover from Wave 9 issue #191 by recording the Stellar testnet deployment in the canonical deployment manifest, verifying its IDs, WASM hashes, deployment ledgers, and governance fields, and making manifest verification fail when Stellar data in the SDK or docs drifts from the manifest.

Related Issue

Closes #[carryover issue]

Changes

🧾 Manifest & Schema

• [MODIFY] deployments/manifest.json
  • Adds a Stellar testnet network entry with the canonical deployment and supported contract records.
• [MODIFY] deployments/schema/v1.json
  • Extends the schema so Stellar records validate IDs, WASM hashes, deployment ledgers, and governance fields.

🔧 Manifest Tooling

• [ADD] scripts/deployment-manifest/src/record/stellar.ts
  • Builds Stellar manifest records from the contract ID source.
• [MODIFY] scripts/deployment-manifest/src/manifest.ts
  • Wires the Stellar record builder into manifest generation and verification.
• [MODIFY] scripts/deployment-manifest/src/consumers.ts
  • Adds the SDK and docs consumer checks so verification fails on Stellar drift.

📄 Source Data

• [MODIFY] stellar/contract-ids.json
  • Holds the testnet contract IDs used as the source for the manifest record.

Verification Results

Manifest verification now compares Stellar IDs, WASM hashes, deployment ledgers, and governance fields against the SDK and docs, and fails on any mismatch.

Acceptance Criteria	Status
Canonical Stellar testnet deployment and supported contracts recorded	✅ Added to deployments/manifest.json
IDs, WASM hashes, deployment ledgers, and governance fields verified	✅ Checked by schema and manifest tooling
Manifest verification fails when SDK or docs Stellar data drifts	✅ Enforced in consumers.ts

Closes #230