R23: Prepare sanitized upstream contribution sequence

[100yenadmin]

Open upstream work only after corresponding fork proof. Order: File-node fallback, preservation design, eval auth, token budget, aliases, read-only policy, repository policy, then generic pacing. Each upstream branch starts from current upstream and contains neutral fixtures.

Acceptance: no Electric Sheep names, premium defaults, credentials, customer data, private URLs, or repository policy; duplicate search is recorded and every upstream artifact links back to its fork issue.

Parent epic: #39

Tracking ID: R23

[100yenadmin]

R23 checkpoint (2026-07-13): four sanitized upstream artifacts are now open from current upstream c6445096.

• File-node embedding fallback: upstream issue #2454, PR #2455, fork proof #45 / #66.
• Interrupted-analysis preservation design: upstream issue #2456, fork proof #49 / #72.
• Eval-server non-loopback authentication: upstream issue #2457, PR #2458, fork proof #52 / #75.
• Deterministic MCP output budgets: upstream issue #2459, PR #2460, fork proof #51 / #74.

Each code branch starts at upstream c6445096, uses neutral tests and configuration names, and excludes fork-specific paths, credentials, private policy, and provider defaults. Next exact action: prepare alias normalization from the same verified upstream head, then read-only policy, repository policy, and generic pacing.

[100yenadmin]

Checkpoint update: the HTTP resilience review found and fixed a P0 resume-integrity gap before promotion.

A process stop after only some chunks of a multi-chunk node were inserted could leave a current node hash on a partial row. Hash-only resume then skipped the node and silently retained missing chunks.

Internal follow-up f32f14ecd3c7ab151efb5a88510ba332c3381af0 on PR #78 now:

• writes a bounded pending-node window before mutation;
• checkpoints LadybugDB before clearing it;
• forces matching-hash pending nodes through delete plus complete regeneration;
• deletes rows for pending nodes that are no longer embeddable;
• applies the contract to CLI analysis and /api/embed;
• retains the repository lock until cancelled work actually stops; and
• rejects model/dimension mismatch before mutation.

Focused proof on the RC19 stack: build pass, typecheck pass, formatting pass, git diff --check pass, and 183/183 focused tests pass. Remote CI on the new head is the remaining cross-platform gate.

Sanitized upstream artifacts: abhigyanpatwari#2467 and abhigyanpatwari#2468.

Evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-13/gitnexus-fork-upstream-reconciliation/r16-partial-window-resume-evidence.md

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #62 - R23: Prepare sanitized upstream contribution sequence
State: open; milestone: GitNexus v1.6.10 Reconciliation - Sprint 4 - Stable Rebase and Governance

Related issues/PRs: #39.
Existing labels: reconciliation, P1, evidence-gate, upstream-candidate.
Suggested labels: security, tests, support.
Suggested owners: none.

Related context

• EPIC: Reconcile evaOS GitNexus on the v1.6.10 RC lineage #39 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: R23: Prepare sanitized upstream contribution sequence - Open upstream work only after corresponding fork proof. Order: File-node fallback, preservation design, eval auth, token budget, aliases, read-only policy, repository policy, then generic pacing. Each upstream branch
Product fit: Product/UX-sensitive issue; review against repo vision and user flow quality, not only technical P0/P1 risk.
Implementation wedge: Ship the smallest user-visible path or prototype that can be smoke-tested against the intended experience.

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:

• 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.
• UX/product smoke or screenshot proof when implementation changes user flow.

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]

R23 complete. The sanitized, current-upstream contribution sequence is open and independently linked to fork proof:

• File-node fallback: upstream [Bug] Embeddings skip text-only repositories with no code symbols abhigyanpatwari/GitNexus#2454 / PR fix(embeddings): fall back to text-bearing file nodes abhigyanpatwari/GitNexus#2455
• Preservation design: upstream [Design] Add strict no-force analysis and a read-only recovery plan abhigyanpatwari/GitNexus#2456 (design-first; no premature PR)
• Eval auth: upstream security(eval): require authentication for non-loopback server binding abhigyanpatwari/GitNexus#2457 / PR feat(eval): require bearer auth for remote binding abhigyanpatwari/GitNexus#2458
• Output budgets: upstream feat(mcp): add deterministic response budgets abhigyanpatwari/GitNexus#2459 / PR feat(mcp): add deterministic response budgets abhigyanpatwari/GitNexus#2460
• MCP aliases: upstream feat(mcp): normalize impact and context parameter aliases abhigyanpatwari/GitNexus#2461 / PR feat(mcp): normalize impact and context parameter aliases abhigyanpatwari/GitNexus#2462
• Read-only policy: upstream feat(mcp): add fail-closed read-only mode abhigyanpatwari/GitNexus#2463 / PR feat(mcp): add fail-closed read-only mode abhigyanpatwari/GitNexus#2464
• Repository policy: existing upstream Mcp server (just serve one repo) abhigyanpatwari/GitNexus#1203 / PR feat(mcp): enforce repository allowlist and default abhigyanpatwari/GitNexus#2465
• Generic embedding resilience and durable resume: upstream Embedding HTTP resilience can silently skip partial multi-chunk nodes on resume abhigyanpatwari/GitNexus#2467 / PR fix(embeddings): make HTTP generation resumable abhigyanpatwari/GitNexus#2468

All code branches were prepared from verified upstream c6445096, use neutral fixtures and generic configuration, and exclude Electric Sheep names, premium/provider defaults, credentials, customer data, private URLs, and private repository policy. Duplicate search and sanitization evidence are retained under the program evidence directory. Upstream review or merge is contribution follow-through, not an internal release gate.

[100yenadmin]

R23 follow-through added two newly reduced, fork-proven contributions without reopening upstream acceptance as a gate:

• deterministic graph lookup collisions: upstream Scope graph lookup depends on insertion order when keys collide abhigyanpatwari/GitNexus#2479 / PR fix(scope): stabilize graph lookup collisions abhigyanpatwari/GitNexus#2480
• canonical repository scan order: upstream Repository traversal order can rewire Rust and PHP graph edges abhigyanpatwari/GitNexus#2481 / PR fix(scan): canonicalize traversal without order-sensitive bindings abhigyanpatwari/GitNexus#2482

Both start from unchanged upstream main at c6445096, use neutral fixtures, and contain no Electric Sheep/OpenClaw-specific policy or private data.