Electric.2: pin LadybugDB 0.18.1 and prove packaged native loading

[100yenadmin]

Parent: #117

Pin @ladybugdb/core exactly to 0.18.1 with lock-only installation and reject unrelated lock churn. Strengthen the GitHub-only release workflow so the same tarball is installed into clean prefixes on Linux, macOS, and Windows and directly proves native import plus CLI version/help/MCP help.

Acceptance: exact version and native import pass on all three runners; release cannot proceed on failure. Doctor output alone is not accepted because its native failure currently exits zero.

Evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-14/gitnexus-electric-2-sprint/

[100yenadmin]

Implementation is now in PR #124 at exact head aa7996a93a543df024f4931c330ad918ffa559be. Focused release-policy/package-verifier tests pass 43/43, actionlint and formatting pass, the exact 0.18.1 pin is confirmed, and a real clean-prefix tarball install passed checksum, native import, CLI, and MCP help proof. The remaining gate is exact-head cross-platform GitHub Actions plus terminal review.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #120 - Electric.2: pin LadybugDB 0.18.1 and prove packaged native loading
State: open; milestone: GitNexus Electric.2 Maintenance Sprint

Related issues/PRs: #117.
Existing labels: P0, evidence-gate, release-blocker.
Suggested labels: bug, docs.
Suggested owners: none.

Related context

• EPIC: GitNexus Electric.2 maintenance sprint #117 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: Electric.2: pin LadybugDB 0.18.1 and prove packaged native loading - Parent: #117 Pin @ladybugdb/core exactly to 0.18.1 with lock-only installation and reject unrelated lock churn. Strengthen the GitHub-only release workflow so the same tarball is installed into clean prefixes on Linux,
Product fit: Implementation issue; keep product fit lightweight unless VISION.md/repo policy raises a constraint.
Implementation wedge: Start with a focused fixture or dry-run path that proves the issue shape before widening behavior.

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: deferred; no product, architecture, UX, library-choice, integration, roadmap, or market-positioning trigger detected.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.

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.

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.

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.
• [deferred] allowlisted_cross_repo_github: Deferred until product, UX, market-positioning, or library-choice signal appears.
• [deferred] external_oss_examples: Deferred for low-research-value issue class.
• [deferred] library_api_docs: Deferred unless a library/API decision is present.
• [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]

Exact-head capability proof is now running at 197dbaedd4207a14a63a43d4706cea7d486af357. Focused policy/verifier tests pass 56/56. The prior Windows packaged-install failure was a diagnostic assertion gap for deliberate launcher removal (Windows emitted ENOENT); the package still failed closed as required. That assertion and cross-Node timeout classification are now covered. Merge remains gated on current-head CI, terminal review threads, and release-provenance review.