Separate install callability from doctor content maturity

[100yenadmin]

TL;DR

eva-v0.42.63.2 installs and is callable through CLI, Codex MCP, and an OpenClaw agent, but scripts/update-local-install.sh exits nonzero because it treats every upstream doctor content-maturity failure as an install/runtime failure. On the local canary, source-scoped searches, Voyage 2048, the OpenClaw plugin, Codex MCP, gateway inference, and a real gbrain_query agent call all passed; doctor still failed on never-run dream cycles, stale sync bookkeeping for an import-managed docs source, and non-actionable type proliferation.

The updater should gate on runtime callability and report doctor content readiness separately. It must not run costly or destructive content mutation just to make an install score green.

Reproduction

1. Install exact tag with Support KB and workspace docs.
2. Both sources import/embed and source-scoped searches pass.
3. gbrain doctor --scope=brain --json exits 1 for:
   • cycle_freshness (no full dream cycle)
   • sync_freshness (workspace docs are import-managed)
   • type_proliferation even though gbrain onboard --check --explain --json returns zero recommendations
4. The updater aborts before its source-aware health report.

Expected

• Provider probe, CLI availability, DB open, source presence/search, plugin load, and explicit adapter callability remain release gates.
• Doctor JSON is always recorded.
• Content, taxonomy, and cycle maturity is reported without making a working install fail.
• type_proliferation is non-blocking when no built-in successor/remediation exists, restoring the behavior previously shipped for Doctor type_proliferation blocks 100/100 when onboard reports no action #192.
• Removed upstream freshness subcommands are not invoked as if they still exist.

Acceptance criteria

• Regression tests cover a doctor exit 1 with successful source searches and plugin inspection.
• Runtime or search failure still fails health.
• Type proliferation with no successor is actionable metadata, not a false blocking command.
• Full GitHub CI is green.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #208 - Separate install callability from doctor content maturity
State: open

Related issues/PRs: #192.
Existing labels: none.
Suggested labels: bug, docs, tests, support.
Suggested owners: none.

Related context

• Doctor type_proliferation blocks 100/100 when onboard reports no action #192 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: Separate install callability from doctor content maturity - ## TL;DR eva-v0.42.63.2 installs and is callable through CLI, Codex MCP, and an OpenClaw agent, but scripts/update-local-install.sh exits nonzero because it treats every upstream doctor content-maturity failure as
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 now in PR #209 at head 4244d22ae92825b6a289ceb71d7e4208d16b75dd. Focused proof: 40 tests passed, including fail-closed coverage for runtime-critical doctor failures, malformed output, and parseable non-diagnostic error JSON. Independent final delta review reported no findings. Full GitHub CI/review is running.

[100yenadmin]

Released eva-v0.42.63.3 from merge 982a838 and completed the exact-tag local callability canary.\n\nProof:\n- GitHub Test, E2E, CodeQL, OSV, Semgrep, gitleaks, Socket, and CodeRabbit are green.\n- Release binaries and SHA256SUMS verified.\n- Local CLI reports 0.42.63.3; PGLite opens with 3,609 pages and schema 124.\n- Both openclaw-support-kb and workspace-docs searches return results.\n- Voyage provider probe returns 2,048 dimensions.\n- Codex installed-machine smoke passes.\n- OpenClaw plugin is loaded at 0.42.63.3.\n- Gateway inference passes on openai/gpt-5.4.\n- A real OpenClaw agent turn called gbrain_query exactly once with zero failures.\n- No stale gbrain serve process remains.\n\nRaw upstream doctor still marks optional content maturity as unhealthy: workspace-docs has an old sync receipt and both sources have never completed a full dream cycle. The Eva install health gate reruns source-scoped searches, sees zero runtime/schema/migration blockers, and classifies those as advisory-content-only. No database was rebuilt and no fleet VM was touched.\n\nFollow-ups: #210 tracks upstream 0.42.64.0; #211 tracks safe legacy workspace-docs path reconciliation.