Electric.2: make MCP tool schemas provider-compatible

[100yenadmin]

Parent: #117

Generalize upstream PR abhigyanpatwari#2489 across the fork schema surface. Begin with failing tests. Remove top-level anyOf/oneOf/allOf from advertised tools while preserving names and properties. Enforce api_impact route/file and impact target/name/symbol requirements in runtime normalization before repository resolution.

Acceptance: invariant holds after policy wrappers and stdio/HTTP listing; canonical, agreeing, conflicting, missing, grouped, read-only, and allowlisted cases pass.

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

[100yenadmin]

Implementation is complete in temporary stacked commit 7a31566f while PR #122 finishes its last CI shard. This branch will be rebased onto merged origin/main before a PR is opened, so the capability diff remains independent.

Focused proof passed: 321 schema/dispatch/policy tests, 41 real Streamable HTTP transport tests, one real spawned stdio handshake, TypeScript typecheck, full build, Prettier, and diff check. Every advertised tool is free of root anyOf/oneOf/allOf; aliases and property names are preserved; missing/conflicting values fail before repository resolution; read-only and allowlist transformations retain the contract.

Evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-14/gitnexus-electric-2-sprint/evals/provider-schemas.md

Exact next action: merge #122 after its isolated transient retry is green, rebase this commit onto the resulting main, push the capability branch, and open the independent PR.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #119 - Electric.2: make MCP tool schemas provider-compatible
State: open; milestone: GitNexus Electric.2 Maintenance Sprint

Related issues/PRs: #117, abhigyanpatwari#2489.
Existing labels: P0, evidence-gate, upstream-candidate.
Suggested labels: tests.
Suggested owners: none.

Related context

• EPIC: GitNexus Electric.2 maintenance sprint #117 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• fix(mcp): avoid top-level api_impact schema combinators abhigyanpatwari/GitNexus#2489 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: Electric.2: make MCP tool schemas provider-compatible - Parent: #117 Generalize upstream PR abhigyanpatwari#2489 across the fork schema surface. Begin with failing tests. Remove top-level anyOf/oneOf/allOf from advertised tools while preserving names and properties. Enforce api_impact
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: 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.
• 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.

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]

Implementation is in PR #123 at exact head 2566bf6efeedf65bfca730c132f293edc4e5b270, independently based on merged main 3d347e737f1250a69d219389fd2f08fd69f0f41d. Focused schema, dispatch, policy, stdio, and Streamable HTTP proof is green; exact-head GitHub Actions and terminal review are running.

[100yenadmin]

CI found and we fixed a backward-compatibility gap before merge: UID-only impact selection was rejected by the new runtime guard. PR #123 is now at f5b349e6174540c53d43ac5bba4073d2c8abe14a; focused dispatch plus the real spawned CLI UID-only regression both pass. All review and CI gates reset to this new head.