Default (event-based) JQL functions return stale results after issue association changes

All 4 default JQL functions, documented as "event-based" and not subject to Atlassian's 7-day caching mechanism, fail to reflect changes made to their underlying issue associations. Confirmed across all 4 functions:

• testPlanTestExecutions
• testSetTests
• defectsCreatedDuringTestExecution
• testsWithoutTestExecution

Environment:

• DC Compatible JQL Functions disabled on the site
• Only Xray Custom JQL Functions are enabled
• Per documentation, with DC Compatible off, only these 4 default event-based functions are available, and none should use caching

Steps to Reproduce (general pattern, confirmed for all 4 functions):

1. Run a JQL query using one of the 4 default functions against a given issue (Test Plan, Test Set, Test Execution, or Project/filter, depending on the function).
2. Note the returned results.
3. Change the underlying association relevant to that function (ex.: add a Test Execution to a Test Plan, add a Test to a Test Set, create a Defect in a Test Execution, or remove all Test Executions from a Test).
4. Re-run the same JQL query.

Expected Result:
Per the documentation, these functions should reflect association changes without delay, since they update based on events rather than the 7-day cache used by DC-compatible functions.

Actual Result:
All 4 functions return stale results after the underlying association changes. New or updated associations are not reflected on re-running the query. This has been confirmed independently for each of the 4 functions, not just one.