@takazudo/zudo-doc 4.4.10 → 4.4.11

package/CHANGELOG.md

@@ -4,6 +4,20 @@ All notable changes to `@takazudo/zudo-doc` are documented in this file.
 
 The format is based on Keep a Changelog, and release notes are generated from the changelog MDX pages.
 
+## [4.4.11] - 2026-07-28
+
+A maintenance release: CI post-deploy gate reliability, the `packages/zudo-doc` dev loop, and documentation. The published package artifacts are unchanged — the build path still cleans exactly as before.
+
+### Bug Fixes
+
+- Keep `packages/zudo-doc` declarations alive during dev. `tsup --watch` ran with `clean: true` and `dts: false`, so a dev session wiped `dist/` and regenerated no `.d.ts` at all (285 → 0). `dev` now pairs `tsup --watch` with a `tsc --watch` declarations pass, and only non-watch builds clean (a705fca1f, #3126)
+- Widen the post-deploy smoke-gate retry window so slow asset propagation no longer turns a green deploy red, and split the CSS-shape action's HTML fetch from its link grep so a failure names the URL that died instead of surfacing a bare curl exit code (960ff3e3f, #3123)
+- Give the six post-deploy gate steps a failure branch naming the URL and curl's exit status. Under `set -euo pipefail` a persistent 404 aborted at the assignment, so the `::error::` annotation was unreachable — the exact diagnosability gap the gate was meant to close. Gate-carrying jobs raised to `timeout-minutes: 15` so a job timeout cannot pre-empt the annotation (5f2266eaf, #3124)
+
+### Other Changes
+
+- Document the `run-p` dev-session cascade as accepted behaviour. One watcher exiting non-zero tears down all of `pnpm dev`, because `run-p` aborts its siblings and the zudo-doc watchers are themselves a nested `run-p`. Records the trigger set (including that `tsup --watch` exits on a failed *first* build while `tsc --watch` does not), the `EMFILE` vs `ENOSPC` inotify limit distinction, and why `--continue-on-error` is the wrong remedy (b9d7d5a29, 23f0deac1, #3129)
+
 ## [4.4.10] - 2026-07-28
 
 ### Bug Fixes

package/README.md

@@ -68,6 +68,6 @@ The fix is to import the package's build-generated safelist into your Tailwind C
 
 ## Dev workflow (in this repo)
 
-This package is published to npm as `@takazudo/zudo-doc` (since `0.2.0`, `latest` tracks the current line). Inside this repo the host site consumes it as a workspace package through its compiled `dist/` — `pnpm dev` at the repo root runs `tsup --watch` so edits under `src/` rebuild automatically; for a one-off rebuild use `pnpm --filter @takazudo/zudo-doc build`.
+This package is published to npm as `@takazudo/zudo-doc` (since `0.2.0`, `latest` tracks the current line). Inside this repo the host site consumes it as a workspace package through its compiled `dist/` — `pnpm dev` at the repo root runs two watchers in parallel, `tsup --watch` for the JS and `tsc -p tsconfig.build.json --watch` for the `.d.ts`, so edits under `src/` rebuild both halves automatically; for a one-off rebuild use `pnpm --filter @takazudo/zudo-doc build`.
 
 zfb itself comes from npm (versions pinned in the root `package.json`). To develop against a local zfb checkout, use the temporary `pnpm.overrides` link escape hatch documented in the root `CLAUDE.md` — do not commit the override.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@takazudo/zudo-doc",
-  "version": "4.4.10",
+  "version": "4.4.11",
   "type": "module",
   "description": "zudo-doc framework primitives layer that sits on top of zfb's engine — sidebar, theme, TOC, breadcrumb, layouts, head injection, View Transitions, SSR-skip wrappers (per ADR-003).",
   "license": "MIT",
@@ -644,17 +644,22 @@
     "@types/string-similarity": "^4.0.2",
     "cross-env": "^7.0.3",
     "happy-dom": "^20.10.6",
+    "npm-run-all2": "^7.0.2",
     "preact": "^10.29.1",
     "preact-render-to-string": "^6.6.6",
     "tsup": "^8.0.0",
     "typescript": "^5.0.0",
     "vitest": "^4.1.0",
     "zod": "^4.3.6",
-    "@takazudo/zudo-doc-history-server": "4.4.10"
+    "@takazudo/zudo-doc-history-server": "4.4.11"
   },
   "scripts": {
     "build": "tsup && tsc -p tsconfig.build.json",
-    "dev": "tsup --watch",
+    "predev": "node ../../scripts/ensure-workspace-build.mjs",
+    "// dev": "Do NOT add `--continue-on-error` here. It stops a fatal watcher exit from cascading, but the dead watcher then fails silently — a dead dev:dts leaves dist/*.d.ts frozen while the JS keeps updating, which typechecks cleanly against stale types instead of failing loudly like #3113's absent declarations did. See the #3129 section in CLAUDE.md.",
+    "dev": "run-p dev:js dev:dts",
+    "dev:js": "tsup --watch",
+    "dev:dts": "tsc -p tsconfig.build.json --watch --preserveWatchOutput",
     "test:plugin-resolution": "node scripts/check-plugin-resolution.mjs",
     "test": "vitest run --config vitest.config.ts",
     "test:slow": "vitest run --config vitest.slow.config.ts",