improve(cli): accurate live progress for sync-accounts

[igorls]

Why

Follow-up to #170. An operator running ./hyp-control sync accounts eos token.pcash saw the progress line stuck at 0/1 (0.00%) for the whole run even though it was working (Processed 448550 accounts). The bar was driven by completed-contract count under misleading field names (processedScopes/totalScopesToProcess actually counted contracts), so a single-contract sync only moves 0% → 100% at the very end.

Changes

• Rename processedScopes/totalScopesToProcess → completedContracts/totalContracts; remove the unused totalScopes.
• Track holder scopes processed per-contract (currentContractScopes) and overall (totalScopesProcessed), and surface the running holders scanned + balances counters — these move continuously.
• Show the contract currently in progress (currentContractIndex + 1) instead of only the last completed one.

The percentage stays contract-granular (the only total known up front — get_table_by_scope gives no cheap holder count), but the moving counters make long single-contract runs legible.

New output

single contract:
  [07:05:40] 0.0% | holders scanned: 433076 | balances: 435000 | contract 1/1 token.pcash (433076 holders) - current: s2hw24.pcash
multi-contract, mid-run:
  [07:05:40] 3.3% | holders scanned: 50000 | balances: 52310 | contract 5/120 eosio.token (1200 holders) - current: bu.klnk
finalizing:
  [07:05:40] 100.0% | holders scanned: 240000 | balances: 251000 | finalizing database writes...

No behavior change to the sync itself. tsc --noEmit passes.

[gemini-code-assist]

Code Review

This pull request refactors the progress tracking in AccountSynchronizer to use contract-based metrics instead of scope-based metrics, preventing the progress indicator from appearing stuck during long-running single-contract syncs. The review feedback highlights two issues: first, this.currentScope is not reset when transitioning to a new contract, which can display stale progress information; second, if this.totalContracts is zero, the progress status will prematurely display 'finalizing database writes...'. Code suggestions are provided to address both issues.

[gemini-code-assist]

When transitioning to a new contract, this.currentScope is not reset. As a result, the progress log will display the last processed scope from the previous contract as the current scope for the new contract until the first scope of the new contract is successfully fetched. Resetting this.currentScope to an empty string at the start of each contract avoids this stale/misleading status message.

Suggested change

	const contract = this.tokenContracts[i];
	this.currentContract = contract;
	this.currentContractIndex = i;
	this.currentContractScopes = 0;
	const contract = this.tokenContracts[i];
	this.currentContract = contract;
	this.currentContractIndex = i;
	this.currentContractScopes = 0;
	this.currentScope = '';

[igorls]

Applied in 74f1cce — reset this.currentScope = '' at the start of each contract.

[gemini-code-assist]

If this.totalContracts is 0 (e.g., if no validated token contracts are found), the condition this.completedContracts >= this.totalContracts (i.e., 0 >= 0) will evaluate to true. This causes the progress status to prematurely and incorrectly display 'finalizing database writes...' during initialization or when there is nothing to process. Adding a guard for this.totalContracts > 0 ensures the status remains 'initializing...' or handles the zero-contract case gracefully.

Suggested change

	let statusMessage: string;
	if (this.completedContracts >= this.totalContracts) {
	statusMessage = 'finalizing database writes...';
	let statusMessage: string;
	if (this.totalContracts > 0 && this.completedContracts >= this.totalContracts) {
	statusMessage = 'finalizing database writes...';

[igorls]

Applied in 74f1cce — guarded with this.totalContracts > 0, so a zero-contract run shows 'initializing...' instead of prematurely finalizing.