[Parent] Safe-output executor E2E test coverage and tool correctness #1428

Tracks open issues concerning the correctness, completeness, and E2E test coverage of safe-output tools in the executor-e2e harness and the safe-output Rust implementations.

Open issues

• #aw_soexec sub-issues cover:
  • E2E test harness gaps: safe-output actions that are never exercised by the executor-e2e definition, causing silent regressions.
  • Implementation bugs: missing file staging, access-control failures, and missing NDJSON fields that prevent tools from executing successfully in Stage 3.
  • Tool capability gaps: safe-output tools lacking features (e.g. inline suggestion rendering) needed by agents.

Related issues (tracked here)

• test(executor-e2e): queue-build never smoke-tested — E2E_QUEUE_PIPELINE_ID unset in 'executor e2e' definition #1422 — queue-build never smoke-tested: E2E_QUEUE_PIPELINE_ID unset in executor-e2e definition
• test(executor-e2e): upload-build-attachment & upload-pipeline-artifact never exercised — harness emits un-staged NDJSON (missing staged_file) #1421 — upload-build-attachment & upload-pipeline-artifact never exercised: harness emits un-staged NDJSON (missing staged_file)
• add-pr-comment: render inline threads as applyable single/multi-line suggestions #1103 — add-pr-comment: render inline threads as applyable single/multi-line suggestions
• fix(safe-outputs): add file staging to upload-workitem-attachment #381 — fix(safe-outputs): add file staging to upload-workitem-attachment
• debug: upload-pipeline-artifact fails with ContainerWriteAccessDeniedException when uploading to other builds #471 — upload-pipeline-artifact fails with ContainerWriteAccessDeniedException when uploading to other builds

Generated by Issue Arborist · 56.3 AIC · ⌖ 8.57 AIC · ⊞ 6K · ◷