[P0] Repair HNSW without rebuilding embeddings and report zero embeddings truthfully

[100yenadmin]

Parent: #130

Goal

Add a fail-closed analyze --repair-vector maintenance mode that preserves every CodeEmbedding row, rebuilds only HNSW, validates vector search through the live eight-connection pool, then reconciles database-derived metadata and registry counts.

Required behavior

• Refuse unsafe storage, locks, recovery state, dirty metadata, conflicting flags, or missing VECTOR support before mutation.
• Preserve all embedding rows and exact identities.
• Return not-indexed without mutation when the database contains zero embeddings.
• Make registry doctor report zero embeddings as not-indexed rather than a broken vector index.
• Validate missing, healthy, unqueryable, zero-embedding, extension-unavailable, recovery-state, and failed-rebuild paths.

Acceptance

OpenClaw repair completes on the installed release; embedding rows and counts are unchanged; two semantic MCP queries return vector-index with partial=false.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #170 - [P0] Repair HNSW without rebuilding embeddings and report zero embeddings truthfully
State: open; milestone: GitNexus Repository Health & Large-Repo Reliability Sprint

Related issues/PRs: #130.
Existing labels: P0, evidence-gate.
Suggested labels: bug, docs, support.
Suggested owners: none.

Related context

• EPIC: Restore truthful semantic retrieval and canonical index lifecycle #130 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: [P0] Repair HNSW without rebuilding embeddings and report zero embeddings truthfully - Parent: #130 ## Goal Add a fail-closed analyze --repair-vector maintenance mode that preserves every CodeEmbedding row, rebuilds only HNSW, validates vector search through the live eight-connection pool, then reconciles
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.