The research stage read ISSUE_TITLE/BODY from gitea.event.issue which is null on workflow_dispatch — the agent got an empty prompt and produced nothing (fail-loud caught it). Now fetches from the API.
The research stage read ISSUE_TITLE/BODY from gitea.event.issue which is null on workflow_dispatch — the agent got an empty prompt and produced nothing (fail-loud caught it). Now fetches from the API.
🤖Headless spec gate (non-blocking, #204 first slice)
Spec-gate agent produced no text output — check runner logs.
Deterministic floors still govern the merge
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.
🤖 **Headless spec gate (non-blocking, #204 first slice)**
Spec-gate agent produced no text output — check runner logs.
<details><summary>Deterministic floors still govern the merge</summary>
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.</details>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The research stage read ISSUE_TITLE/BODY from gitea.event.issue which is null on workflow_dispatch — the agent got an empty prompt and produced nothing (fail-loud caught it). Now fetches from the API.
🤖 Headless spec gate (non-blocking, #204 first slice)
Spec-gate agent produced no text output — check runner logs.
Deterministic floors still govern the merge
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.