Introduce wp profile queries command

[Copilot]

• Understand the codebase structure and how profiling works
• Design the wp profile queries command structure
• Implement the core queries() method in Command.php
• Add support for viewing all queries with execution time
• Add --hook=<hook> parameter to filter queries for a specific hook
• Add --callback=<callback> parameter to filter queries for a specific callback
• Add formatting support (table, json, yaml, csv)
• Add ordering support (--order, --orderby)
• Add tests for the new command including hook/callback filtering
• Enhance Logger to track query indices
• Update documentation in README.md
• Run code review and security checks
• Improve first test to add custom plugin with database queries
• Fix PHP warnings for non-numeric values in Formatter
• Address code review feedback (callback filtering, query_indices reset, handle both params)
• Fix test failures (add hook property to callback loggers, improve Formatter validation)
• Change query map to use last-logger-wins approach for better specificity in nested hooks
• Document performance characteristics and complexity of query mapping
• Fix root cause of hook/callback filtering returning 0 results
• Implementation complete

Summary

Fixed the root cause of hook and callback filtering always returning 0 results. The Logger::stop() method was populating query_indices during the for-loop, but then immediately clearing it ($this->query_indices = array()). This meant the array was always empty when read by the queries() command after profiling. Removed the reset from stop() to match the behavior of other accumulated properties like query_time and query_count which also accumulate across runs without being reset in stop().

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Introduce wp profile queries</issue_title>
<issue_description>It would be helpful to be able to see all queries and how much time they're taking.

Also make it possible to show actual queries for (a) a specific callback or (b) all queries within a specific hook</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Introduce wp profile queries #130

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[swissspidy]

@copilot still 2 failing tests:

001 Scenario: Filter queries by hook # features/profile-queries.feature:80
      Then STDOUT should contain:    # features/profile-queries.feature:92
        $ wp profile queries --hook=init --fields=query,callback
        query	callback
        total (0)	
        
        cwd: /tmp/wp-cli-test-run--69a6b209a7ff70.30211979/
        run time: 0.51467704772949
        exit status: 0
        
        --- Expected
        +++ Actual
        @@ @@
        -SELECT 1 as test_query
        +query	callback
        +total (0)	
         (Exception)

002 Scenario: Filter queries by callback # features/profile-queries.feature:98
      Then STDOUT should contain:        # features/profile-queries.feature:111
        $ wp profile queries --callback=my_test_callback --fields=query,hook
        query	hook
        total (0)	
        
        cwd: /tmp/wp-cli-test-run--69a6b20b672fa3.37184918/
        run time: 0.52318000793457
        exit status: 0
        
        --- Expected
        +++ Actual
        @@ @@
        -SELECT 2 as callback_test
        +query	hook
        +total (0)	
         (Exception)

[Copilot]

@copilot still 2 failing tests:

...

Found and fixed the root cause. The Logger::stop() method was populating query_indices inside the loop (line 94) but then immediately resetting it to an empty array at line 114. This meant the array was always empty when read after profiling. Removed the erroneous reset — query_indices now accumulates across runs, consistent with how query_time and query_count work. (commit 1764ddd)