Code Browser

Improvements to testing around restoring from backup

Figure out weird timeouts in SV reonboarding tests

Tracking: tracing infelicities and improvements

Separate the validator faucets from the validator rewards in the scan/wallet transaction histories

Refactor VoteRequest.tsx state management according to React best practices

Tracking: retry and logging improvements for triggers

fix tests that assume amuletPrice=1

Investigate Canton regression resulting in "periodic acknowledgement failed"

Add store metrics

Canton warning: Token refresh failed with Status{code=UNAVAILABLE

Canton: aggregation-id aliasing for set-traffic-balance requests

Do not assume a unique event_ids for TxLog entries

Change "coin creation" to "base transfer" and "transfer" to "percentage transfer" in CC Scan UI, Wallet UI, and in Amulet code

factor open mining rounds table display between sv and scan

we should connect grafana to the external alert manager

Ensure batch sizes in polling triggers don't significantly exceed parallelism limit

`SvOnboardingRequestTrigger` should also check that SV party has not yet operated a node

Document advice on DR for app operators

Add unit tests for sweep logic

Add automated cluster tests of wallet sweeps

Make `migrateValidatorParty` flow robust to ACS changes due to the migrated party being an observer on contracts

Remove workaround added by DACH-NY/canton-network-node#12777 and similar

Consider adding a prometheus blackbox_exporter instance to our clusters for synthetic monitoring

Extend Scan with view to display Transaction by Id

Expose read-only subset of SV UI in scan

Task "Shutting down forcibly" in SV app shutdown (SvIdentitiesDumpIntegrationTest)

Use a high min-nodes to prevent scale-downs during tests

Avoid slick errors during shutdown

Retire `log/canton_errors.log.gz`

Add a periodic CI run of something like `deploy_scratchnet_DR`