EPIC: GitNexus Electric.2 maintenance sprint

[100yenadmin]

Goal

Publish and locally activate a proven GitHub-only 1.6.10-electric.2 patch release without disrupting the existing .1 installation or live indexes.

Non-goals

• No bulk upstream sync, embeddings, reranking, live-index mutation, OpenClaw canary, npm publication, container release, or gateway restart.
• Do not touch the original dirty checkout or delete the .1 rollback prefix.

Resume identity

• Base: bd2b37ffed2d9e60c01ab16b6ba4c2c3c9acb6d4
• Worktree: /Volumes/LEXAR/repos/GitNexus-electric2-sprint
• Branch: sprint/1.6.10-electric.2
• Evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-14/gitnexus-electric-2-sprint/

Ordered work

1. Fresh MCP context metadata.
2. Provider-compatible MCP schemas.
3. Exact LadybugDB 0.18.1 plus cross-platform packaged native-load proof.
4. Separate release-preparation PR, protected GitHub release, checksum verification, side-by-side local install, wrapper switch.

Acceptance

• Zero advertised root anyOf/oneOf/allOf.
• Fresh metadata without MCP restart; denied repositories perform no metadata read.
• Clean-prefix tarball installs and native import pass on Linux, macOS, and Windows.
• All protected current-head checks and review lanes are terminal.
• Release assets verify by SHA-256; .1 remains the rollback target.

Stop conditions

Base movement, unexpected lock churn, policy bypass, native false success, platform package failure, schema key removal, unresolved release blockers, duplicate/mismatched tag, npm/container publication, or live-index mutation.

Current status

Baseline established; child issues are being created.

Exact next action

Implement the fresh MCP context metadata issue from a failing test.

Child issues

• Electric.2: refresh MCP context metadata per request #118
• Electric.2: make MCP tool schemas provider-compatible #119
• Electric.2: pin LadybugDB 0.18.1 and prove packaged native loading #120
• Electric.2: prepare, publish, and locally activate the release #121

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #117 - EPIC: GitNexus Electric.2 maintenance sprint
State: open; milestone: GitNexus Electric.2 Maintenance Sprint

Related issues/PRs: none detected from issue metadata.
Existing labels: P0, evidence-gate, fork-only, release-blocker.
Suggested labels: bug, tests.
Suggested owners: none.

Related context

• No same-repo issue/PR references detected in issue metadata.

Agent-start packet

Problem shape: EPIC: GitNexus Electric.2 maintenance sprint - ## Goal Publish and locally activate a proven GitHub-only 1.6.10-electric.2 patch release without disrupting the existing .1 installation or live indexes. ## Non-goals - No bulk upstream sync, embeddings, reranking,
Product fit: Architecture/integration issue; check repo policy, prior decisions, and operational constraints before implementation.
Implementation wedge: Start with a bounded adapter/contract or dry-run packet before changing live runtime 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: 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.
• Contract or degraded-mode proof before runtime promotion.
• 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: No explicit same-repo references detected; still safe as bounded local context.
• [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]

Capability #118 merged in PR #122 at merge commit 3d347e737f1250a69d219389fd2f08fd69f0f41d. Exact-head CI and evaOS review were green/terminal; evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-14/gitnexus-electric-2-sprint/evals/context-metadata.md.

[100yenadmin]

All four source PRs are now merged: #122 (fresh context metadata), #123 (provider-compatible schemas), #124 (exact LadybugDB 0.18.1 and cross-platform package proof), and #125 (release preparation). Fork main is e690cabf19dea108fced6ee1a7ef17e9e623ec54. Protected GitHub-only release run #29369633801 is in progress on that exact commit. No npm/container publication, indexing, embeddings, live-index mutation, canary, or OpenClaw restart is occurring. Exact next action: let the single protected run finish, approve its release environment if requested, then verify/download/install the artifact beside .1 and switch the wrapper once.

[100yenadmin]

Sprint complete. Child issues #118-#121 are closed; capability PRs #122-#124 and release PR #125 are merged. GitHub release: https://github.com/electricsheephq/evaOS-gitnexus/releases/tag/electric/v1.6.10-electric.2. Exact release head: e690cabf19dea108fced6ee1a7ef17e9e623ec54. Local default is .2; .1 remains intact and verified. Sanitized evidence was posted to upstream PR abhigyanpatwari#2439, PR abhigyanpatwari#2489, and issue abhigyanpatwari#2441. Company OS: https://app.notion.com/p/GitNexus-1-6-10-electric-2-Internal-Release-Closeout-2026-07-15-39d96299402f81279d5be78e29ff84e5. Evidence and EOS closeout: /Volumes/LEXAR/Codex/session-notes/2026-07-14/gitnexus-electric-2-sprint/. No release blocker remains. Issue #126 is intentionally outside this completed sprint and tracks future workflow hardening without changing or republishing .2.