Cardano Updates

Add comprehensive boot-sequence.md covering:
- Service components (core and monitoring) with lifecycle types
- Startup order flowchart with dependency signals
- Sync stages state machine (SYNCING → APPLYING_INDEXES → LIVE)
- Health check methods for all services
- Shared resources with volume paths per network (mainnet/preprod)

The new index-applier service introduced in v2.0 is documented, including the deferred index creation strategy that reduces initial sync time by ~6 hours on mainnet.

Also fixes:
- Reorder sidebar positions to place boot-sequence first
- Add missing Tabs component import in hardware-profiles.md

Co-authored-by: Mateusz Czeladka <[email protected]>

Remove all documentation and configuration references to the deprecated single Docker image deployment. From version 2.0.0, only Docker Compose deployment with separate service containers will be supported.

Changes:
- Update GitHub Actions description to list all component images instead of "All-in-one Image"
- Remove deprecation warning from README about single Docker image
- Update DockerHub link to organization page instead of deprecated image
- Clean up .gitignore comments to reflect Docker Compose profile files

Co-authored-by: Mateusz Czeladka <[email protected]>

Remove all documentation and configuration references to the deprecated single Docker image deployment. From version 2.0.0, only Docker Compose deployment with separate service containers will be supported.

Changes:
- Update GitHub Actions description to list all component images instead of "All-in-one Image"
- Remove deprecation warning from README about single Docker image
- Update DockerHub link to organization page instead of deprecated image
- Clean up .gitignore comments to reflect Docker Compose profile files

Remove all documentation and configuration references to the deprecated single Docker image deployment. From version 2.0.0, only Docker Compose deployment with separate service containers will be supported.

Changes:
- Update GitHub Actions description to list all component images instead of "All-in-one Image"
- Remove deprecation warning from README about single Docker image
- Update DockerHub link to organization page instead of deprecated image
- Clean up .gitignore comments to reflect Docker Compose profile files

Implements automated index application for the APPLYING_INDEXES sync state. The index-applier container polls the API until the sync stage transitions to APPLYING_INDEXES, then applies all indexes from db-indexes.yaml using CREATE INDEX CONCURRENTLY.

Changes:
- Add apply-indexes.sh script with idempotent logic and invalid index handling
- Add curl, jq, yq dependencies to postgres Dockerfile
- Add docker-compose-index-applier.yaml service definition
- Include index-applier in main docker-compose.yaml
- Add index-management.md documentation in advanced-configuration
- Update docker.md deployment guide with index application section

The script:
- Polls /network/status for APPLYING_INDEXES stage
- Detects and drops invalid indexes (from failed CONCURRENTLY operations)
- Creates indexes sequentially using CONCURRENTLY to avoid indexer restarts
- Reads index definitions from db-indexes.yaml (single source of truth)

Restructures database index configuration to support both index monitoring
and external index creation by watchdog services.

Changes:
- Create dedicated db-indexes.yaml configuration file with 16 database indices
- Introduce DbIndex record with 'name' and 'command' fields for each index
- Add getIndexNames() and getIndexCommands() helper methods to RosettaIndexConfig
- Update PostgreSQLIndexCreationMonitor to use getIndexNames() helper
- Move db_indexes list from application.yaml to db-indexes.yaml
- Update all tests to work with new configuration structure

Benefits:
- Separation of concerns: index definitions in dedicated file
- Type safety via Java records
- External watchdog services can retrieve SQL commands via getIndexCommands()
- Single source of truth for both index names and creation commands

Restructures database index configuration to support both index monitoring
and external index creation by watchdog services.

Changes:
- Create dedicated db-indexes.yaml configuration file with 16 database indices
- Introduce DbIndex record with 'name' and 'command' fields for each index
- Add getIndexNames() and getIndexCommands() helper methods to RosettaIndexConfig
- Update PostgreSQLIndexCreationMonitor to use getIndexNames() helper
- Move db_indexes list from application.yaml to db-indexes.yaml
- Update all tests to work with new configuration structure

Benefits:
- Separation of concerns: index definitions in dedicated file
- Type safety via Java records
- External watchdog services can retrieve SQL commands via getIndexCommands()
- Single source of truth for both index names and creation commands

Removes duplicate db_indexes list from all profile-specific YAML files
(application-online.yaml, application-offline.yaml, application-h2.yaml,
application-test.yaml).

The list is now defined only once in the base application.yaml and
properly inherited by all profiles through Spring Boot's @ConfigurationProperties
binding mechanism via RosettaIndexConfig.

This eliminates maintenance overhead and ensures consistency across all
deployment profiles.

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>

Refactors the index monitoring system to check pg_index system catalog
for index validity and readiness (indisvalid and indisready flags) instead
of monitoring active index creation via pg_stat_progress_create_index.

Key changes:
- PostgreSQLIndexCreationMonitor now queries pg_index joined with pg_class
- Checks that ALL required indices exist and have indisvalid=true and indisready=true
- Required indices list added to application.yaml (cardano.rosetta.rosetta-indexes)
- Only transitions to LIVE state when all 11 required indices are valid and ready

This ensures proper state machine flow: SYNCING -> APPLYING_INDEXES -> LIVE
and prevents premature transition to LIVE state before external watchdog
completes applying the optional performance indices.

The previous approach could result in SYNCING -> LIVE -> APPLYING_INDEXES -> LIVE
when indices were already applied before the monitoring check ran.

Refactors the index monitoring system to check pg_index system catalog
for index validity and readiness (indisvalid and indisready flags) instead
of monitoring active index creation via pg_stat_progress_create_index.

Key changes:
- PostgreSQLIndexCreationMonitor now queries pg_index joined with pg_class
- Checks that ALL required indices exist and have indisvalid=true and indisready=true
- Required indices list added to application.yaml (cardano.rosetta.rosetta-indexes)
- Only transitions to LIVE state when all 11 required indices are valid and ready

This ensures proper state machine flow: SYNCING -> APPLYING_INDEXES -> LIVE
and prevents premature transition to LIVE state before external watchdog
completes applying the optional performance indices.

The previous approach could result in SYNCING -> LIVE -> APPLYING_INDEXES -> LIVE
when indices were already applied before the monitoring check ran.

Removes the V1.0_1500_0__rosetta_app_error_workaround.sql migration file
that was creating an error table as a workaround for yaci-store not
creating it automatically.

Co-authored-by: Mateusz Czeladka <[email protected]>

Removes the V1.0_1500_0__rosetta_app_error_workaround.sql migration file
that was creating an error table as a workaround for yaci-store not
creating it automatically.

Co-authored-by: Mateusz Czeladka <[email protected]>