A GitHub Action for publishing Agent Framework runs as playable Stories

[sunfishloop]

Hi Agent Framework community. I noticed several Show and tell posts here are about demos, autonomous workflows, provenance, and agent interaction patterns. For those cases, the run trace is often as important as the final output: a maintainer or reviewer wants to see what happened, what evidence was available, and where the agent recovered or changed direction.

I built a GitHub Marketplace Action for that artifact: https://github.com/marketplace/actions/publish-agent-story

It turns Codex, Claude Code, OpenClaw, JSONL, or plain LOG traces into a sanitized SunfishLoop Story: a playable, shareable page for one agent run. For Agent Framework projects, I think this could be useful for demo threads, eval reviews, or CI runs where a raw log is too noisy but a one-line summary is too weak.

The important safety boundary: the public Story should contain summarized decisions, visible actions, evidence, and results only. It should not publish private chain-of-thought, credentials, customer data, or internal logs.

Low-pressure CTA: would a minimal manual-trigger workflow example be useful for one Agent Framework sample or demo project? If maintainers are open to it, I can prepare a small opt-in PR that only adds the publishing step and keeps it off by default.