fix: address #42 CI follow-ups (cflite, examples/go exemption, drop Jekyll)

Three follow-up issues surfaced when #42's CI ran:

1. **cflite `PR (address)` failure** — `.clusterfuzzlite/build.sh` was
   `cp ./target/x86_64-unknown-linux-gnu/release/$target $OUT/`, but
   cargo-fuzz writes binaries to `fuzz/target/<triple>/release/<target>`
   (the fuzz crate's own target dir). The `./target/...` path was a
   vestige of an earlier layout where fuzz/ depended on the parent's
   `[lib]`, since removed. Updated the cp source path.

2. **`governance / Language / package anti-pattern policy`** — surfaced
   `examples/go/nop.go` as a banned-Go-file violation. The file is a
   per-language CNO reference (alongside `examples/c/`, `examples/clojure/`,
   `examples/javascript/nop.js`, ~30 langs total) — the Go-specific
   runtime characteristics ARE the point of the example. Added a
   `.hypatia-ignore` entry with that rationale. The repo language
   policy still bans new Go code; this is reference material.

3. **Jekyll workflow** — `.github/workflows/jekyll-gh-pages.yml`
   tripped `Workflow Security Linter` (5 unpinned actions) and is
   estate-banned anyway (Jekyll is being replaced by casket-ssg
   estate-wide). Deleted the workflow entirely. If/when this repo
   wants a docs site, add a casket-ssg build/deploy workflow modelled
   on `hyperpolymath/casket-ssg/.github/workflows/pages.yml`.

Note on the Hypatia code-scanning check failure (22 errors / 10
warnings): every alert resolves against files I'm deleting in this PR
(rescript-deno-ci.yml, jekyll-gh-pages.yml) or against pre-existing
issues on main (examples/ada/balanced_ops.adb has
`ada_pragma_suppress`, src/abi/Proofs/DivMod.idr has structural_drift
warnings). The PR doesn't add new alerts; it just causes Hypatia to
re-scan files in the diff scope. These should clear after merge as
main shrinks past the removed files. Out of scope here.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

.clusterfuzzlite/build.sh

@@ -2,6 +2,10 @@
 # SPDX-License-Identifier: MPL-2.0
 cd "$SRC"/absolute-zero
 cargo +nightly fuzz build
+# cargo-fuzz writes binaries to `fuzz/target/<triple>/release/<target>`
+# (the fuzz crate's own target dir), not to the workspace root. The
+# previous `./target/...` path was a vestige of an earlier layout where
+# fuzz/ depended on the parent crate's `[lib]` (since removed).
 for target in $(cargo +nightly fuzz list); do
-    cp ./target/x86_64-unknown-linux-gnu/release/$target $OUT/
+    cp fuzz/target/x86_64-unknown-linux-gnu/release/$target $OUT/
 done

.github/workflows/jekyll-gh-pages.yml

@@ -0,0 +1,16 @@
+# Hypatia rule exemptions for absolute-zero.
+#
+# Format: `<rule_id>:<file_path_relative_to_repo_root>` (one per line).
+# Comments (lines starting with #) and blank lines are ignored.
+#
+# Adding an entry requires a stated rationale below the line so the
+# exemption survives review and audit.
+
+# Per-language CNO reference example. `examples/<lang>/` is a 30-language
+# showcase comparing how each language expresses "do absolutely nothing"
+# — the Go-specific runtime characteristics (goroutine scheduler init,
+# GC startup, runtime.GOMAXPROCS) are the point of the example. Mirrors
+# the rationale for keeping `examples/javascript/nop.js` (also a
+# per-language reference). The repo language policy still bans new Go
+# code; this is reference material, not implementation.
+cicd_rules/banned_language_file:examples/go/nop.go