decouple: remove /api/wiki-enrich + wiki_index read path (migrated to navi-places)

PR-B of decouple #4-READ. navi-places now reads its own wiki_index.db directly
(navi-backend a8f9520, deployed + verified: Horseshoe Falls enrichment served
from /var/lib/navi-backend/wiki_index.db; admin-info dropped the recon-wiki-enrich
dependency). recon's endpoint is edge-unreachable-unused, safe to remove.

- DELETE lib/wiki_enrich_api.py (the /api/wiki-enrich blueprint).
- DELETE lib/place_detail.py (97-line survivor: lookup_wiki_index +
  _get_wiki_index_db) — its only consumer was wiki_enrich_api.py (verified zero
  non-test code consumers). Fully orphaned.
- DELETE lib/wiki_enrich_api_test.py (tests the deleted endpoint).
- api.py: drop the wiki_enrich_bp import + register_blueprint.

Untouched (separate decouple): /api/wiki-rewrite (wiki_rewrite_api.py +
wiki_rewrite.py), still navi-consumed. /opt/recon/data/wiki_index.db left in
place (data; now a harmless dead file). Internal localhost migration — no nginx.

Flag (doc follow-up, not fixed): deployment_config.py:10 + wiki_rewrite_api.py:6
both have stale in-prose references to the deleted place_detail.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

lib/api.py

@@ -62,10 +62,6 @@ app.request_class = _LargeZimRequest
 from .netsyms_api import netsyms_bp
 app.register_blueprint(netsyms_bp)
 
-# ── Wiki-enrich Blueprint (extraction #5 prep — HTTP wrapper over wiki_index) ──
-from .wiki_enrich_api import wiki_enrich_bp
-app.register_blueprint(wiki_enrich_bp)
-
 # ── Wiki-rewrite Blueprint (extraction #5 prep — HTTP wrapper over rewrite_wiki_link) ──
 from .wiki_rewrite_api import wiki_rewrite_bp
 app.register_blueprint(wiki_rewrite_bp)