[Chore] Add CI check that the docs site builds on every PR touching docs

[collinsezedike]

Summary

.github/workflows/docs.yml only builds and deploys the mdBook site on push to main. A PR that breaks the book build (e.g. a bad mermaid diagram, a broken {{#include}}) currently isn't caught until after merge.

Scope

Add a mdbook build docs step to .github/workflows/ci.yml (or a separate lightweight workflow) that runs on pull requests, without deploying anything, just to catch build failures before merge.

Proposed approach

Reuse the same mdBook + mdbook-mermaid install steps already in docs.yml, but scope the trigger to pull_request and drop the deploy job.

[Johnsource-hub]

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

[Chigybillionz]

Hi, I’ve reviewed this issue and I’m confident I can fix it. I’d like to take it on.

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in 12hours

[bamiebot-maker]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[Babigdk]

Proposal

I’d like to work on this by adding a lightweight documentation validation workflow that builds the mdBook on every pull request without deploying it. I’ll reuse the existing mdBook and mdbook-mermaid setup from docs.yml to keep the configuration consistent, ensuring issues such as broken Mermaid diagrams, invalid {{#include}} directives, or other documentation build errors are detected before merge while avoiding duplicated maintenance where possible.

[grantfox-oss]

🦊 GrantFox — @Johnsource-hub has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #16)
2. Your PR will be reviewed by the drydocs maintainers

Good luck! Track your progress on GrantFox.