[nedtwigg]

On a changed story's page at hackathon.selfie.dev, anyone can now ask Muse Spark about the change. It reads the before, after, and diff images, and the commits and code diff from GitHub since the commit that was approved. The answer streams in, and the page says what code it read and what it left out. Spec: docs/specs/chat.md.

• Model: muse-spark-1.3 on Meta's Responses API, standard mode, with store: false. Nothing of a conversation is kept on the server: the page holds it and sends it with each question.
• Open to anyone, by Ned's decision, for as long as the service is up for the hackathon. One address may ask 10 questions a minute, which slows someone down but doesn't cap the bill.
• What the model can do: nothing but answer. It has no tools and its replies show as plain text, since the code and pixels it reads come from the branch under review. It can't approve or reject.
• Where it lives: a Worker-only route, added through a new extra-routes argument to createReviewApi. It isn't on ReviewSource, so selfie ui is unchanged.

Testing: pnpm test and pnpm typecheck pass. The route runs in the workerd suite with stand-ins for GitHub and the model. One real call to Meta's API, with a rendered image, returned the stream the parser expects. The 8 new Parts/Chat stories rendered with no failures.

/simplify ran. Left as they are: sharing the notes form, since Enter, controlled text, and restoring a failed question all differ; a single-story comparison in the store; and sending image URLs in place of data: URLs, which the spec doesn't allow.

🤖 Generated with Claude Code