task: consolidate existing MindIE adapters under Apps #452

Goal

Relocate the MindIE-specific adapter already in this repository entirely into src/inferrsi/apps/mindie/ (project.py, context.py, mcp.py, read_worker.py). This bounded migration does not take over the broader MindIE Agent integration and real-task qualification tracked by #374, and does not include an internal refactor of existing subpackages. Related: #371, #408 and #412.

PR checklist

• M1 — Consolidate the existing MindIE adapter in Apps and retire the four root paths. Candidate internal files are project.py, context.py, mcp.py and read_worker.py. Add worker_process.py only if the subprocess launch/limit handling is shared by more than one module inside apps/mindie; do not introduce a one-user abstraction. Keep provider-specific pure projection inside the adapter as pure functions. Keep read_worker.py a standalone file whose top-level imports are stdlib-only: it still runs under the approved MindIE interpreter and imports mindie_knowledge inside read(), so do not describe the worker as stdlib-only overall. It must not gain relative or package imports, and apps/mindie/__init__.py must stay import-free. Repoint mindie_mcp.py:7's from . import __version__ to from ... import __version__ (or an absolute import) when the module moves; do not re-export __version__ from apps/mindie/__init__.py.
• In that same PR update the canonical CLI, worker/package lookup, active consumers, docs and tests; delete root mindie_project.py, mindie_context.py, mindie_mcp.py and _mindie_read_worker.py, and shrink the C1 exact-root inventory guard by these four files in the same PR.

Dependencies and boundaries

Integrate after the canonical CLI migration A1 in #408. All MindIE-specific code, including the worker, stays in apps/mindie/: do not add MindIE-specific Harness, Knowledge or infra modules, and do not create an extensions/ package or scatter MindIE-specific files into the core modules. Apps calls its worker and records original bytes, digests and receipts through applicable existing generic factual-storage interfaces. Verify interface suitability during implementation; do not invent a MindIE-specific core service. Harness must not depend on MindIE or infra.

Acceptance

• Preserve grant storage and explicit opt-in; no implicit activation, counter changes or new MindIE capability.
• Preserve the external-worker -I -B boundary, private working directory, 20-second/2-MiB limits and read-only SQLite behavior, including negative tests; add a negative test proving the worker still runs from an installed wheel with -I -B and no package-relative imports.
• Preserve source bytes, digests, attribution and receipts. Pure projection has no I/O; do not silently substitute canonical JSON rules for the existing strict parser, and keep the existing strict-parser negative tests byte-for-byte.
• Verify installed-wheel worker lookup outside the checkout, stdio behavior and worker import/isolation side effects, including an installed-wheel import of apps.mindie.mcp; do not introduce eager core imports through package initializers. Keep the accepted OBS layout decision: the historical six-key/no-retrieval path for readers providing neither observation nor provenance, and the existing extended path otherwise.
• No new MindIE-specific code outside apps/mindie, no four-layer migration, no permanent old-root aliases, and no claims of broader task: 支持 MindIE Agent 对接（知识、执行与评测交接） #374 real-task qualification.

Delivery discipline

• One implementation Claude session handles only the current PR in an isolated worktree. A second Claude session may only plan the next PR in a separate planning worktree; it must not edit source.
• Move implementation, update all active consumers/docs/tests, and delete the corresponding old root modules in the same PR. Do not introduce permanent compatibility shells or module-registry aliases.
• Preserve CLI command behavior, original evidence bytes, record/format contracts and isolation/security checks. Announce retired Python import/serialization module paths; historical frozen evidence remains pinned to its original commit or wheel, not rewritten.
• Before each implementation or review handoff, refresh main and confirmed dependencies. A completed plan is not implementation or approval. No automatic merge.