R13: Secure eval-server non-loopback binding

[100yenadmin]

Retain GITNEXUS_AUTH_TOKEN. Loopback may run without a token; non-loopback startup must refuse unless a token exists. Validate Authorization: Bearer, compare safely, return 401, and redact credentials from logs and errors.

Acceptance: no non-loopback unauthenticated start, health/tool routes follow the documented auth contract, wrong or missing tokens fail, and logs contain no token material.

Validation: subprocess bind/auth tests including IPv4 and IPv6 loopback classification.

Parent epic: #39

Tracking ID: R13

[100yenadmin]

Capability

Implements R13 by securing the standalone gitnexus eval-server HTTP surface.

• Retains GITNEXUS_AUTH_TOKEN.
• Allows tokenless startup only on IPv4/IPv6 loopback.
• Refuses non-loopback startup without a token before database initialization or socket binding.
• Applies exact Bearer authentication to health, tool, and shutdown routes.
• Uses constant-time comparison and generic 401 responses with WWW-Authenticate: Bearer.
• Keeps token material out of logs, diagnostics, banners, and response bodies.
• Updates localized CLI help and runtime examples to match the enforced policy.

This replaces, rather than cherry-picks, legacy fork commit 8a38fe83; the old patch did not fail closed on remote binds and had no tests.

Evidence

• Red phase retained: 12 of 13 new contract tests failed before implementation.
• Focused unit/help tests: 75 passed.
• Real subprocess bind/auth tests: 5 passed.
• TypeScript: passed.
• Targeted ESLint: zero errors; existing warnings only.
• Full package build: passed.
• Prettier and diff checks: passed.
• Detailed evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-13/gitnexus-fork-upstream-reconciliation/r13-secure-eval-server.md.

Stack And Gate

• Base: reconcile/r12-mcp-output-budgets.
• Head: 694526a591f899ad5c457f12450f4cb706a4ab8c.
• This PR must wait for R12, then be retargeted to the integration branch and revalidated at current head.
• Publication, runtime rollout, live-index mutation, and default-branch promotion are outside this PR.

Closes #52 after merge.
Parent epic: #39.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #52 - R13: Secure eval-server non-loopback binding
State: open; milestone: GitNexus v1.6.10 Reconciliation - Sprint 2 - Bounded and Secure Agent Interfaces

Related issues/PRs: #39.
Existing labels: reconciliation, P0, evidence-gate, upstream-candidate, release-blocker.
Suggested labels: bug, security, 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: R13: Secure eval-server non-loopback binding - Retain GITNEXUS_AUTH_TOKEN. Loopback may run without a token; non-loopback startup must refuse unless a token exists. Validate Authorization: Bearer, compare safely, return 401, and redact credentials from logs and
Product fit: Implementation issue; keep product fit lightweight unless VISION.md/repo policy raises a constraint.
Implementation wedge: Start with a focused fixture or dry-run path that proves the issue shape before widening 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.

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.