Hermes Agent 1d87b76e1f fix(framework/tools): lane-brief.sh — classify PR-body-linked issues as work-underway (#546) ...

Remediation of coder3 independent-validation blocker on PR #547.

lane-brief.sh inspected only the open-PR index/title/head fields, never the PR
BODY or Gitea issue linkage. A body-only "Closes #546" was therefore invisible,
so issue #546 (open, with PR #547 'Closes #546' in its body) was placed under
DISPATCH CANDIDATES with work-underway count 0 — re-dispatchable in-flight work,
unacceptable for a dispatch-truth tool.

Fix:
- Fetch open PRs as JSON including `body`; resolve PR->issue links via Gitea's
  closing-keyword set (close/closes/closed, fix/fixes/fixed, resolve/resolves/
  resolved), case-insensitive, word-boundary anchored, `#` directly following the
  keyword. Any issue so linked from an OPEN PR is classified WORK UNDERWAY.
- Preserve the prior title/head bare-ref heuristic and per-repo behavior; require
  `#` immediately after the keyword so cross-repo `owner/repo#N` forms don't leak.
- Bare `#N` prose mentions in a body are intentionally NOT links (e.g. "#538 line
  of work") to avoid marking live, dispatchable issues as in-flight.

Tests (committed, RED-on-revert non-vacuity):
- test-lane-brief-pr-linkage.sh: open-PR-with-'Closes #546'-in-body excludes #546
  from candidates (and a reverted copy with the body-scan removed regresses #546
  to a candidate — RED proof); bare #777 and substring 'hotfix #999' stay
  candidates (word-boundary + closing-keyword-only guards).
- test-ci-wait-exit-matrix.sh: ci-wait.sh exit matrix 0 (all-success) / 1
  (terminal-not-success: failure + error/killed) / 2 (usage) / 3 (timeout).

shellcheck -x + bash -n clean on all four files; no secret values. ci-wait.sh
unchanged (coder3 PASS preserved). Closed-issue exclusion unchanged.

Refs #546, PR #547

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-18 16:49:13 -05:00

3.0 KiB

Raw Blame History

View Raw