Fix config drift 244

[Mosas2000]

Fix Config Drift (Closes #244)
Successfully implemented a centralized configuration system with 30 professional commits on branch fix-config-drift-244.

Implementation Summary
Problem Solved:

Contract configuration was scattered across multiple files with inconsistent values
config.ts
had wrong contract name (sprintfund-core instead of sprintfund-core-v3)
Scripts had hardcoded contract addresses and names
No validation to catch configuration drift
Solution Implemented:

Centralized Configuration (contract-config.json)

Single source of truth for all contract settings
Includes contract address, name, principal
Network configurations for mainnet/testnet
Legacy contract information
Configuration Loaders

JavaScript loader:
contract-config.js
TypeScript loader:
contract-config.ts
Helper functions for accessing config values
Validation and error handling
Updated All Files

Fixed
config.ts
contract name
Updated
config.ts
to use centralized config
Updated all scripts: create-proposal, stake, call-logger, withdraw-legacy
Updated shell script: create-test-proposal.sh
Updated .env.example to include contract name
Validation & Automation

validate-config.js

• Checks config consistency
  update-config.js
• Helper to update config files
  GitHub Actions workflow for CI/CD validation
  Unit tests for config loader functions
  Documentation

CONFIGURATION.md - Comprehensive configuration guide
MIGRATION_CONFIG.md - Migration guide for developers
CHANGELOG_CONFIG.md - Change log for config system
.contract-config.md - Config file documentation
Updated CONTRACT_VERSIONS.md with new approach