chore(memory): V1-2.2 root visibility evidence, A6 decision, BDR-089/090, LRN-102
This commit is contained in:
1 parent
a095ea0e1b
commit
958228a9de
8 files changed
+140
-9
No files matched your search
@@ -702,3 +702,10 @@ Supersedes [[LRN-099]].
|
||||
|
||||
**Future application**: new SVG/CSS consumer reuses `url_openings`/`local_url_target`, never own parser. Hostile tests written apart from reader, assert browser behaviour.
|
||||
Supersedes [[LRN-100]].
|
||||
|
||||
## LRN-102 — Unquoted heredocs expand backticks: quote the delimiter, scan before commit (2026-10-30) (2026-10-30)
|
||||
**Pattern**: unquoted heredoc (`<<EOF`) runs command substitution on backticks and `$(…)` inside body. Markdown/Rust doc text with `` `id` `` became output of `id` (uid, groups incl. sudo, lxd) inside test doc comment; caught by fresh verifier before commit (V1-2.2 K, 2026-10-30). Same run: `` `tests/svg_reserved_ids.rs` `` and `` `snapshot_invalid` `` erased silently (shell errors only on stderr).
|
||||
|
||||
**Context**: any shell-written file holding backticks: Rust/TS doc comments, markdown, commit bodies, python snippets passed via `python3 - <<EOF`.
|
||||
|
||||
**Application**: always quote delimiter (`<<'EOF'`, `<<'PYEOF'`) unless expansion wanted; prefer Write/Edit tools for prose; before commit grep added lines for `uid=`, `gid=`, home paths and empty backtick pairs; treat `command not found` lines during a file write as corruption signal, re-read file.
|
||||
Reference in new issue
Block a user