R04: Resolve LadybugDB 0.18.0 versus 0.18.1

[100yenadmin]

Compare RC-pinned LadybugDB 0.18.0 with 0.18.1 in isolated locks on macOS ARM, macOS without Homebrew assumptions, Linux, and Windows. Exercise delete/checkpoint behavior and a forced native-load failure. Coordinate on upstream GitNexus abhigyanpatwari#2441 and LadybugDB abhigyanpatwari#681; do not create duplicates.

Acceptance: the selected version completes checkpoint workloads, loads on supported platforms, and makes a failed native load return non-zero. The local-only 7171cf3d remains evidence, not an automatic cherry-pick.

Validation: matrix artifacts, package/lock diff, subprocess exit codes, and linked upstream findings.

Parent epic: #39

Tracking ID: R04

[100yenadmin]

Local comparison is complete; the cross-platform gate remains open.

Evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-13/gitnexus-fork-upstream-reconciliation/r04-ladybug-disposition.md

At RC19 d43c479a on macOS ARM:

• 0.18.0: native load pass; 50/50 focused tests pass
• 0.18.1: native load pass with Homebrew OpenSSL; 50/50 focused tests pass
• both: forced zero-byte native module makes analyze exit 1 and creates no index
• 0.18.1 still links absolute /opt/homebrew/opt/openssl@3 paths

Coordination:

• Bug: analyze exits 0 after LadybugDB native load failure — silently does nothing while reporting success abhigyanpatwari/GitNexus#2441 (comment)
• Bug: darwin-arm64 prebuilt lbugjs.node hardcodes Homebrew OpenSSL paths — dlopen fails on Macs without Homebrew (regression from 0.15.3) LadybugDB/ladybug#681 (comment)

Disposition: keep RC19's 0.18.0 pin. Do not replay local commit 7171cf3d or select 0.18.1 until Linux, Windows, and Homebrew-free macOS jobs pass.

[100yenadmin]

Important correction from the resumed R04 inspection: RC19's 0.18.0 binary also links absolute /opt/homebrew/opt/openssl@3 paths. This is not unique to 0.18.1.

Updated evidence: r04-ladybug-disposition.md

Disposition:

• neither 0.18.0 nor 0.18.1 currently satisfies the macOS portability gate
• keep 0.18.0 only in the RC laboratory
• do not replay 7171cf3d
• R04 stays open pending an upstream linkage/resolution fix plus Linux, Windows, and non-Homebrew macOS proof

Upstream correction: LadybugDB abhigyanpatwari#681.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #43 - R04: Resolve LadybugDB 0.18.0 versus 0.18.1
State: open; milestone: GitNexus v1.6.10 Reconciliation - Sprint 0 - Immutable Baseline

Related issues/PRs: abhigyanpatwari#2441, abhigyanpatwari#681, #39.
Existing labels: dependencies, reconciliation, P0, evidence-gate, release-blocker.
Suggested labels: bug, support.
Suggested owners: none.

Related context

• Bug: analyze exits 0 after LadybugDB native load failure — silently does nothing while reporting success abhigyanpatwari/GitNexus#2441 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• [SM-16] Restructure resolveUncached — replace Tier 2a/2b data source abhigyanpatwari/GitNexus#681 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• EPIC: Reconcile evaOS GitNexus with upstream v1.6.10 #39 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: R04: Resolve LadybugDB 0.18.0 versus 0.18.1 - Compare RC-pinned LadybugDB 0.18.0 with 0.18.1 in isolated locks on macOS ARM, macOS without Homebrew assumptions, Linux, and Windows. Exercise delete/checkpoint behavior and a forced native-load failure. Coordinate on
Product fit: Implementation issue; keep product fit lightweight unless VISION.md/repo policy raises a constraint.
Implementation wedge: Prototype the candidate module behind a config flag or fixture before committing to the dependency.

Build / borrow / buy scan:

• Build: identify the smallest implementation wedge that proves the issue without broad rollout.
• Borrow: inspect same-repo prior art, repo memory, GitNexus context, and allowlisted cross-repo examples first.
• Buy/use: run capped external OSS/library/API/current-market research with citations, observed dates, and why each source matters.
• Library choice: compare maintenance, API fit, license, bundle/runtime cost, and integration proof.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.
• Allowlisted cross-repo GitHub examples with direct issue/PR/repo URLs.
• External OSS repositories or library/API docs with freshness dates.

Acceptance criteria:

• Preserve and execute the issue's stated acceptance criteria.
• Include source citations for any external OSS/library/current-market claims.
• Keep issue-enrichment comments sticky and idempotent.
• Keep labels, owners, reviewers, and roadmap fields suggestion-only.

Proof plan:

• Focused unit/fixture test for the changed planner behavior.
• Dry-run issue-enrichment evidence packet before live comment posting.
• Redaction check for issue body, citations, and generated markdown.
• Dependency/license/API-fit note before adding or relying on a package.

Known traps:

• Do not treat related links as proof by themselves; each source needs a reason why it matters.
• Do not scan old issue backlogs or exceed repo-level enrichment throttles.
• External research must stay capped, cited, fresh-dated, and redacted.

Non-goals:

• Do not auto-apply labels, owners, reviewers, roadmap fields, or milestones.
• Do not bulk-enrich old backlog issues from this planner output.
• Do not claim external market or OSS research was performed unless cited sources are present.

Context-source taxonomy:

