Tracking: prepare and manage release_v4.8.2 branch

[halibobo1205]

This issue is to coordinate the creation and tracking of the release_v4.8.2 branch from develop.

Branch Details

• Version: v4.8.2
• Branch to create: release_v4.8.2
• Base branch: develop

Tasks

• Create release_v4.8.2 branch from develop
• Push final PRs to release_v4.8.2 (e.g., version bump, changelog, fixes, features)
• Perform QA and testing on release_v4.8.2
• Merge release_v4.8.2 back to master when testing is complete
• Tag GreatVoyage-v4.8.2(Pyrrho) on master and release
• Merge master back to develop (if applicable)

Notes

Once the release_v4.8.2 branch is created, it will act as the staging area for all final updates and fixes for this release.
Any non-release-related changes should continue in develop.

PRs without Issue

• ci: add multi-platform build tests and system-test workflows #6574
• fix(docs): github issue template #6572
• refactor(config): remove unused config files #6566
• refactor(config): extract ConfigKey and remove testnet config #6565
• ci: enhance PR lint and add PR guidelines to CONTRIBUTING.md #6564
• ci: make build job depend on PR lint check #6559
• fix readme typo and format #6556
• refactor: move test constant out of production code and rename NET_CONF #6555

[halibobo1205]

Please leave a message here if there are any issues or features you’d like to propose for the next version.

[waynercheung]

Proposing to include the fix for #6568 in v4.8.2.
Issue: getaccount and related APIs return value as a numeric type (int64), which exceeds JavaScript's safe integer range (2^53 - 1). JS clients using JSON.parse() silently lose precision on large balances.

Solution agreed in #6568: Add a companion value_string field (string representation of the same int64) to avoid breaking existing consumers while resolving the precision issue.

The fix is backward-compatible (additive only) and low-risk, which makes it a good candidate for a patch release. Please let me know if this should be tracked here or handled separately.

[halibobo1205]

Hi, for the first task, we will create the release_v4.8.2 branch from develop.
The difference between develop and master can be found here.
Is the develop branch in a satisfactory state for the next release?
If there is any problem, please list it here.
If not, we’re planning to create the branch in two days.

[waynercheung]

Proposing to include the fix for #6547 in v4.8.2.

[xxo1shine]

Proposing to include the fix for #6546 in v4.8.2.