chore(release): prepare 1.6.10-electric.1

[100yenadmin]

Summary

• set the CLI, lockfile, Claude/Codex plugin manifests, and both marketplace manifests to 1.6.10-electric.1
• add the fork changelog entry and versioned GitHub Release notes
• prepare the first long-term Electric GitHub-only artifact release

Provenance

• reconciled source promotion: chore(reconciliation): promote proven RC19 internal source candidate #98
• release governance: Release: replace upstream publishers with protected Electric GitHub Releases #109 / ci: add protected Electric GitHub release flow #110
• RC19 peeled source floor: d43c479ac58c18d397958f48a99465d6c3110b1d
• current fork main base: b3b94040808b1f11f5628803ecacb54d79d8239c
• this release remains explicitly RC19-based and does not claim upstream stable v1.6.10 ancestry

Validation

• release policy suite: 24/24
• plugin and marketplace version sync: 3/3
• npm run build
• npx tsc --noEmit
• npm pack dry-run and real pack
• isolated tarball install reports 1.6.10-electric.1
• packaged CLI --help and mcp --help
• local tarball SHA-256 verification
• git diff --check

Remote CI on this exact PR head is the canonical broad validation gate.

Release boundary

This PR only promotes source and version metadata. It does not create a tag or release and does not publish npm packages or containers. It does not change OpenClaw runtime state, live GitNexus indexes, or embeddings.

After merge, the protected Electric Release workflow will independently rebuild, install, checksum, and require internal-release approval before creating electric/v1.6.10-electric.1.

Relates #111

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0e3c724f-dea8-4f12-ad67-9462d3c8883e

📥 Commits

Reviewing files that changed from the base of the PR and between b3b9404 and ec9f408.

⛔ Files ignored due to path filters (1)

• gitnexus/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (7)

• .agents/plugins/marketplace.json
• .claude-plugin/marketplace.json
• Documentation/releases/1.6.10-electric.1.md
• gitnexus-claude-plugin/.claude-plugin/plugin.json
• gitnexus-claude-plugin/.codex-plugin/plugin.json
• gitnexus/CHANGELOG.md
• gitnexus/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/1.6.10-electric.1

---

_{Comment @coderabbitai help to get the list of available commands.}

[evaos-code-review-bot]

evaOS review status: completed

PR: #112 - chore(release): prepare 1.6.10-electric.1
Head: ec9f408f3237f4e464fee62e305877975ab5c1a4
Updated: 2026-07-14T12:00:48.184Z

evaOS review completed for this PR head.

Automation note: agents should wait for this comment to reach completed, stale_head, closed_or_merged_before_review, skipped, or failed before treating evaOS review as settled for this head. provider_deferred means evaOS still intends to retry.

PR URL: #112

Review URL: #112 (review)

[evaos-code-review-bot]

Walkthrough

PR: #112 - chore(release): prepare 1.6.10-electric.1
Head: ec9f408f3237f4e464fee62e305877975ab5c1a4 into main. Review event: COMMENT.
Provider: GLM/Z.ai through ZCode (zcode-glm, zcode, model GLM-5.2).

Estimated review effort: 1/5 (~10 min)

Changed Files

File	Status	Churn	Purpose	Risk

Review Signal

No validated inline findings.
Dropped findings before posting: 1. High-severity findings: 0.

Risk Taxonomy

No finding categories.

Validation and Proof

1 required validation/proof recommendation(s) selected from changed files.

• required: TypeScript/web build or CI proof - Runtime TypeScript/web files or package/config files changed. Proof: npm run build; typecheck; focused Vitest; green GitHub check.
  Proof status: sufficient - PR metadata mentions acceptable proof for each required validation recommendation.
  Profile validation hints: Call out stale index, wrong repo identity, memory growth, and destructive analyze behavior.
  Profile proof expectations: Look for focused CLI, index, query, or migration proof.

Related Context

Related issues/PRs: #98, #109, #110, #111.
Suggested labels: none.
Suggested reviewers: none from current metadata.

Review Settings Preview

• Profile: assertive
• Enabled sections: Review summary (inline_review); Walkthrough (inline_review); Changed-files table (walkthrough); Effort estimate (walkthrough); Related issues/PRs (walkthrough); Suggested labels (suggestion_only); Review status comment (sticky_status)
• Path instructions: none
• Label suggestions: gitnexus, code-intelligence, backend
• Reviewer suggestions: none
• Suggestion behavior: suggestions only; labels and reviewers are not auto-applied.
• Roadmap-only settings: auto-apply labels; auto-request reviewers; required status checks

