[OPS] Recover WorldOS and collapse duplicate registry entries safely

[100yenadmin]

Parent: #130

Goal

Recover WorldOS and collapse duplicate local GitNexus registrations without deleting source checkouts or losing unique work/index evidence.

Ordered work

1. Freeze analyzers/database owners and snapshot registry/config/wrapper/meta/WAL/counts.
2. Preserve unreachable indexed SHAs, dirty diffs, stash manifests, and both WorldOS index directories.
3. Recover/rebuild canonical WorldOS until registry/meta/database counts agree and real VECTOR works; never replay the unmatched WAL blindly.
4. Remove each duplicate with an exact absolute-path preview, require exactly one registry-row delta, and re-smoke the survivor.

Families: evaOS-GUI (8 duplicates), dashboard (1), NeonDiff (1), GitNexus (1 plus remote repair), evaOS ws-proxy (2), WorldOS owner-play (1 after recovery).

Acceptance and proof

No normalized-remote or case-insensitive alias duplicates; counts and sidecars agree; every surviving canonical graph/FTS/VECTOR smoke passes; source worktrees remain present; rollback archives are readable.

Evidence: /Volumes/LEXAR/Codex/session-notes/2026-07-20/gitnexus-repository-health-sprint/registry/.

Stop conditions

Stop on active handles, symlink/unsafe storage, unexpected WAL or nonzero duplicate embeddings, unpreserved local work, target-preview mismatch, or registry delta larger than one row.

Exact next action

Wait for the installed .3 diagnostics, then run the frozen preflight and archive WorldOS before any removal.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #134 - [OPS] Recover WorldOS and collapse duplicate registry entries safely
State: open; milestone: GitNexus Repository Health & Large-Repo Reliability Sprint

Related issues/PRs: #130.
Existing labels: P1, evidence-gate.
Suggested labels: none.
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: [OPS] Recover WorldOS and collapse duplicate registry entries safely - Parent: #130 ## Goal Recover WorldOS and collapse duplicate local GitNexus registrations without deleting source checkouts or losing unique work/index evidence. ## Ordered work 1. Freeze analyzers/database owners and
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

• No obvious issue triage gap detected from issue metadata.

No labels, owners, reviewers, or roadmap fields were changed by this bot.

[100yenadmin]

WorldOS recovery is terminal. Installed 1.6.10-electric.3 rebuilt and promoted the exact-main canonical index at /Users/lume/WorldOS. Registry, metadata, and database agree at 26,654 nodes, 51,026 edges, and 19,153 Voyage code-3 embeddings. Active graph, FTS, and vector-index probes passed, followed by two MCP semantic queries with partial=false. The registry changed by exactly one row: the owner-play duplicate was unregistered only. Its checkout, sentinel, index, and archive remain unchanged; the pre-.3 canonical generation remains at the dated rollback path. No analyzer or database owner remains. Evidence: registry/worldos-sidecar-lane.md (SHA-256 f83c6b8dd708a78f98df3b64a4a78eb13071218f3f950ec3a46fa700bc7482df).