From 15e304e0c3a9a5ae0e0ff818f8bcd3c5254d0667 Mon Sep 17 00:00:00 2001 From: jknapp Date: Wed, 5 Aug 2026 11:41:03 -0700 Subject: [PATCH] docs(lsphp): the build assertion probes with -i, not -m The comment describing the assertion still said 'lsphp -m | grep' while the code correctly uses -i. That is the exact trap documented three lines below -- lsphp is the LSAPI SAPI and answers -m by printing usage and exiting 0, so an -m based check never matches and never fails. Leaving the comment wrong would invite someone to 'restore' it. Co-Authored-By: Claude Opus 5 (1M context) --- Dockerfile.lsphp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dockerfile.lsphp b/Dockerfile.lsphp index 38451ec..c884838 100644 --- a/Dockerfile.lsphp +++ b/Dockerfile.lsphp @@ -87,7 +87,7 @@ RUN bash -c 'set -e; \ ## cac_path_parity.from/.to mapping, so it is safe in any context (including ## wp-cli runs, where $_SERVER carries no filesystem paths). ## -## The trailing `lsphp -m | grep` is a BUILD-TIME ASSERTION: if the .so fails to + grep` is a BUILD-TIME ASSERTION| grep` is a BUILD-TIME ASSERTION: if the .so fails to ## load (ABI drift after a base-image PHP bump, bad build) the image build fails ## here rather than shipping a sidecar that silently lost path parity. ## NOTE: probe lsphp with `-i` ONLY. The lsphp binary is the LSAPI SAPI, not the