AI Target: Deprecate Legacy DOC_GAP Inference in DreamService

Architectural Paradox

The DreamService REM pipeline historically used jsdocx output (structure.json / all.json) to score [DOC_GAP] penalties against Graph Nodes.

However, we identified a critical structural flaw during the evaluation of Swarm Intelligence heuristics:

• jsdocx is fundamentally a human-centric format that inherently omits undocumented codebase entities. Consequently, attempting to map missing entities by joining against it creates a paradox (verifying an Abstract Syntax entity against a manifest that dropped it).
• Negative ROI: Agentic SLMs and LLMs natively parse source code AST. Training the Swarm to focus processing power on closing JSDoc syntax gaps generates unhelpful noise that obscures high-value test ([TEST_GAP]) and systemic component ([TOPOLOGY_GAP]) priorities.

Resolution

Instead of patching the deterministic verification loop on a flawed documentation JSON file, we have evaluated and executed a hard pivot:

1. Deprecated Logic: Eradicated the legacy [DOC_GAP] routine from DreamService.mjs and related capability inference.
2. Shifted Weighting: Re-centered the processing capacity strictly toward code maturity ([TEST_GAP]) and strategic architectural context ([GUIDE_GAP]).
3. Paving the Way: This resolves the operational noise blocking the future [TOPOLOGY_GAP] Swarm architectural mapping.

Handoff Context

Pull Request #9996 handles the removal and unit test rectifications.