Restore GitHub Pages deploy after repository move

[Copilot]

The deploy Actions job started failing when actions/deploy-pages attempted to create a Pages deployment and received 404 Not Found. The workflow was still assuming the old Pages/repository setup after the move to astrid-runtime/book.

• Pages workflow initialization

  • Add actions/configure-pages@v5 to the build job so the workflow resolves the current Pages base path before building.
  • Pass steps.pages.outputs.base_path into MDBOOK_OUTPUT__HTML__SITE_URL instead of hardcoding /book/.

• Pages deploy action

  • Move actions/deploy-pages to @v5 so deploy uses the current Pages action path alongside configure-pages.

• Repository metadata

  • Update book.toml GitHub links from unicity-astrid/book to astrid-runtime/book so generated repo/edit links point at the live repository.

- name: Setup Pages
  id: pages
  uses: actions/configure-pages@v5

- name: Build
  run: mdbook build
  env:
    MDBOOK_OUTPUT__HTML__SITE_URL: ${{ steps.pages.outputs.base_path }}/

[Copilot]

Pull request overview

This PR updates the GitHub Pages deployment workflow and repository metadata after moving the repo to astrid-runtime/book, ensuring Pages builds and deploys correctly under the new configuration.

Changes:

• Add actions/configure-pages@v5 and use its base_path output to set MDBOOK_OUTPUT__HTML__SITE_URL dynamically.
• Upgrade actions/deploy-pages from @v4 to @v5.
• Update book.toml repository/edit URLs to point at astrid-runtime/book.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
book.toml	Updates generated repository/edit links to the new GitHub org/repo.
.github/workflows/deploy.yml	Aligns Pages build/deploy steps with current Pages actions and dynamic base path resolution.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.