From f613cf25d2caaa3b87442ff7800c30facb8828c4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C3=81Z=C3=81R=20Imre=20AI=20Agent?= Date: Thu, 16 Jul 2026 13:49:14 +0200 Subject: [PATCH] build(baseline): use submodule content as-is (authoritative), no LF normalize MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Live has mixed CRLF/LF and content drift vs the submodule HEADs, so normalizing would break the currently-matching files. The baseline reflects the authoritative developer repos; line-ending handling is a verifier concern. Signed-off-by: LÁZÁR Imre Assisted-by: claude-code@claude-opus-4-8 --- build-baseline.sh | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/build-baseline.sh b/build-baseline.sh index 2eee9a1e..064703cf 100755 --- a/build-baseline.sh +++ b/build-baseline.sh @@ -66,16 +66,13 @@ if [ -d "$ROOT/overrides" ]; then rsync -a --exclude='.gitkeep' "$ROOT/overrides/" "$OUT/" fi -# 5b) Deploy transform for the submodule-sourced dirs: the developer repos -# (cadcommonlib, maintenance) store CRLF line-endings; the deployed live form -# is LF. Normalize the text files to LF so the baseline byte-matches deployment. -log "normalize: line-endings (common_cadline_libraries, maintenance) -> LF" -for dir in "$OUT/common_cadline_libraries" "$OUT/maintenance"; do - [ -d "$dir" ] || continue - find "$dir" -type f 2>/dev/null | while IFS= read -r f; do - grep -Iq . "$f" 2>/dev/null && sed -i 's/\r$//' "$f" - done -done +# NOTE: common_cadline_libraries + maintenance come from the authoritative +# developer submodules (cadcommonlib, maintenance) as-is. Their content currently +# diverges from the live docroot (mixed line-endings + a content drift on +# crm_hardlock.class.php / POfile.php) because live was not last deployed from the +# submodule HEADs. The baseline reflects the authoritative repos; the HIDS flags +# the live divergence until live is re-deployed or the drift is reconciled. +# Line-ending normalization is intentionally left to the verifier, not applied here. # 6) Safety net — malware IOC + scan artifacts must never appear in the baseline # (the sources above already exclude them; this is defensive, documented in