triagebot-action

Problem When the triage bot commits an agent's fix, it built a shell command via git commit -m ${JSON.stringify(commitMessage)}\. only produces a double-quoted JS string literal — it does not escape backticks or , which are command substitution inside a double-quoted shell string. LLM-authored commit messages routinely contain backticks (e.g. `removeTrailingForwardSlash('/')/bin/shisPushedforce: truemainpkg.pr.newgitCommit()src/github.tsexecFilegitPushfailed('/')$(whoami)"quotes"mainpnpm testcheck:distpnpm lintpnpm formatdist/dist/git commit -m ""` shell string is gone from the bundle.

Summary restore pkg.pr.new preview publishing after fixed triage branches are pushed pass preview URLs into generated issue comments and only mark fixes pending when previews exist expand Flue/tool and orchestration logging for preview debugging add mocked coverage for preview publishing in the triage flow Tests pnpm lint pnpm test

Summary add a Flue event logger modeled on Flue CLI's line event presenter wire the logger into the standalone action Flue context with log assistant text, thinking, tool start/done/error, log, and compaction events add unit coverage for buffered text/thinking and event categories rebuild bundled action output Why When the action runs Flue directly instead of through , Flue events were not being printed. This made triage runs look stuck after messages like even though skills/tools could still be running. Testing