From 0e61717cc59e40c6d428b07cea726fdae0ee3976 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 15 Nov 2026 10:37:25 +0000 Subject: [PATCH] docs(plan): name the ECHIDNA Julia file without a local-looking path The family plan cited the ECHIDNA file as src/julia/coprocessor.jl. Atoma has no src/julia directory, so the Hypatia structural-drift rule SD022 read the path as a stale local reference and raised a warning on the first pull request. The sentence now names the file and says that it is in the ECHIDNA Julia sources. Co-Authored-By: Claude Claude-Session: https://claude.ai/code/session_0136P7Zmp1i8PGVHkq3u2iNz --- docs/plan/FAMILY-ULTRAPLAN.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/plan/FAMILY-ULTRAPLAN.adoc b/docs/plan/FAMILY-ULTRAPLAN.adoc index 6370081..8c1722b 100644 --- a/docs/plan/FAMILY-ULTRAPLAN.adoc +++ b/docs/plan/FAMILY-ULTRAPLAN.adoc @@ -251,7 +251,8 @@ estate script `scripts/check-bench-regression.sh`. == ECHIDNA coprocessor (F10) Question from the owner: are these repositories wired to the ECHIDNA -coprocessor layer and its Julia side, `src/julia/coprocessor.jl`, and can that +coprocessor layer and its Julia side (the file `coprocessor.jl` in the ECHIDNA +Julia sources), and can that be done without friction? Answer: no repository in the family refers to the coprocessor. The wiring is