[RELEASE] Ship and install 1.6.10-electric.3

[100yenadmin]

Parent: #130

Goal

Ship electric/v1.6.10-electric.3, install it side-by-side with .2, select it through the common wrapper, and prove Codex plus Claude runtime behavior.

Non-goals

No npm, container, customer, or public runtime rollout. A merge or green PR is not release/install/runtime proof.

Required gates

• All release-blocking source PRs merged with exact-head required checks, approval, and current-head thread readback.
• Final protected-main workflows pass on the release SHA.
• Tarball install and gitnexus --version prove the artifact.
• Install under /Volumes/LEXAR/Codex/tools/gitnexus/1.6.10-electric.3; preserve .2 and timestamped wrapper/config snapshots.
• Rewrite Codex and both Claude GitNexus environments from the canonical absolute-path manifest.
• After restart, each agent runs two successive OpenClaw/Hermes semantic queries with semantic_mode=vector-index, no partial/exact refusal, and a live second call.

Rollback

Restore the previous wrapper/config snapshot and select .2; preserve registry/index archives. Do not claim rollback until the restored wrapper initializes.

Stop conditions

Stop on missing required main checks, skipped VECTOR coverage, failed tarball smoke, wrapper/config drift, missing rollback, registry mismatch, or failed agent runtime proof.

Exact next action

After source PR merges and release soaks, create the version/tag PR from current protected main and record exact artifact identity.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #137 - [RELEASE] Ship and install 1.6.10-electric.3
State: open; milestone: GitNexus Repository Health & Large-Repo Reliability Sprint

Related issues/PRs: #130.
Existing labels: P0, evidence-gate, fork-only, release-blocker.
Suggested labels: tests, support.
Suggested owners: none.

Related context

• EPIC: Restore truthful semantic retrieval and canonical index lifecycle #130 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: [RELEASE] Ship and install 1.6.10-electric.3 - Parent: #130 ## Goal Ship electric/v1.6.10-electric.3, install it side-by-side with .2, select it through the common wrapper, and prove Codex plus Claude runtime behavior. ## Non-goals No npm, container, customer,
Product fit: Product/market issue; check vision fit, customer value, and whether external precedent can reduce time-to-market.
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.

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.
• Current market/product examples, capped and cited, only when they change implementation direction.

Acceptance criteria:

• Add explicit acceptance criteria before implementation is considered done.
• 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.

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.
• Technical severity alone can miss product/UX regressions; include product-manager review framing.

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.
• [enabled] current_market_examples: Use for product/UX/market positioning issues with freshness dates.
• [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]

Release-soak blocker found and contained

The isolated 85,345-node Voyage soak failed safely before staged promotion. GitNexus main sent OpenAI's dimensions field to Voyage; a sanitized direct probe with the same Keychain credential succeeded at 2,048 dimensions using Voyage's required output_dimension field.

• Issue: [P0] Restore Voyage 2,048-dimensional request compatibility #141
• Fix PR: fix(embeddings): restore Voyage 2,048d requests #142, exact head 3b9f5345a0bedc812a6cdb9061e60ea2701ce74f
• Focused TDD: two Voyage path tests failed before the patch; 57/57 HTTP-embedding tests pass after it, including a lookalike-host guard.
• Live fleet registry/config/index state remains untouched.
• The resumed 85k run is now progressing through Voyage one repository at a time. Resource telemetry is observation only; no memory/swap/RSS admission or termination gate exists.

This PR is now a release dependency for #137. The 125k canary will not start until the 85k process exits and validates.

[100yenadmin]

Release gate update: #143 / PR #144 is now an explicit .3 dependency. The first controlled 85k resume recognized its 5,000-node checkpoint but then misclassified it as pre-versioning because schema identity was tied to Git history. The focused regression now proves schema v6 on both final non-Git metadata and interrupted embedding-checkpoint metadata. A fresh sequential 85k canary is running on the combined PR #142 + PR #144 integration; no release claim is made until that resume and the remaining soak gates pass.