Pre-merge checklist

• Inline comments target current RIGHT-side diff lines.
• No secret-like content survived into posted inline comments.
• REQUEST_CHANGES is only used when eligible P0/P1 findings survive validation.
• Required behavior proof is present or not applicable.
• Labels and reviewers are suggestions only; the bot did not auto-apply them.

[github-actions]

CI Report

✅ All checks passed

Pipeline Status

Stage	Status	Details
✅ Typecheck	success	tsc --noEmit
✅ Tests	success	unit tests, 3 platforms
✅ E2E	success	gitnexus-web changes only

Test Results

Tests	Passed	Failed	Skipped	Duration
14717	14655	0	62	20s

✅ All 14655 tests passed

62 test(s) skipped — expand for details

• COBOL pipeline benchmark > scales with file count
• PreToolUse augmentation filtering (integration) > CJS: emits the MCP-query hint on stdout, stderr silent by default, when a GitNexus MCP process owns the repo DB
• PreToolUse augmentation filtering (integration) > CJS: MCP-owner path emits the MCP query hint; stderr reason gated by GITNEXUS_DEBUG
• PreToolUse augmentation filtering (integration) > CJS: MCP-owner hint emits on stdout; stderr stays silent with GITNEXUS_DEBUG='0'
• PreToolUse augmentation filtering (integration) > CJS: MCP-owner hint emits on stdout; stderr stays silent with GITNEXUS_DEBUG='false'
• PreToolUse augmentation filtering (integration) > Plugin: emits the MCP-query hint on stdout, stderr silent by default, when a GitNexus MCP process owns the repo DB
• PreToolUse augmentation filtering (integration) > Plugin: MCP-owner path emits the MCP query hint; stderr reason gated by GITNEXUS_DEBUG
• PreToolUse augmentation filtering (integration) > Plugin: MCP-owner hint emits on stdout; stderr stays silent with GITNEXUS_DEBUG='0'
• PreToolUse augmentation filtering (integration) > Plugin: MCP-owner hint emits on stdout; stderr stays silent with GITNEXUS_DEBUG='false'
• MCP-owner hint throttle (PreToolUse hook silently skips when MCP server owns DB lock — defeats the purpose abhigyanpatwari/GitNexus#2396) > CJS: emits once, then throttles within the window (marker gates it)
• MCP-owner hint throttle (PreToolUse hook silently skips when MCP server owns DB lock — defeats the purpose abhigyanpatwari/GitNexus#2396) > Plugin: emits once, then throttles within the window (marker gates it)
• MCP hint pattern escaping (PreToolUse hook silently skips when MCP server owns DB lock — defeats the purpose abhigyanpatwari/GitNexus#2396) > CJS: quote+newline pattern stays JSON-safe in additionalContext
• MCP hint pattern escaping (PreToolUse hook silently skips when MCP server owns DB lock — defeats the purpose abhigyanpatwari/GitNexus#2396) > Plugin: quote+newline pattern stays JSON-safe in additionalContext
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: skips augment for real node_modules/gitnexus ps line (npx child)
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: npx parent command line is NOT treated as GitNexus server owner
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: skips augment for gitnexus serve child
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: ENOENT lsof → augment still runs (fail-open)
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: ETIMEDOUT lsof → augment skipped (fail-closed)
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: ETIMEDOUT lsof → emits hint on stdout, stderr silent by default
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: ETIMEDOUT lsof with wrapper disabled → identical fail-closed skip
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: bad wrapper (no -k support) is rejected by the self-test → still fail-closed
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: guard exit 124 (budget expiry) → fail-closed skip
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: guard signal-death (status null + signal, no error) → fail-closed skip
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: always-exit-0 stub guard is rejected → augment still runs and emits context
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: non-GitNexus ps line → augment runs
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: multiple PIDs — skip if any ps line is GitNexus MCP
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > CJS: ps ENOENT → augment runs (ignore that PID)
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: skips augment for real node_modules/gitnexus ps line (npx child)
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: npx parent command line is NOT treated as GitNexus server owner
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: skips augment for gitnexus serve child
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: ENOENT lsof → augment still runs (fail-open)
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: ETIMEDOUT lsof → augment skipped (fail-closed)
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: ETIMEDOUT lsof → emits hint on stdout, stderr silent by default
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: ETIMEDOUT lsof with wrapper disabled → identical fail-closed skip
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: bad wrapper (no -k support) is rejected by the self-test → still fail-closed
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: guard exit 124 (budget expiry) → fail-closed skip
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: guard signal-death (status null + signal, no error) → fail-closed skip
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: always-exit-0 stub guard is rejected → augment still runs and emits context
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: non-GitNexus ps line → augment runs
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: multiple PIDs — skip if any ps line is GitNexus MCP
• Ladybug DB owner guard — production-shaped ps + failure modes (fix: skip Claude augment hook when GitNexus server owns DB abhigyanpatwari/GitNexus#1493) > Plugin: ps ENOENT → augment runs (ignore that PID)
• PHP pipeline benchmark > scales with file count (workers enabled)
• C++ capture identifier-type-lookup benchmark > capture emit scales sub-quadratically with co-scaled enums and call sites
• buildTypeEnv > known limitations (documented skip tests) > Ruby block parameter: users.each { |user| } — closure param inference, different feature
• Go pipeline benchmark > scales with file count (workers enabled)
• Go pipeline benchmark — worker pool (issue Worker idle timeout kills long Go scope extraction and surfaces as Napi::Error during analyze abhigyanpatwari/GitNexus#1848) > does not quarantine the large generated Go file on sub-batch idle timeout
• Go structural interface detection benchmark > scales linearly with interface × struct count
• Go structural interface detection split-phase benchmark > separates index-build and detection time
• antigravity hook adapter e2e > AfterTool — MCP-query hint when MCP server owns the DB (PreToolUse hook silently skips when MCP server owns DB lock — defeats the purpose abhigyanpatwari/GitNexus#2396) > emits the MCP-query hint on stdout, no stderr noise, exit 0 (CLI augment never ran)
• antigravity hook adapter e2e > AfterTool — MCP-query hint when MCP server owns the DB (PreToolUse hook silently skips when MCP server owns DB lock — defeats the purpose abhigyanpatwari/GitNexus#2396) > surfaces the skip reason on stderr only under GITNEXUS_DEBUG=1
• Spring inheritance scaling benchmark (Spring route extraction: ingestion does not resolve interface-inherited mappings (#2280) abhigyanpatwari/GitNexus#2288) > scales linearly with interface×controller pair count
• Spring inheritance pipeline benchmark — end-to-end (Spring route extraction: ingestion does not resolve interface-inherited mappings (#2280) abhigyanpatwari/GitNexus#2288) > full analyze scales linearly with interface→controller pair count
• C# pipeline benchmark > scales with file count — namespaces spread across the solution
• C# pipeline benchmark > scales with file count — all types in one (global) namespace bucket
• C# pipeline benchmark > scales with file count — all types in one (named) namespace bucket
• Ruby pipeline benchmark > scales with file count (workers enabled)
• C++ pipeline benchmark > scales with file count
• Rust pipeline benchmark > scales with file count (workers enabled)
• C++ ADL emit benchmark > emit phase scales sub-quadratically with co-scaled files and sites
• Vue pipeline benchmark > scales with component count
• getOsPageSize > returns undefined on Windows without forking
• run.cjs direct-exec entrypoint (fix(cli): steer docs, skills, and hooks through a CLI-neutral project-local runner (#1939) abhigyanpatwari/GitNexus#1945) > resolves a .cmd shim via the Windows shell branch, passing args and exit code

Code Coverage

Tests

Metric	Coverage	Covered	Base	Delta	Status
Statements	80.9%	54755/67679	N/A%	—	🟢 ████████████████░░░░
Branches	68%	33642/49467	N/A%	—	🟢 █████████████░░░░░░░
Functions	87.08%	6368/7312	N/A%	—	🟢 █████████████████░░░
Lines	84.41%	48854/57872	N/A%	—	🟢 ████████████████░░░░

---

_{📋 View full run · Generated by CI}

[100yenadmin]

Release-owner approval is recorded for this operation. Exact head ec9f408f3237f4e464fee62e305877975ab5c1a4 has 45 successful checks, zero failures or pending jobs, no unresolved review threads, and an exact-head evaOS review with no validated findings. The repository currently has no second authenticated maintainer who can satisfy the independent last-push approval rule, so this merge will use the administrator path without changing or disabling branch protection. The protected internal-release environment remains a separate approval gate before any tag or GitHub Release mutation.

[100yenadmin]

Correction to the prior operational note: GitHub enforces the independent-approval rule even for the administrator merge path, so --admin was rejected. With the repository owner approval and all exact-head checks settled, the merge will use a time-bounded exception to the review-count setting only. Required status checks, strict current-head enforcement, admin enforcement, and every other branch protection remain enabled. The exact one-approval plus last-push-approval setting will be restored immediately after the merge and verified.