Reconcile legacy workspace-docs source paths without deleting embeddings

[100yenadmin]

TL;DR\n\nOn legacy installs, workspace-docs may remain registered with the old workspace-root local_path even though the current updater correctly resolves and imports the agents.defaults.workspace/docs directory. This makes future sync --all semantics and doctor freshness misleading. Reconcile the path without deleting or re-embedding the user's source.\n\n## Reproduction\n\nLocal configured workspace: /Users/lume/.openclaw/workspace-eva.\nResolved docs directory: /Users/lume/.openclaw/workspace-eva/docs.\nRegistered workspace-docs local_path: legacy workspace root.\nThe exact-tag updater imports the docs directory, searches pass, and embeddings remain 100%, but the source record retains the older root.\n\n## Safety boundary\n\nDo not repair this by sources remove plus re-add: that deletes source-scoped pages and may trigger costly re-embedding. Prefer a provider-neutral, guarded source-path update seam or an idempotent migration that verifies source identity and path overlap first.\n\n## Acceptance\n\n- Fresh installs still register the docs subdirectory.\n- Legacy installs update the registered path without deleting pages, chunks, or embeddings.\n- Path overlap and missing-path guards fail closed.\n- Updater and health tests cover the migration.\n- Existing customer databases are not rebuilt.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #211 - Reconcile legacy workspace-docs source paths without deleting embeddings
State: open

Related issues/PRs: none detected from issue metadata.
Existing labels: none.
Suggested labels: docs, tests, support.
Suggested owners: none.

Related context

• No same-repo issue/PR references detected in issue metadata.

Agent-start packet

Problem shape: Reconcile legacy workspace-docs source paths without deleting embeddings - ## TL;DR\n\nOn legacy installs, workspace-docs may remain registered with the old workspace-root local_path even though the current updater correctly resolves and imports the agents.defaults.workspace/docs directory.
Product fit: Product/market issue; check vision fit, customer value, and whether external precedent can reduce time-to-market.
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: run capped external OSS/library/API/current-market research with citations, observed dates, and why each source matters.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.
• Allowlisted cross-repo GitHub examples with direct issue/PR/repo URLs.
• External OSS repositories or library/API docs with freshness dates.
• Current market/product examples, capped and cited, only when they change implementation direction.

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.
• External research must stay capped, cited, fresh-dated, and redacted.
• Technical severity alone can miss product/UX regressions; include product-manager review framing.

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: No explicit same-repo references detected; still safe as bounded local context.
• [enabled] allowlisted_cross_repo_github: Triggered by issue class; keep to configured allowlist and source caps.
• [enabled] external_oss_examples: Use for build/borrow/buy precedent with citations and observed dates.
• [enabled] library_api_docs: Use when implementation may depend on a module, SDK, API, or framework choice.
• [enabled] current_market_examples: Use for product/UX/market positioning issues with freshness dates.
• [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.