What happened
When the release CI chain fails and a manual refire is dispatched via a new agent-dispatch-labeled issue (issue #50), the workflow run shows INPUT_SUBAGENT / INPUT_APP / INPUT_VERSION / INPUT_RAW_NOTES all blank, and no issue lands on brilliant-web.
Why INPUT_* are blank (expected)
INPUT_SUBAGENT et al. are workflow_call env vars — they're intentionally empty on the issues: labeled path. Parsing is supposed to happen from the issue body instead. So the empty inputs aren't the bug; the bug is that the body parsing or downstream brilliant-web dispatch silently failed even though the workflow showed a run.
Likely suspects
raw-notes: |- multiline regex — the body parser uses raw-notes:\s*\|-?\n([\s\S]+?)(?=\n\S|$) in multiline mode. The $ in the lookahead matches end-of-line in multiline regex, not end-of-string — the last block may be captured as empty if it's the final field with no trailing newline followed by a non-space char.- BRILLIANT_WEB_PAT unavailable on issue-triggered path — secrets declared under
workflow_call.secrets may not automatically flow to the issues: labeled trigger branch. Worth logging !!process.env.BRILLIANT_WEB_PAT to confirm.
Reproduce
- Create an issue on radcap with label
agent-dispatch and a valid subagent: format-release-notes body
- Check whether a new issue appears on brilliant-web
- Check the run logs for
INPUT_* vs the parsed subagent/app/version variables
Context
Discovered during v1.0.5 release (2026-06-12). brilliant-web updated the app page via manual deploy (v1.9.44) so no user impact, but the refire path is broken for future use.
What happened
When the release CI chain fails and a manual refire is dispatched via a new
agent-dispatch-labeled issue (issue #50), the workflow run shows INPUT_SUBAGENT / INPUT_APP / INPUT_VERSION / INPUT_RAW_NOTES all blank, and no issue lands on brilliant-web.Why INPUT_* are blank (expected)
INPUT_SUBAGENT et al. are
workflow_callenv vars — they're intentionally empty on theissues: labeledpath. Parsing is supposed to happen from the issue body instead. So the empty inputs aren't the bug; the bug is that the body parsing or downstream brilliant-web dispatch silently failed even though the workflow showed a run.Likely suspects
raw-notes: |-multiline regex — the body parser usesraw-notes:\s*\|-?\n([\s\S]+?)(?=\n\S|$)in multiline mode. The$in the lookahead matches end-of-line in multiline regex, not end-of-string — the last block may be captured as empty if it's the final field with no trailing newline followed by a non-space char.workflow_call.secretsmay not automatically flow to theissues: labeledtrigger branch. Worth logging!!process.env.BRILLIANT_WEB_PATto confirm.Reproduce
agent-dispatchand a validsubagent: format-release-notesbodyINPUT_*vs the parsedsubagent/app/versionvariablesContext
Discovered during v1.0.5 release (2026-06-12). brilliant-web updated the app page via manual deploy (v1.9.44) so no user impact, but the refire path is broken for future use.