Merge upstream blockscout/blockscout master

Sync 61 commits from upstream. Resolved 67 conflicts:
- Deleted workflow files (modify/delete): keep deleted (DOScan custom CI)
- mix.exs versions: accept upstream
- Elixir source: accept upstream
- CHANGELOG.md: accept upstream

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: JOY

…hub/skills/alias-nested-modules/SKILL.md …nts/skills/alias-nested-modules/SKILL.md.github/skills/alias-nested-modules/SKILL.md renamed to .agents/skills/alias-nested-modules/SKILL.md .github/skills/alias-nested-modules/SKILL.md renamed to .agents/skills/alias-nested-modules/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: alphabetically-ordered-aliases
+description: Ensure that aliases are alphabetically ordered within their groups to maintain consistent code style and address Credo readability warnings.
+---
+
+## Overview
+
+Elixir code style conventions prefer that module aliases are alphabetically ordered within their groups. This improves code readability, maintainability, and consistency. Credo checks for this ordering and warns when aliases are not properly alphabetized.
+
+## When to Use
+
+- When addressing Credo warning: "The alias is not alphabetically ordered among its group"
+- When organizing module aliases at the top of a file
+- When multiple aliases from related modules are defined together
+- When refactoring code to improve consistency and readability
+
+## Anti-Patterns (Avoid These)
+
+```elixir
+defmodule Explorer.Migrator.HeavyDbIndexOperation.RenameTransactions do
+  # ❌ BAD: Aliases not alphabetically ordered
+  alias Explorer.Chain.Cache.BackgroundMigrations
+  alias Explorer.Migrator.{HeavyDbIndexOperation, MigrationStatus}
+  alias Explorer.Migrator.HeavyDbIndexOperation.Helper
+  alias Explorer.Migrator.HeavyDbIndexOperation.DropTransactionsIndex
+  alias Explorer.Repo
+end
+
+# In the above, "Helper" comes after "DropTransactionsIndex" 
+# alphabetically, but it's listed before it. Correct order should be:
+# - DropTransactionsIndex (D < H)
+# - Helper (H)
+```
+
+## Best Practices (Use These)
+
+```elixir
+defmodule Explorer.Migrator.HeavyDbIndexOperation.RenameTransactions do
+  # ✅ GOOD: Aliases properly alphabetically ordered
+  alias Explorer.Chain.Cache.BackgroundMigrations
+  alias Explorer.Migrator.{HeavyDbIndexOperation, MigrationStatus}
+  
+  # Within same group, ordered alphabetically:
+  # D comes before H comes before R
+  alias Explorer.Migrator.HeavyDbIndexOperation.DropTransactionsIndex
+  alias Explorer.Migrator.HeavyDbIndexOperation.Helper
+  alias Explorer.Repo
+end
+```
+
+## How to Implement
+
+### Step 1: Identify alias groups
+Aliases are grouped by their module depth and prefix. List all aliases by location:
+
+```
+Group 1: Single-level modules
+- alias Explorer.Repo
+
+Group 2: Multi-level modules from same prefix
+- alias Explorer.Chain.Cache.BackgroundMigrations
+- alias Explorer.Migrator...
+```
+
+### Step 2: Sort alphabetically within each group
+
+Within each group, sort by:
+1. The full module path alphabetically
+2. Consider the last component of the path when the prefix is the same
+
+For modules with the same prefix like:
+- `Explorer.Migrator.HeavyDbIndexOperation.CreateTransactions...`
+- `Explorer.Migrator.HeavyDbIndexOperation.DropTransactions...`
+- `Explorer.Migrator.HeavyDbIndexOperation.Helper`
+
+Sort by the last component: `Create...` < `Drop...` < `Helper`
+
+### Step 3: Reorder in code
+
+Rearrange the alias statements to match the alphabetical order determined in Step 2.
+
+### Step 4: Verify with Credo
+
+Run Credo to ensure no warnings remain:
+
+```bash
+mix credo --strict
+```
+
+## Example Violations and Fixes
+
+### Violation 1: Helper before DropTransactions
+
+```elixir
+# ❌ BEFORE
+alias Explorer.Migrator.HeavyDbIndexOperation.Helper
+alias Explorer.Migrator.HeavyDbIndexOperation.DropTransactionsIndex
+
+# ✅ AFTER
+alias Explorer.Migrator.HeavyDbIndexOperation.DropTransactionsIndex
+alias Explorer.Migrator.HeavyDbIndexOperation.Helper
+```
+
+### Violation 2: Mixed ordering in group
+
+```elixir
+# ❌ BEFORE
+alias Explorer.Repo
+alias Explorer.Chain.Cache.BackgroundMigrations
+alias Explorer.Migrator.{HeavyDbIndexOperation, MigrationStatus}
+
+# ✅ AFTER
+alias Explorer.Chain.Cache.BackgroundMigrations
+alias Explorer.Migrator.{HeavyDbIndexOperation, MigrationStatus}
+alias Explorer.Repo
+```
+
+## Related Skills
+
+- [Code Formatting](../code-formatting/SKILL.md) - Run after applying alias ordering fixes
+- [Alias Nested Modules](../alias-nested-modules/SKILL.md) - Define aliases for nested modules
+
+## References
+
+- [Credo Readability.AliasOrder](https://hexdocs.pm/credo/Credo.Check.Readability.AliasOrder.html)
+- [Elixir Naming Conventions](https://hexdocs.pm/elixir/naming-conventions.html)

.agents/skills/alphabetically-ordered-aliases/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: code-formatting
-description: Fixes code formatting in the Blockscout Elixir project using mix format. Use when you need to fix formatting violations, code style inconsistencies, or ensure consistent code formatting. For linting issues, use `mix credo`.
+description: Fixes code formatting in the Blockscout Elixir project using mix format. Use when you need to fix formatting violations, code style inconsistencies, or ensure consistent code formatting. For linting issues, use `mix credo`. Use this skill for every change made.
 ---
 
 ## Overview

.github/skills/code-formatting/SKILL.md .agents/skills/code-formatting/SKILL.md.github/skills/code-formatting/SKILL.md renamed to .agents/skills/code-formatting/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: elixir-credo-predicate-naming
+description: "Use when working on Elixir code with Credo predicate naming warnings, boolean helper functions, or renaming functions that start with is_. Prevents violations like: Predicate function names should not start with 'is' and should end in a question mark."
+---
+
+# Elixir Credo Predicate Naming
+
+Use this skill to prevent and fix predicate naming violations in Elixir.
+
+## Rules
+
+- Predicate functions must end with `?`.
+- Predicate functions must not start with `is_`.
+- Prefer names like `valid_*?`, `enabled_*?`, `has_*?`, `can_*?`, `matches_*?`, or `<noun>_*?`.
+
+## Refactor Workflow
+
+1. Find predicate functions named like `is_*?`.
+2. Rename each one to a Credo-compliant name that still reads clearly.
+3. Update all call sites in the same module and across the codebase.
+4. Keep arity unchanged unless behavior intentionally changes.
+5. Run a focused Credo check for edited files.
+
+## Naming Guidance
+
+- `is_valid_zrc2_transfer_log?/4` -> `valid_zrc2_transfer_log?/4`
+- `is_enabled?/1` -> `enabled?/1`
+- `is_erc20_transfer?/2` -> `erc20_transfer?/2`
+- `is_contract_verified?/1` -> `contract_verified?/1`
+
+## Safety Checks
+
+- Preserve semantics during rename.
+- Verify no stale references remain.
+- If the function is part of a public API, rename consistently and update docs/specs.
+
+## Verification Commands
+
+```bash
+mix credo path/to/file.ex
+mix test
+```
+
+## Expected Result
+
+No Credo findings for predicate naming in updated files.