ci: exclude every documents.js-family package from minimumReleaseAge

minimumReleaseAge gates every package pnpm resolves during install, not just
this repo's own direct dependencies -- bumping one sibling can pull in a fresh transitive
version of another family member, and an incomplete exclude list rejects that transitive
version if it was published within the window. Confirmed live: this repo's first
sibling-dependency-update dispatch run today failed with ERR_PNPM_NO_MATURE_MATCHING_VERSION
on a family package this repo doesn't depend on directly. Every repo's exclude list now
covers the whole documents.js family, matching the web app's own already-complete list.

Author: Mearman

pnpm-workspace.yaml

@@ -7,5 +7,9 @@ minimumReleaseAge: 60
 # Bare package names (no @version), per pnpm's own documented syntax (https://pnpm.io/settings#minimumreleaseageexclude -- "webpack" exempts every version, not just one) -- these are this org's own sibling packages, published only via their own semantic-release CI with npm OIDC trusted publishing, so a version-agnostic exemption is a deliberate, low-risk carry-forward rather than the version-pinned entries this file used to need updating on every single release, matching documents.js's/pdf-codec's/odf.js's/ooxml.js's own identical convention.
 minimumReleaseAgeExclude:
   - documents.js
+  - ooxml.js
   - odf.js
+  - document-schema.js
   - pdf-codec
+  - markdown-codec
+  - byte-codec