neuron-technologies/el-retired
Archived
3
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases 5 Wiki Activity

[SNAPSHOT — DO NOT MERGE] Live darwin soul runtime (el-sdk) — capture for history + reconciliation #56

Closed
tim.lingo wants to merge 1 commits from chore/live-darwin-runtime into main
pull from: chore/live-darwin-runtime
merge into: :main
Conversation 1 Commits 1 Files Changed 2
+29 -355
tim.lingo commented 2026-06-16 00:40:02 +00:00
Member
Copy Link
Copy Source

This captures the live, previously un-versioned macOS soul runtime into git. It is a reference snapshot — do NOT blind-merge (the diff is deletion-heavy because the snapshot lags main on newer functions).

Why

~/el-sdk/el_runtime.c is the source the live macOS soul (:7770, 765760 B) is actually built from, and it was in no git repo — the only copy of several data-integrity fixes. One rm and they were gone with no history. This branch preserves it.

What this snapshot HAS that main lacks

  • UAF fix — engram_node_full uses el_strdup_persist (27 sites vs 19 on main). This is the documented root cause of the hallucinated/lost-saves bug class.
  • Response-truncation fix — max(strlen, _tl_fs_read_len) binary-safe reads.

What main has that this snapshot LACKS (why the diff shows ~355 deletions)

  • engram_wm_*, engram_load_merge, http_serve_async (main commit 35c1897 — "needed by soul CI").

Still missing everywhere

  • Atomic engram_save (temp + fsync + rename) — the engram-clobber fix; diagnosed, not yet written (see neuron #21).

Recommended reconciliation (Will)

Do NOT merge this over main. Instead port the two fixes above forward onto main (and ideally add atomic save), so one canonical lang/el-compiler/runtime/el_runtime.c has: main’s newer fns + UAF + truncation + atomic save. Then make the soul build from that versioned source instead of ~/el-sdk. Also reconcile with feat/windows-el-runtime (#55) which ports the same file to Windows.

🤖 Generated with Claude Code

**This captures the live, previously un-versioned macOS soul runtime into git. It is a reference snapshot — do NOT blind-merge (the diff is deletion-heavy because the snapshot lags main on newer functions).** ## Why `~/el-sdk/el_runtime.c` is the source the live macOS soul (`:7770`, 765760 B) is actually built from, and it was in **no git repo** — the only copy of several data-integrity fixes. One `rm` and they were gone with no history. This branch preserves it. ## What this snapshot HAS that `main` lacks - **UAF fix** — `engram_node_full` uses `el_strdup_persist` (27 sites vs 19 on main). This is the documented root cause of the hallucinated/lost-saves bug class. - **Response-truncation fix** — `max(strlen, _tl_fs_read_len)` binary-safe reads. ## What `main` has that this snapshot LACKS (why the diff shows ~355 deletions) - `engram_wm_*`, `engram_load_merge`, `http_serve_async` (main commit 35c1897 — "needed by soul CI"). ## Still missing everywhere - **Atomic `engram_save`** (temp + fsync + `rename`) — the engram-clobber fix; diagnosed, not yet written (see neuron #21). ## Recommended reconciliation (Will) Do NOT merge this over main. Instead **port the two fixes above forward onto main** (and ideally add atomic save), so one canonical `lang/el-compiler/runtime/el_runtime.c` has: main’s newer fns + UAF + truncation + atomic save. Then make the soul build from that versioned source instead of `~/el-sdk`. Also reconcile with `feat/windows-el-runtime` (#55) which ports the same file to Windows. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
tim.lingo added 1 commit 2026-06-16 00:40:03 +00:00
chore(runtime): snapshot the LIVE darwin soul runtime (el-sdk) into git
El SDK Release / build-and-release (pull_request) Failing after 13s
Details
8d4c5f34bf 
Verbatim capture of ~/el-sdk/el_runtime.{c,h} — the un-versioned source the live
macOS soul (:7770, 765760B) is actually built from. Captured so the data-integrity
fixes that exist ONLY in this file are no longer one rm away from gone with no history.

Contains (vs origin/main): the UAF fix (engram_node_full uses el_strdup_persist —
the hallucinated/lost-saves root cause; 27 sites vs 19) and the response-truncation
fix (max(strlen,_tl_fs_read_len) binary-safe reads).

DIVERGES BOTH WAYS: this snapshot LACKS main's newer engram_wm_*, engram_load_merge,
http_serve_async (diff is deletion-heavy as a result) and still lacks the atomic
engram_save (temp+fsync+rename) fix. DO NOT merge over main — reconcile by porting
the two fixes above forward onto main.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
tim.lingo commented 2026-07-17 13:59:12 +00:00
Author
Member
Copy Link
Copy Source

Closing: this snapshot served its purpose — the darwin runtime has since been reconciled upstream (darwin elb, elc OOM fix #77, dist regen). The capture is preserved on branch chore/live-darwin-runtime for history. — Tim (via Neuron)

Closing: this snapshot served its purpose — the darwin runtime has since been reconciled upstream (darwin elb, elc OOM fix #77, dist regen). The capture is preserved on branch chore/live-darwin-runtime for history. — Tim (via Neuron)
tim.lingo closed this pull request 2026-07-17 13:59:18 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
BETA-CRITICAL
On the beta critical path — must resolve before ship
 HELD
Blocked pending an external decision (counsel / dual sign-off)
 ORTHOGONAL
Parallel workstream (testing/hardening) — safe to assign off critical path
 POST-BETA
Important but not blocking the beta ship
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
andre.almeida (Andre Almeida) tim.lingo (Tim Lingo) will.anderson (Will Anderson)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: neuron-technologies/el-retired#56
Delete Branch "chore/live-darwin-runtime"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?