fix(ci): restore pages/id-token permissions on the docs deploy job

[andypost]

The docs site stopped deploying after the recent main changes — the main runs fail with startup_failure and nothing reaches docs.freeunit.org.

Cause: the call-docs-build-push job in docs.yml lost its job-level permissions: block (removed in the recent fix(ci) commits). The reusable docs-build-push.yml deploy job requests pages: write + id-token: write, but a reusable-workflow job cannot exceed the calling job's grant — which was only the root contents: read. GitHub rejects this before any job runs → startup_failure → no deploy.

Fix: restore the permissions: block on call-docs-build-push (exactly what was present at f03c594, when #20 last deployed successfully):

  call-docs-build-push:
    uses: freeunitorg/docs/.github/workflows/docs-build-push.yml@main
    permissions:
      pull-requests: write
      contents: read
      pages: write
      id-token: write
    with:
      ...

Merging this to main retriggers the deploy, which should now succeed and publish the 1.36.0 docs.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.