R03: Prove pristine upstream RC19 floor

[100yenadmin]

Prove the unmodified RC19 base before porting fork behavior. Run focused local build, typecheck, unit, and integration checks; use GitHub Actions for the broad cross-platform matrix. Smoke CLI, MCP, current Codex plugin discovery, analyze, query, context, impact, status, and doctor on disposable fixtures.

Acceptance: the base is green independently or every base failure is isolated and reported upstream without a masking fork patch.

Validation: npm run build, npx tsc --noEmit, npm run test:unit, focused integration tests, and exact remote-CI head.

Parent epic: #39

Tracking ID: R03

[100yenadmin]

Pristine RC19 validation is blocked without any fork patch.

Evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-13/gitnexus-fork-upstream-reconciliation/r03-pristine-floor.md

Results at exact base d43c479ac58c18d397958f48a99465d6c3110b1d:

• build: pass
• typecheck: pass
• unit: 479 files passed, 1 failed; 9,864 tests passed, 30 skipped, 2 failed
• both failures are plugin manifest version mismatches (1.6.9 vs 1.6.10-rc.19)

Upstream:

• RC19 unit suite fails because plugin manifests remain at 1.6.9 abhigyanpatwari/GitNexus#2445
• Contributor CLI install fails unless gitnexus-shared is installed first abhigyanpatwari/GitNexus#2446

Feature ports remain frozen. R04 and R05 may proceed because they are independent Sprint 0 evidence tasks; integration and broad smoke proof remain pending behind this pristine-floor disposition.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #42 - R03: Prove pristine upstream RC19 floor
State: open; milestone: GitNexus v1.6.10 Reconciliation - Sprint 0 - Immutable Baseline

Related issues/PRs: #39.
Existing labels: reconciliation, P0, evidence-gate, release-blocker.
Suggested labels: bug, docs, tests.
Suggested owners: none.

Related context

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

Agent-start packet

Problem shape: R03: Prove pristine upstream RC19 floor - Prove the unmodified RC19 base before porting fork behavior. Run focused local build, typecheck, unit, and integration checks; use GitHub Actions for the broad cross-platform matrix. Smoke CLI, MCP, current Codex plugin
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]

R03 resumed upstream rather than patched in the fork.

• GitNexus Contributor CLI install fails unless gitnexus-shared is installed first abhigyanpatwari/GitNexus#2446 now has draft upstream PR docs: document shared-first contributor setup abhigyanpatwari/GitNexus#2448 from current upstream main.
• Validation: Prettier and git diff --check pass; diff is one documentation hunk.
• GitNexus detect_changes was attempted but correctly refused because the registered live index belongs to another canonical clone; no live index was rebuilt or mutated.
• GitNexus RC19 unit suite fails because plugin manifests remain at 1.6.9 abhigyanpatwari/GitNexus#2445's exact release-workflow root cause and a tested four-manifest synchronization design are posted at RC19 unit suite fails because plugin manifests remain at 1.6.9 abhigyanpatwari/GitNexus#2445 (comment).
• That second fix awaits maintainer sign-off because it changes the sole publication workflow.

R03 remains open and feature ports remain frozen pending a corrected upstream candidate.

[100yenadmin]

R03 continuation update:

• Evidence-only draft PR test(ci): prove pristine v1.6.10-rc.19 floor #64 is running the RC19 application tree through the fork Ubuntu/Windows/macOS matrix. The validation base changes only the CI target-branch filter; the PR head adds only an inert four-line trigger marker.
• Disposable local smokes pass for doctor, analyze, query, context, impact, clean git status, MCP stdio initialize/tools-list/tools-call, and Codex marketplace discovery/install.
• Codex discovery succeeds but reports plugin version 1.6.9, independently retaining the RC19 unit suite fails because plugin manifests remain at 1.6.9 abhigyanpatwari/GitNexus#2445 metadata defect.
• Build/typecheck remain green; the two pristine manifest assertions remain the release-floor blocker.

No fork patch, main change, runtime action, or live-index mutation occurred. Next gate: finish #64 and obtain a corrected upstream candidate after abhigyanpatwari#2445.

[100yenadmin]

R03 remote disposition complete:

• test(ci): prove pristine v1.6.10-rc.19 floor #64 finished with 30 green checks. Its only primary failure is the two known RC19 unit suite fails because plugin manifests remain at 1.6.9 abhigyanpatwari/GitNexus#2445 manifest assertions; all Ubuntu/Windows/macOS platform, packaged-install, ABI, benchmark, build, lint, format, and typecheck jobs passed.
• New upstream issue CI: Windows platform shard 1/3 has only 3 seconds of watchdog headroom on RC19 abhigyanpatwari/GitNexus#2449 records the Windows 1/3 test step finishing in 14m57s against a 15-minute watchdog.
• New upstream issue CI: setup composites still pin deprecated Node 20 action runtime abhigyanpatwari/GitNexus#2450 and ready PR ci: update setup composites to setup-node v6 abhigyanpatwari/GitNexus#2451 repair the two stale setup composites still pinning the deprecated setup-node v4 runtime.
• Upstream docs PR docs: document shared-first contributor setup abhigyanpatwari/GitNexus#2448 is now ready for review.

R03 remains open only because the pristine release metadata contract still fails and a corrected candidate does not exist.

[100yenadmin]

External-gate checkpoint (2026-07-13):

• This is the third consecutive live refresh with the same external blockers.
• Stable GitNexus v1.6.10 is still absent; upstream main remains c6445096.
• GitNexus RC19 unit suite fails because plugin manifests remain at 1.6.9 abhigyanpatwari/GitNexus#2445 has no maintainer approval or corrected candidate.
• GitNexus PRs docs: document shared-first contributor setup abhigyanpatwari/GitNexus#2448 and ci: update setup composites to setup-node v6 abhigyanpatwari/GitNexus#2451 remain ready/mergeable with no reviews; their Vercel authorization failure requires the upstream team.
• LadybugDB PRs [SM-17] Replace lookupFuzzy in named-binding-processor.ts abhigyanpatwari/GitNexus#682 and [SM-19] Delete resolveCallTarget — replace with thin dispatcher abhigyanpatwari/GitNexus#684 remain ready/mergeable with six ordinary checks green and no reviews.
• No released Ladybug artifact contains [SM-17] Replace lookupFuzzy in named-binding-processor.ts abhigyanpatwari/GitNexus#682, so the release-artifact acceptance test cannot run.
• All safe work owned by the fork program is complete. R06+ remains frozen because starting it would violate the explicit Sprint 0 evidence gate.
• Original fork history, commit 7171cf3d, the three dirty files, tags, workflows, packages, releases, runtime, and live indexes remain untouched.

Resume on the first material external-state change: stable v1.6.10, approval or a corrected GitNexus candidate, a released Ladybug artifact containing abhigyanpatwari#682, or actionable review feedback on an open upstream PR. Rehydrate all current-head state before acting.

[100yenadmin]

Gate correction (2026-07-13):

• Upstream issues and pull requests are contribution and coordination artifacts only.
• Upstream review, merge, authorization, and publication are not prerequisites for internal fork implementation or disposable testing.
• Internal fork CI and source-built dependency artifacts are authoritative for R06-R19.
• The known RC19 manifest mismatch remains visible and receives a genuine fork release-workflow repair; it is not masked by weakened assertions.
• Stable upstream v1.6.10 gates only R20 stable rebase, R21 stable validation, and R24 promotion readiness.
• The previous external-gate blocked checkpoint is superseded. Continue with R03/R04 disposition and R06.