{"agent":"claude","input":"Add a GitHub Actions workflow that builds this Jekyll site with its own Gemfile and deploys it to GitHub Pages. Read the Gemfile, Gemfile.lock, _config.yml, the gemspec if there is one, the existing workflows and the root pages first. Write .github/workflows/pages.yml from GitHub's Jekyll starter with current action versions: a build job with ruby/setup-ruby and bundler-cache, actions/configure-pages, bundle exec jekyll build with --baseurl from the configure-pages output and JEKYLL_ENV production, and actions/upload-pages-artifact; a deploy job on the github-pages environment with actions/deploy-pages; permissions contents read, pages write and id-token write; and a pages concurrency group that does not cancel in progress. Add a .ruby-version matching the Ruby the workflow uses and a dependabot entry for github-actions. In the sandbox install that Ruby, run bundle install against the existing lockfile and, only if it fails, bundle update within the Gemfile's constraints in a separate commit; then build, check the output has every post and page, serve it and open it in the browser, and run actionlint. In the pull request say that the Pages source must be switched to GitHub Actions by hand and why a workflow build is used instead of the Pages pipeline for this Gemfile.","resources":[{"url":"https://github.com/your-org/your-app"}]}