governance: PENDING-30..33 — banish-JS posture, build-time vignette renderer, rendering-class doctrine, versioning truth-up (Road-to-Stage-G W1.14)

PENDING.md

@@ -822,3 +822,43 @@ The Jurist's six-phase authorization map governs sequencing. Cross-cutting succe
 **Note:** Amends a jurist-authorized §SEO decision (REVIEWED-29) — flagged for jurist concurrence.
 **Files affected:** `site.hs` (sitemap rule), `apparatus-specification.md` §SEO.
 **Awaiting:** Steward + jurist authorization.
+
+## PENDING-30 — Prologue Postures: banish-JS with governed gate
+**Date:** 2026-06-07
+**Tag:** PROPOSAL
+**Summary:** Name zero-JS as an AldineXXI posture in the form of the house's existing banish-bold pattern: JS banished from the default path; admissible only through a six-condition gate (provably unachievable in HTML/CSS/build-time · reader-initiated, never ambient · observes nothing · page fully readable without it · first-party self-hosted · declared in spec, steward-authorized per instance, logged as precedent).
+**Rationale:** The 2026-06-07 audit found ARC ships zero JS as executed direction but unnamed commitment — and found the one surviving script was ungoverned residue (the unhandledrejection silencer, 312 pages), exactly the accretion a named posture forecloses. The Wave-0 analysis established that everything on the known horizon (vignette, running head, mode) is achievable without JS, so the marginal capability of a runtime is zero while its costs (fragility against ARC's for-return durability; a second runtime to govern; the privacy posture held as policy rather than structural property) are real. The gate keeps the spec honest about legitimate futures (e.g. the §III.b reader font-size control — a reader-initiated instrument) without admitting machinery. Steward ruled the direction 2026-06-07 (roadmap W1.1); this entry is the jurist-visible record for the Postures amendment.
+**Options:** (1) Banish-with-gate as above (steward-ruled). (2) Absolute prohibition (simpler, but lies about the §III.b held option). (3) Unnamed status quo (the audit showed what accretes).
+**Recommendation:** Option 1; spec text lands in the Wave-2 reconciliation pass.
+**Files affected:** `AldineXXI-specification.md` Prologue *Postures*; consequential: vignette spec Part II (PENDING-31), §VII.f implementation note (CSS scroll-driven), removal of the residual script (roadmap W3.4).
+**Awaiting:** Jurist review (framework extension per §XIV category 2; steward direction already given).
+
+## PENDING-31 — Vignette Part II: build-time SVG+CSS renderer
+**Date:** 2026-06-07
+**Tag:** PROPOSAL
+**Summary:** Revise vignette-specification.md Part II Component 3 from the browser renderer (Canvas+SVG, requestAnimationFrame, ~300–400 lines JS) to a build-time renderer: Hakyll reads the genome sidecar and emits inline SVG + CSS per piece. Part I (the lock) is untouched.
+**Rationale:** Consequence of PENDING-30. The Wave-0 fidelity table (roadmap, `drafts/road-to-stage-g-2026-06-07.md`) traces every Part-I commitment to a build-time mechanism: geometry/ground-mark as inline SVG; field via SVG filters (feTurbulence grain, gradient density, overlay luminance); breath as CSS keyframes with the generation-fixed phase offset baked as negative animation-delay; mode-awareness as build-computed light-dark() pairs (orientation-preserving by construction — structurally safer than the runtime mapping Part I warns can silently invert); reduced-motion as a CSS media query. Two approximations, both within Part I's own tolerances: field drift refreshes per deploy (≈0.04%/day against a 5–7-year monotonic cycle) and the reduced-motion still frame is the base frame rather than the phase-offset frame (amplitude ≤2%, the spec's own "visually immaterial"). The genome contract, sidecar, steward review, Phase α/ω framing, and the dwell-test gate all carry unchanged; the validate-and-save harness survives as spec'd.
+**Options:** (1) Build-time renderer (steward-ruled direction). (2) Keep Component 3 as written and open the PENDING-30 gate for it (defensible — render-time drift is exact — but pays the runtime costs for imperceptible gain).
+**Recommendation:** Option 1. Phase-1 prototype proceeds against a hand-written test genome after jurist concurrence; first prototype goes to the jurist per the dwell-test review interface regardless.
+**Files affected:** `vignette-specification.md` Part II (Component 3 + build-sequence wording); Part I untouched.
+**Awaiting:** Jurist review (Part II was jurist-passed 2026-05-29; this revises that pass).
+
+## PENDING-32 — Frontmatter §2.8: a rendering inherits its work's class
+**Date:** 2026-06-07
+**Tag:** HARDENING
+**Summary:** Codify the convention the corpus already obeys 6-for-6 but nothing governs: a rendering file declares the same `class:` as its work; optionally, the build validates the equality.
+**Rationale:** Audit finding J2 (2026-06-07, adversarially verified): all six renderings (Taliesin fr/es; bio/cv fr/es) carry their work's class, but neither frontmatter §2.8 nor content-typology states the rule, and `excludeRenderings` keys on `work:` alone — a future rendering with a divergent class would silently carry wrong apparatus/template bindings. One sentence in §2.8 closes the doctrine; a small build check (rendering's class == work's class, loud on mismatch) closes the enforcement, in the spirit of §5 clause 3.
+**Options:** (1) Doctrine sentence + build validation. (2) Doctrine sentence only.
+**Recommendation:** Option 1; the check is a few lines beside `renderingSiblings`.
+**Files affected:** `frontmatter-specification.md` §2.8; `site.hs` (validation); content-typology cross-reference.
+**Awaiting:** Jurist concurrence (amends the PENDING-25/REVIEWED-28 doctrine by extension).
+
+## PENDING-33 — Essay-versioning: truth-up and promotion from DRAFT
+**Date:** 2026-06-07
+**Tag:** PROPOSAL
+**Summary:** Amend essay-versioning-specification.md to the shipped truth and promote it from "DRAFT · design sketch" to OPERATIVE-for-the-built-scope.
+**Rationale:** Audit finding J7: the spec's mechanism is substantially live (full versioning module, /v/ routes with canonical-to-actual-route + noindex, version stamps, feed/sitemap integration) while the document still presents itself as an unbuilt sketch — the corpus's one materially dishonest status line, and Stage G should not read it in that state. The truth-up folds: (a) §4 amended to the shipped stamp shape (inline dated links to each /v/ page; no "Prior versions" index link — audit A4 judged the shipped shape arguably cleaner); (b) the §6 colophon worked-example resolved — either wire the about-page path's version stamp or re-designate the exemplar to the After-the-Reply pieces and rule the orphaned `edition_label: Fourth Edition` disposition; (c) §7 items 6–8 and the §4 retractation half explicitly marked deferred-until-need; (d) `sequence_position` → `sequence_order` (frontmatter §2.2 alignment).
+**Options:** (1) Truth-up + promote as above. (2) Truth-up only, status stays DRAFT (understates a live system). (3) Build the missing pieces first (disproportionate; no retractation piece exists).
+**Recommendation:** Option 1; (b)'s exemplar choice is a steward call inside the jurist pass.
+**Files affected:** `essay-versioning-specification.md`; possibly `site.hs`/`about-page.html` if (b) wires the stamp.
+**Awaiting:** Steward authorization + jurist review.