feat: Render Markdown in chat and query output using rich

[KylinMountain]

Summary

• Use rich.live.Live + rich.markdown.Markdown to progressively render LLM responses with proper terminal formatting (headings, bold, code blocks, lists, etc.)
• Applied to both openkb chat (interactive REPL) and openkb query (single-shot)
• Falls back to plain text when --no-color is set (chat) or stdout is not a tty (query)
• Add rich>=13.0 as an explicit dependency

Test plan

• python -m pytest tests/ — 197 passed
• openkb chat — verify headings, bold, code blocks render with formatting
• openkb chat --no-color — verify plain text fallback
• openkb query "question" — verify formatted output
• openkb query "question" > file.txt — verify no ANSI codes in file

[KylinMountain]

[KylinMountain]

Code review

Found 1 issue:

1. In query.py, after live.stop() writes the tool call line to stdout, live.start() re-activates the auto-refresh thread (4 Hz by default). On the next refresh cycle, Live uses position_cursor() — which emits ANSI CURSOR_UP sequences based on the previous render height — to move back up into the already-printed area and overwrite it with the last Markdown renderable. This means the tool call text printed between live.stop() and live.start() will be overwritten/erased by the next Live refresh. The fix is to not re-start Live after a tool call (keep it stopped until more text arrives, then start a fresh Live), or to use live.console.print(tool_call_text) before stopping so it is incorporated into the live area.

OpenKB/openkb/agent/query.py

Lines 153 to 160 in 5d2b4b4

	args = getattr(raw, "arguments", "{}")
	if live:
	live.stop()
	sys.stdout.write(f"\n[tool call] {raw.name}({args})\n\n")
	sys.stdout.flush()
	if live:
	live.start()
	elif item.type == "tool_call_output_item":

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}

[KylinMountain]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}