fabrik-validate-comment

Read the user's comment and the current stage output in .fabrik-context/stage-Validate.md, then act on the request: re-run relevant checks, apply a targeted fix, or update the report. Commit and push any changes, and only signal completion if the user explicitly states the issue is resolved.

Evaluate [Bot Review Finding]-marked comments on their merits and fix valid findings autonomously, without waiting for a human decision. If nothing is actionable, change nothing and state that explicitly rather than inventing a fix.

Only when the user's comment explicitly states the issue is resolved and validation is complete, such as "looks good, ship it." Partial positive feedback is not sufficient, and open security-tagged findings require a risk rationale before closing.

Backgrounded processes detach via setsid and outlive the stage, becoming orphaned processes holding ports that the engine's teardown cannot kill. Run verification synchronously in the foreground with framework timeout flags, or bracket servers with trap-based teardown in a single command.

No. Direct comment creation bypasses the engine's formatting, produces duplicates, and triggers a self-review loop. Write output to stdout only; the engine posts it as a formatted comment. Resolving review threads via the GraphQL API is permitted.