Ripple and Glitch are gone; Crt stays

The user tried them live and wants them removed entirely: the builtins,
their levels, config keys and leader paths (tR, tg), their slots in the
built-in chain, their shaders (source and prebuilt), EffectCode paths, and
on macOS their scene flags (pardes.h), the Metal kernel's coordinate warps
and the Swift pointer mapping that mirrored them. Docs say so (decision 8
in docs/render-pipeline.md); config.md documents Crt's levels, Shader and
ShaderAnimation instead.

Shared files touched: macos.zig (flags). Not touched: pardes.zig,
Messages.zig, mouse.zig, gui.zig, detached/*.

1 files changed, 9 insertions, 12 deletions

diff --git a/docs/macos.md b/docs/macos.md
index e104d3a6..5166e2d5 100644
--- a/docs/macos.md
+++ b/docs/macos.md
@@ -102,8 +102,8 @@ asking for a thin insert caret instead of a block. `Surface.images` crosses
 separately as `pardes_frame_images` / `pardes_frame_image_list` — see "Pixel
 attachments" below.
 
-`pardes_scene` is the matching full-window snapshot: a bit each for CRT,
-ripple, and glitch, plus the 60 Hz time/frame that animates them. It is returned
+`pardes_scene` is the matching full-window snapshot: a bit for CRT, plus the
+60 Hz time/frame that animates it. It is returned
 by value, so the renderer never holds a pointer into live core state. A zero
 flags word is also the fast-path contract: draw the CoreText frame directly.
 
@@ -662,8 +662,7 @@ longer leaves a dark titlebar over a cream grid.
 
 ## Scene effects
 
-`Crt`, `Ripple`, and `Glitch` are three switches over one postprocess, not three
-stacked filters. Their canonical macOS source is `shaders/crt.ci.metal`, which
+`Crt` is one full-window postprocess. Its canonical macOS source is `shaders/crt.ci.metal`, which
 the build installs as `pardes.app/Contents/Resources/crt.ci.metal`. The Swift
 shell loads that exact asset with `CIKernel.kernels(withMetalString:)` and runs
 it through a `CIContext` created from the system Metal device. The source is
@@ -673,14 +672,12 @@ The ordinary CoreText/attachment/cursor pass is one function. With any scene
 bit or panel track it targets a retained, backing-scale bitmap; kernels then
 sample the complete frame into the flipped view. PDFs, image panes, taglines,
 rules, and the caret therefore receive the same effect. With every bit off and
-no panel track the bitmap and Core Image context are bypassed entirely. Ripple
-and glitch alter sample coordinates only, preserving theme colors; CRT works
+no panel track the bitmap and Core Image context are bypassed entirely. CRT works
 in linear light with restrained bloom, scan/mask, vignette, hum, and noise
 instead of applying a broad color remap.
 
 The scene kernel alone receives a `clampedToExtent` image and the final output
-is cropped back to the original finite extent. Coordinate tears and chroma
-samples therefore clamp to the edge exactly like SDL's scene sampler instead
+is cropped back to the original finite extent. Chroma samples therefore clamp to the edge exactly like SDL's scene sampler instead
 of acquiring transparent-black seams from Core Image's finite source image.
 
 The Zig side owns the clock. `pardes_animation_tick` increments its wrapped
@@ -689,8 +686,8 @@ from that integer. Input bursts cannot accelerate the shader.
 
 Pointer input follows the same destination-to-source transform as the last
 presented scene frame before it is divided by the cell metrics. The view keeps
-that exact `pardes_scene_s` snapshot and mirrors the Metal barrel, ripple and
-glitch sampling arithmetic in `ScenePostprocessor.sourcePoint`; pixels outside
+that exact `pardes_scene_s` snapshot and mirrors the Metal barrel arithmetic
+in `ScenePostprocessor.sourcePoint`; pixels outside
 the CRT tube have no cell. The resulting displayed-grid cell then reaches the
 core, whose panel-track mapping resolves it to canonical pane content.
 
@@ -716,8 +713,8 @@ while `pardesComposedInCore` effects only clip the already-composed core cells;
 pixel attachments have no character value and pass through unchanged.
 Because the input is the finished bitmap rather than a glyph-only
 batch, backgrounds, glyphs, taglines, rules, the caret, PDF pages, and image
-panes move and dissolve together. Scene CRT/ripple/glitch runs once after the
-panel composition.
+panes move and dissolve together. The scene CRT runs once after the panel
+composition.
 
 With no scene bit and no panel track the retained bitmap, Core Image context,
 and Metal passes are bypassed. `EffectCode Panel*` links to this Metal