[Feature][Medium] Replace hardcoded node IDs in peer script and document upgrade history

[numbers-official]

Summary

Two maintainability improvements to prevent stale configuration and improve operational clarity.

Findings

1. Hardcoded node IDs in info.peers.sh will become stale

File: api/info.peers.sh, lines 10-16 and 27-29

The script has hardcoded node IDs for both Snow (testnet, 5 nodes) and Jade (mainnet, 1 node). When validators are rotated or decommissioned, this script silently returns empty or misleading results. The script also queries public Avalanche API endpoints directly rather than using the configurable env.sh, inconsistent with other API scripts.

Fix: Dynamically fetch current validators using platform.getCurrentValidators and extract node IDs, or accept node IDs as command-line arguments. Also source env.sh for consistency:

SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
source "${SCRIPT_DIR}/env.sh"

2. Upgrade.json entries lack rationale documentation

Files:

• avalanchego/configs/chains/2oo5UvYgFQikM7KBsMXFQE3RQv3xAFFc8JY2GEBNBF1tp4JaeZ/upgrade.json
• avalanchego/configs/chains/2PDRxzc6jMbZSTLb3sufkVszgQc2jtDnYZGtDTAAfom1CTwPsE/upgrade.json

Both files contain precompile upgrades with timestamps that have already passed. The testnet file has a complex enable-then-disable-after-20-minutes pattern for contractDeployerAllowListConfig with no inline documentation. New operators have no way to understand the purpose or outcome of these entries.

Fix: Add a companion UPGRADE_HISTORY.md in the configs directory documenting each upgrade with rationale, execution date, and outcome. Update avalanchego/configs/README.md to describe the current state of precompile configurations.

Impact

• Peer monitoring could return stale/incorrect results after validator rotation
• New operators face confusion when deploying nodes with undocumented past upgrades

Generated by Health Monitor with Omni

[numbers-official]

已重構 api/info.peers.sh：\n- NodeID 集中到 SNOW_NODE_IDS / JADE_NODE_IDS 陣列（一個地方更新即可）\n- 加入 # Last reviewed: 2026-04-16 維護時間戳\n- 加入說明：當 validator 節點異動時需更新此檔\n- 改用 silent curl（-s 減少 output 噪音）\n- upgrade history 記錄建議在 README 的版本表格中追蹤（avalanchego/subnet-evm 版本已在 README 對應段落維護）