[aviggiano]

Summary

• join final-report fuzzer backend provenance through finding_id, upstream_id, and source_finding_id
• preserve fail-closed behavior by unioning campaign backends across every alias
• cover the exact R59 presentation-ID/source-ID shape plus an adversarial partial-backend claim

Live evidence

Aave v4 invariant-only R59 reached 31/32 successful nodes. final-report emitted presentation ID NP-01, retained campaign ID failure-1 as source_finding_id, and correctly recorded backend recon. The artifact gate looked up only NP-01, inferred no campaign backend, and rejected it with PROPERTY_REPORT_FUZZER_BACKEND_MISMATCH / Report fuzzer backends do not match the campaign records.

This PR fixes that newly exposed final-node blocker. A fresh externally owned live run is still required before #404 can close; this host does not have the uncommitted .ultrafuzz/modal/benchmark.json launch configuration.

Refs #404

Validation

• artifact-gates suite: 68/68 passed
• focused regression tests: 2/2 passed
• runtime typecheck passed
• touched-file ESLint passed
• touched-file Prettier check passed
• git diff --check passed

Greptile Summary

The PR extends final-report backend joins across presentation and source finding IDs while attempting to constrain aliases through lifecycle provenance.

• Passes the final report into property-provenance diagnostics.
• Collects campaign backends across aliases admitted by matching report outcomes.
• Adds coverage for renumbered findings and cross-outcome alias claims.

Confidence Score: 4/5

The PR is not safe to merge until report aliases are verified against independent campaign provenance rather than lifecycle claims from the report itself.

The previously reported backend-borrowing path remains reachable despite the reply claiming it was fixed: a report can coordinate its alias with a fabricated primary lifecycle source, causing the new helper to admit an unrelated real campaign finding and use its backend.

Files Needing Attention: packages/runtime/src/artifact-gates.ts, packages/runtime/test/artifact-gates.test.ts

Important Files Changed

Filename	Overview
packages/runtime/src/artifact-gates.ts	Adds alias-aware backend joining, but treats lifecycle assertions from the report under validation as proof that an alias belongs to the outcome.
packages/runtime/test/artifact-gates.test.ts	Covers the intended renumbering and a cross-outcome claim, but not a report that coordinates a false alias with a matching fabricated lifecycle binding.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  P[Property provenance alias] --> O[Matching report outcome]
  O --> L[Report-authored primary lifecycle source]
  L --> A[Alias admitted]
  A --> C[Campaign backend map lookup]
  C --> G[Backend provenance gate]

Loading

Prompt To Fix All With AI

### Issue 1
packages/runtime/src/artifact-gates.ts:3191-3204
**Report assertions verify their own aliases**

When a property-provenance entry claims an existing campaign finding as an alias and its matching report outcome supplies a fabricated primary lifecycle source for that finding, `verifiedReportFindingAliases` treats the report-authored lifecycle assertion as verification and imports the real campaign backend. The unrelated finding then avoids `PROPERTY_REPORT_FUZZER_BACKEND_MISMATCH` despite having no genuine campaign provenance.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (3): Last reviewed commit: "fix(runtime): bind report aliases to lif..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

Context used:

• Knowledge Base — Runtime: Run Orchestration Lifecycle

[greptile-apps]

Report assertions verify their own aliases

When a property-provenance entry claims an existing campaign finding as an alias and its matching report outcome supplies a fabricated primary lifecycle source for that finding, verifiedReportFindingAliases treats the report-authored lifecycle assertion as verification and imports the real campaign backend. The unrelated finding then avoids PROPERTY_REPORT_FUZZER_BACKEND_MISMATCH despite having no genuine campaign provenance.

Knowledge Base Used: Runtime: Run Orchestration Lifecycle

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/runtime/src/artifact-gates.ts
Line: 3191-3204

Comment:
**Report assertions verify their own aliases**

When a property-provenance entry claims an existing campaign finding as an alias and its matching report outcome supplies a fabricated primary lifecycle source for that finding, `verifiedReportFindingAliases` treats the report-authored lifecycle assertion as verification and imports the real campaign backend. The unrelated finding then avoids `PROPERTY_REPORT_FUZZER_BACKEND_MISMATCH` despite having no genuine campaign provenance.

**Knowledge Base Used:** [Runtime: Run Orchestration Lifecycle](https://app.greptile.com/monad-foudnation/-/custom-context/knowledge-base/monad-developers/ultrafuzz/-/docs/runtime.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.