TEST: claude-code-action example on bisque-cloud/presenter@v1 (v1.9.0)

This pull request adds one workflow file. When a pull request opens, Claude Code writes a short narrated explainer of it, and a watch link comes back as a comment. The file is a test copy of the example from the presenter project, so it exercises the released action on this repository, and the description says to close it after the run.

The author's description calls it a test of the released action. The example workflow is copied unedited, and it uses the public plugin marketplace and the version one tag of the presenter action, now at version 1.9. That is why the README also gets a short note: this workflow tests the release, rather than the repository's own copy of the action.

The first job gives Claude only read permissions. It checks out the repository, runs Claude Code with the presenter plugin, and allows a shell, file writes and web fetches, capped at 150 turns. The prompt tells Claude to read the pull request with the GitHub command line, write the slides and a context file, narrate them on the runner, and fix whatever the checks find. It must stop before publishing. Then the folder is uploaded as an artifact.

The second job runs on a fresh runner. It downloads the folder and hands it to the presenter action, which publishes in the voice already narrated, so nothing is spoken twice. Only this job can write pull request comments and request an identity token. The workflow comments explain why: Claude's session has its publishing credentials removed, so the split follows the same pattern as trusted publishing for packages.

The workflow needs one repository secret, a Claude Code token, and pull requests from forks run without secrets, so they get no explainer. The pull request has no tests or results of its own, since the run it triggers is the evidence. The author says to close it afterwards, so the review is a quick read of the workflow, and nothing here is meant to merge.