EPIC: Reconcile evaOS GitNexus on the v1.6.10 RC lineage

[100yenadmin]

Goal

Rebuild the Electric Sheep GitNexus distribution on the proven upstream v1.6.10 RC lineage, retaining only the minimum proven fork delta while inheriting upstream reliability, compatibility, and security fixes. A future stable v1.6.10 is new reconciliation input rather than a blocker for the internal source candidate.

Current baseline

• Fork: electricsheephq/evaOS-gitnexus
• Fork remote main: 86b3d3529092fcb74983a0357dd82a1db3c4a5b5
• Preserved local-only commit: 7171cf3d3cb7dbe19499ba6c95f0e5c2820abc19
• Upstream main at latest promotion check: 1482c0bc89d2e458df4e846a3db09753f72718cd
• RC laboratory base: v1.6.10-rc.19, peeled commit d43c479ac58c18d397958f48a99465d6c3110b1d
• Stable v1.6.10: still absent; R20 R20: Repin reconciliation from RC19 to stable v1.6.10 #59 records the explicit internal RC19 disposition
• Audit divergence: fork remote main 31 commits ahead and 181 behind upstream main
• Existing recovery issues: [safety] Add preservation-only recovery for interrupted incremental analysis #36, [bug] Large follow-up incremental crashes in NodeBatchInsert error handler #37, [bug] Incremental analyze crashes in LadybugDB FTS delete hook #38

Non-goals

• No history rewrite, bulk upstream merge, or replay of the 1,574-file synchronization commit.
• No npm publication, GitHub release, runtime rollout, or live-index mutation.
• No work on roadmap issues Graduated lazy-retrieval ladder (card → skeleton → hot-path → policy-gated full source) #28, Live / dirty-buffer indexing to eliminate index staleness (overlay + checkpoint) #29, or SCIP compiler-verified edges to raise depth≥2 trace confidence above heuristic tree-sitter #30 in this program.
• No upstream contribution containing Electric Sheep names, private repository policy, credentials, customer data, or premium defaults.

Evidence and decision record

• Audit: /Volumes/LEXAR/Codex/session-notes/2026-07-13/gitnexus-fork-upstream-reconciliation/audit.md
• Integration plan: /Volumes/LEXAR/Codex/session-notes/2026-07-13/gitnexus-fork-upstream-reconciliation/integration-plan.md
• GitHub issue specification: /Volumes/LEXAR/Codex/session-notes/2026-07-13/gitnexus-fork-upstream-reconciliation/github-issue-specs.json

Milestones

• Sprint 0: Immutable Baseline
• Sprint 1: Reliability and P0 Preservation
• Sprint 2: Bounded and Secure Agent Interfaces
• Sprint 3: Retrieval Resilience and Scale Proof
• Sprint 4: Internal RC19 Promotion and Governance

Sprints are evidence-gated, not calendar-gated. A later sprint may not make its predecessor's unresolved blocker disappear.

Promotion gate

• Peeled upstream v1.6.10-rc.19 at d43c479a is the truthful internal base; stable v1.6.10 remains absent.
• Required current-head GitHub checks are green.
• Two successful exact-head bounded release canaries complete with retained evidence. Each must cover real LadybugDB/FTS/VECTOR state, add/edit/rename/delete, importer closure, a 50-plus-file escalation, all four recovery boundaries, forced equivalence, embeddings, dirty state, sidecars, and process exits in a fresh disposable repository/home.
• Full OpenClaw-corpus analysis remains a nonblocking scale soak/diagnostic lane; it is not repeated for every candidate because it redundantly rebuilds the complete graph and deterministic embedding corpus for hours.
• Every fork-ahead and local-only commit has a terminal disposition.
• No unexpected embedding loss, false-success exit, native crash, stuck dirty marker, unsafe rebuild, or unbounded effective write set remains.
• Operational confidence is at least 95%.

Stop conditions

Stop implementation and update this epic if any of these occur:

• embedding loss or unexplained count/model/dimension change;
• native crash or native-load failure that exits zero;
• stuck dirty marker, unsafe rebuild, or escalation failure;
• validation would require the live index or its only copy;
• upstream advances materially enough to invalidate the pinned base;
• current user-owned dirty files would be overwritten;
• publication, release, default-branch replacement, or runtime mutation becomes necessary.

Child issues

Every child issue must link this epic, its milestone, validation evidence, blocker, and exact next action before pause or handoff.

Sprint	Issues
Sprint 0	R01 #40, R02 #41, R03 #42, R04 #43, R05 #44
Sprint 1	R06 #45, R07 #46, R08 #47, R09 #48, R10 #49
Sprint 2	R11 #50, R12 #51, R13 #52, R14 #53, R15 #54
Sprint 3	R16 #55, R17 #56, R18 #57, R19 #58
Sprint 4	R20 #59, R21 #60, R22 #61, R23 #62, R24 #63

Existing incident evidence routes into the program as follows:

• [safety] Add preservation-only recovery for interrupted incremental analysis #36 interrupted incremental preservation -> R10 R10: Specify interrupted-analysis preservation contract #49
• [bug] Large follow-up incremental crashes in NodeBatchInsert error handler #37 NodeBatchInsert crash -> R08 R08: Validate and disposition NodeBatchInsert crash issue #37 #47
• [bug] Incremental analyze crashes in LadybugDB FTS delete hook #38 FTS deletion crash -> R09 R09: Validate and disposition FTS deletion crash issue #38 #48

Pull requests

Focused fork PRs #64-#97 implement and validate the capability stack. Source-only promotion PR #98 is mergeable at 2ec953bda2dbccfa2605cea2992879925d277e54; its runtime tree is the validated 59ad8d906fea9858d6f5e31fbd2d5c90bbc20b8a candidate, plus only the governance, diagnostic-harness, wiki-output, and immutable-base-image repairs proven in #99-#108. Sanitized upstream contributions are linked from R23 #62; upstream acceptance is nonblocking.

Current status

R01-R24 are dispositioned. Exact-head PR #96 and #97 matrices are green with 39 checks each; promotion PR #98 has 57 passing checks, five intentional skips, zero pending checks, every required context green, exact-head CodeRabbit approval, and 23/23 resolved review threads. Two bounded release canaries passed in 622.35s and 622.52s; preserved local head, dirty files, tags, fork main, and live indexes remain untouched. One non-required stale CodeQL policy snapshot is specifically dispositioned in the evidence packet; its current security instances are fixed. Exact next action: make a separate product-owner source-merge decision. Do not rerun canaries or merge, publish, release, deploy, roll out, or mutate a live index under this program.