Triage runner does not execute `pre_script` from harness configuration

[guyoron1]

Problem

The triage agent runner does not execute the pre_script field from harness configuration. A per-repo triage harness using base composition declares pre_script: scripts/custom-pre-triage.sh, and that script exits 1 — but the triage agent proceeds to run normally.

This was discovered while verifying the base-composition dispatch fix from fullsend-ai#5693 (closing fullsend-ai#5045). The dispatch enumeration now correctly handles base: fields, so the triage harness is found and dispatched. However, the triage runner path does not invoke the pre_script before starting the agent.

Evidence

• Harness: .fullsend/harness/triage.yaml with pre_script: scripts/custom-pre-triage.sh
• Script: scripts/custom-pre-triage.sh contains echo "hello world" followed by exit 1
• Expected: triage aborts due to non-zero pre_script exit
• Actual: triage runs to completion and posts a triage comment

Context

• Issue Remove redundant pre-code.sh / pre-fix.sh calls from reusable workflows fullsend-ai/fullsend#4718 documents that reusable-code.yml and reusable-fix.yml call pre-scripts both inline (in the workflow YAML) and via run.go:760-773. The triage runner path appears to lack equivalent pre_script execution.
• The run.go pre_script handling (lines 760-773) may not be reached by the triage agent's execution path, or the triage reusable workflow does not invoke fullsend run in a way that triggers pre_script execution.

Expected behavior

When a triage harness declares pre_script, the runner should execute it before starting the triage agent. If the script exits non-zero, triage should abort (matching code/fix behavior).

Validation criteria

1. A triage harness with pre_script pointing to a script that exits 1 should cause the triage run to fail/abort
2. A triage harness with pre_script pointing to a script that exits 0 should allow triage to proceed normally
3. pre_script from base-composed harnesses should be respected the same as inline declarations

[guyoron1]

/fs-triage

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:46 AM UTC · Completed 8:49 AM UTC
Commit: c887fc4 · View workflow run →

[fullsend-ai-triage]

This issue is already being addressed by an open PR that is labeled ready-for-merge. The PR fixes the root cause: during base composition, mergeForgeBlocks inherits the base's forge.github.pre_script, and ResolveForge then unconditionally overwrites the child's top-level pre_script with that inherited forge-level value — silently dropping the child's explicit declaration. The fix clears inherited forge-level pre_script/post_script entries when the child explicitly declares the corresponding top-level field.

All three validation criteria from this issue are covered by the PR's tests:

1. Triage harness with pre_script that exits 1 → run aborts
2. Triage harness with pre_script that exits 0 → triage proceeds
3. Base-composed harness pre_script values are preserved correctly

Note: this issue describes the same problem as the now-closed #799, which was closed as "Path A complete." Once the PR merges, this issue should also be resolved.

Addressed by:

• fix(#799): preserve child pre_script during base forge composition #823

Previous run

This issue appears to be a duplicate of the already-closed #799, which has the same title, description, and evidence. PR #823 is open and directly addresses this problem — it fixes the base-composition bug where a child harness's pre_script was silently overwritten during ResolveForge, and adds triage-specific tests verifying that pre-script abort-on-exit-1 and proceed-on-exit-0 both work correctly.

All three validation criteria from this issue are covered by PR #823's test plan:

1. Triage harness with a pre_script that exits 1 causes the run to abort
2. Triage harness with a pre_script that exits 0 allows triage to proceed
3. Base-composed harness pre_script values are preserved correctly

Once PR #823 merges, this issue should be resolved. If there is a distinct aspect of this problem not covered by that PR, please clarify.

Addressed by:

• fix(#799): preserve child pre_script during base forge composition #823

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:53 AM UTC · Completed 8:56 AM UTC
Commit: c887fc4 · View workflow run →

[guyoron1]

/fs-code

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 9:29 AM UTC · Completed 9:39 AM UTC
Commit: c887fc4 · View workflow run →