chore(main): release 4.0.0

[bitwise-fast-forward-merge]

🤖 I have created a release beep boop

4.0.0 (2026-06-29)

⚠ BREAKING CHANGES

• callers must now grant pages: write. GitHub resolves a reusable workflow's permissions as the union of every job and ignores if:, so the docs job's pages:write is required even on repos without a zensical.toml or the run fails at startup. Add pages: write to the caller's permissions block (see examples/release.yaml). Consuming repos should also delete their inline docs job and set Settings -> Pages -> Source -> GitHub Actions.

Features

• build and publish Zensical docs to Pages on release (c619e32)

---

This PR was generated with Release Please. See documentation.

[github-actions]

Note

Merging this PR: this repository merges by fast-forward so every
commit keeps its original signature. The GitHub merge button is not used.
Once this PR is approved and all checks pass, a maintainer merges it by
commenting /merge on the PR.

The branch must be up to date with main (rebased and re-signed) to
fast-forward. If /merge reports it is not fast-forwardable, rebase onto
main and comment /merge again.

[dmccaffery]

/auto-merge

[bitwise-fast-forward-merge]

Note

Auto-merge armed. Once this PR is approved and every required check
passes, it will be fast-forwarded into the base branch automatically,
preserving every commit signature.

Remove the auto-merge label to cancel. If the branch is not
fast-forwardable, rebase onto the base branch and re-sign — CI re-runs
and the merge retries.

[bitwise-fast-forward-merge]

Fast-forwarded main to 4a154ffd7efb — original signature preserved, no re-sign.

[bitwise-fast-forward-merge]

🤖 Created releases:

• v4.0.0

🌻