• [enabled] vision_repo_policy_memory_gitnexus: Use repo vision, policy, memory, and GitNexus first before external research.
• [enabled] same_repo_issues_prs: Issue metadata contains same-repo references.
• [enabled] allowlisted_cross_repo_github: Triggered by issue class; keep to configured allowlist and source caps.
• [enabled] external_oss_examples: Use for build/borrow/buy precedent with citations and observed dates.
• [enabled] library_api_docs: Use when implementation may depend on a module, SDK, API, or framework choice.
• [deferred] current_market_examples: Deferred for implementation-only issues.
• [enabled] internal_mcp_docs: Use internal docs/MCP context when available; missing context is degraded, not blocking.

Validation suggestions

• Confirm owner, acceptance criteria, and validation evidence before implementation.

Triage gaps

• Owner or reviewer signal not detected in issue body.

No labels, owners, reviewers, or roadmap fields were changed by this bot.

[100yenadmin]

R04 now has a concrete upstream repair:

• LadybugDB draft PR fix(nodejs): resolve OpenSSL through macOS rpaths LadybugDB/ladybug#682
• rewrites macOS OpenSSL dependencies to @rpath
• embeds Homebrew ARM, Homebrew Intel, and MacPorts search roots
• does not bundle or statically link OpenSSL
• re-signs and verifies the Mach-O addon before artifact upload

Local red/green proof:

• verifier fails on the published 0.18.1 addon before relocation
• relocation passes and is idempotent
• relocated addon loads successfully in Node
• Bash syntax, ShellCheck, and diff checks pass

PR abhigyanpatwari#682 is mergeable and repository checks are queued. Its authoritative Node macOS ARM/Intel matrix is dispatch-only, so R04 remains open pending maintainer dispatch plus Linux/Windows evidence.

[100yenadmin]

R04 continuation update:

• Evidence-only draft PR test(ladybug): compare 0.18.1 on the RC19 matrix #65 changes only the package and lock from RC19 Ladybug 0.18.0 to exact 0.18.1 and is running the same Ubuntu/Windows/macOS matrix as the 0.18.0 baseline in test(ci): prove pristine v1.6.10-rc.19 floor #64.
• This comparison does not select or propose merging 0.18.1. Published 0.18.1 still carries absolute Homebrew OpenSSL paths.
• fix(nodejs): resolve OpenSSL through macOS rpaths LadybugDB/ladybug#682 remains the upstream @rpath repair, with local verifier red/green, idempotence, Node load, Bash, and ShellCheck proof. Its authoritative macOS ARM/Intel artifact matrix still requires maintainer dispatch.

R04 stays open until the paired GitNexus runs and upstream artifact run satisfy the complete native-load/checkpoint contract.

[100yenadmin]

R04 artifact update:

• Ladybug precompiled run 29227829393 completed 8/8 green at PR [SM-17] Replace lookupFuzzy in named-binding-processor.ts abhigyanpatwari/GitNexus#682 head
  d61f8590, including macOS ARM and Intel.
• Node run 29230524989 completed 5/5 green after an evidence-only fork
  repository override.
• A stronger Node run 29231227559 completed 5/5 green after both macOS jobs
  hid the Homebrew OpenSSL copies and loaded from /opt/local/lib.
• The fork run-ID routing bug was filed as LadybugDB [SM-18] Delete lookupFuzzy, lookupFuzzyCallable, globalIndex, callableIndex abhigyanpatwari/GitNexus#683 with draft PR [SM-19] Delete resolveCallTarget — replace with thin dispatcher abhigyanpatwari/GitNexus#684.
• PR [SM-17] Replace lookupFuzzy in named-binding-processor.ts abhigyanpatwari/GitNexus#682 is ready for maintainer review. All ordinary checks and artifact
  contracts are green.
• All 19 ordinary fork workflows are disabled again; default branch is
  main; zero runs are queued or active.

R04 stays open because published 0.18.0 and 0.18.1 still lack the repair.
Exact next action: merge abhigyanpatwari#682, release a containing artifact, then repeat the
focused GitNexus install/load/checkpoint checks against that exact version.

Evidence:
/Volumes/LEXAR/Codex/session-notes/2026-07-13/gitnexus-fork-upstream-reconciliation/r04-ladybug-disposition.md

[100yenadmin]

Current-head checkpoint:

• Ladybug [SM-17] Replace lookupFuzzy in named-binding-processor.ts abhigyanpatwari/GitNexus#682: ready, mergeable, six ordinary checks green, zero current
  review threads, authoritative artifact proof green.
• Ladybug [SM-19] Delete resolveCallTarget — replace with thin dispatcher abhigyanpatwari/GitNexus#684: ready, mergeable, six current-head checks green, zero current
  review threads.
• GitNexus docs: document shared-first contributor setup abhigyanpatwari/GitNexus#2448 and ci: update setup composites to setup-node v6 abhigyanpatwari/GitNexus#2451: ready and mergeable with zero current review
  threads; Vercel authorization remains an upstream-team check.
• Requested CodeRabbit review on [SM-17] Replace lookupFuzzy in named-binding-processor.ts abhigyanpatwari/GitNexus#682/[SM-19] Delete resolveCallTarget — replace with thin dispatcher abhigyanpatwari/GitNexus#684 has not produced a terminal review.
• GitNexus RC19 unit suite fails because plugin manifests remain at 1.6.9 abhigyanpatwari/GitNexus#2445 still has no maintainer workflow approval.
• Upstream GitNexus main remains c6445096; stable v1.6.10 is absent.

R06+ remains frozen. Exact next action is maintainer review/approval and the
first corrected upstream release artifact; no fork feature port should begin
before those Sprint 0 gates close.