Correction: Pivot To Configuration Research

User correction: the current Pi team should focus on configuration research, not D3-TUI repo triage.

Stop any D3-TUI implementation or repo-first task selection. Preserve any repo-triage notes already written, but do not continue that track unless it directly supports a configuration research question.

Read now:

1. /workcell/llm-wiki/wiki/research/README.md
2. /workcell/llm-wiki/wiki/research/research-queue.md
3. /workcell/llm-wiki/wiki/research/answer-template.md
4. /workcell/llm-wiki/wiki/research/source-map.md
5. /workcell/llm-wiki/wiki/tasks/claim-board.md

New objective:

• Deepen and clarify the best setup for the Pi workcell based on the planning session.
• Answer the open architecture questions: pi-teams, LangGraph, CrewAI, AutoGen/Microsoft Agent Framework, Pydantic AI, LlamaIndex/RAG, Docker, pi-container-sandbox, Forgejo workflow, KOS/toolchain, Bun/Pi install shape, validation/smoke testing, remote UI, and external-agent coordination.
• Claim one open research question at a time.
• Write answers to the listed answers/q-*.md path.
• Update research-queue.md status and release the claim.

Team adjustment:

• lead: coordinate question selection and final synthesis.
• researcher: source/framework research and citations.
• builder-reviewer: operational fit, failure modes, validation needs, and implementation risk.

No source implementation during this pass. Repo inspection is allowed only as evidence for a configuration question.