Fix failed log misattribution in pipeline summaries

[cursor]

Description

Fixes a correctness bug in the new bulk pipeline-log summarization path. When multiple failed steps shared an identifier across stages, all_step_logs could attach the first matching stage's log to another step, producing a false execution summary.

The failed-log fetch path now retains a map keyed by the canonical logBaseKey, and bulk result assembly merges each fetched value using that exact key. A regression test covers duplicate deploy identifiers in separate stages with distinct logs.

Type of Change

• Bug fix
• New feature
• Refactor
• Documentation
• Other

Checklist

• pnpm test passes (117 files, 2565 tests)
• pnpm typecheck passes
• pnpm build passes
• pnpm standards:check passes (80 tests)
• pnpm docs:check passes

Coding Standards (registry-driven MCP model)

Not applicable — this change does not add or modify Harness API coverage or tool registration.

  

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Saranya-jena]

@cursor wouldn't it cause an issue when logbasekey is very long?