[CLD-1983]: feat(operations): add WithForceExecute option and latest cache reuse

[graham-chainlink]

What changed

• Added WithForceExecute execute option to force operation execution and bypass previous successful report short-circuiting.
• Updated cached report lookup to prefer the most recent matching successful report.

Why

• We have use case from our users where in the same changeset , they want to execute the same operations but it can return different data due to it being update in between calls. With the operations report caching, they will never be able to fetch the latest data, introducing an option to bypass the cache will support this use case.

Context: https://chainlink-core.slack.com/archives/C043E82DUM8/p1775799230707799

JIRA: https://smartcontract-it.atlassian.net/browse/CLD-1983

[changeset-bot]

🦋 Changeset detected

Latest commit: 03fc12e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
chainlink-deployments-framework	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[graham-chainlink]

now that there can be multiple reports of the same ID, we want to return the most recent ones instead of the oldest one

[Copilot]

Pull request overview

Adds an execution option to bypass cached successful reports and adjusts cached report selection to prefer the newest successful match, updating tests and docs accordingly.

Changes:

• Add WithAlwaysExecute option to force ExecuteOperation to run and skip successful-report reuse.
• Update cached successful report lookup to prefer the most recent matching successful report.
• Add/adjust tests and docs to reflect the new behavior.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
operations/execute.go	Adds WithAlwaysExecute/config flag and changes cached report lookup to scan from newest to oldest.
operations/execute_test.go	Extends previous-run test for forced re-execution and adds a regression test for “most recent successful report” reuse.
operations/doc.go	Updates package docs to mention default reuse and show WithAlwaysExecute usage.
.changeset/gentle-moles-rule.md	Adds release note entry for the new option.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

operations/execute.go:196

• ExecuteOperationN now applies ExecuteOption functions before checking for reusable execution-series reports. Previously, if enough cached reports existed, options were not invoked. If any custom ExecuteOption has side effects, this is an observable behavior change on cache hits; consider documenting this or restructuring so only the needed option(s) are evaluated before the cache short-circuit.

	executeConfig := &ExecuteConfig[IN, DEP]{
		retryConfig: newDisabledRetryConfig[IN, DEP](),
	}
	for _, opt := range opts {
		opt(executeConfig)
	}

	if executeConfig.alwaysExecute {
		return []Report[IN, OUT]{}, ErrAlwaysExecuteNotSupportedForExecuteOperationN
	}

	results, ok := loadSuccessfulExecutionSeriesReports[IN, OUT](b, operation.def, input, seriesID)
	resultsLen := uint(len(results))
	if ok {
		// if there are more reports than n, we return only the first n reports
		if resultsLen >= n {
			b.Logger.Infow("Operations already executed in an execution series. Returning previous results", "id", operation.def.ID,
				"version", operation.def.Version, "description", operation.def.Description, "executionSeriesID", seriesID)

			return results[:n], nil
		}
	}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[graham-chainlink]

This is a breaking change, but i checked company wide usage for ExecuteOperationN and didn see any.

[graham-chainlink]

I have to introduce new functional option type for ExecuteOperationN as i dont want ExecuteOperationN to support always run option as it has its own quirks. Previously it was sharing the same option type as ExecuteOperation

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
81.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube