Rewrite eval_system.md as user guide; preserve original spec as eval_system_design.md ...

- docs/eval_system.md: replaced stale spec with current user guide
  covering UI tabs, CLI, rubric, experts, versioning, API
- docs/eval_system_design.md: preserved original design spec for
  reference

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Add eval system Phase 5 — debug UI ...

Self-contained SPA at /debug/eval (route already wired in 8e0eed6).
Single index.html in the existing debug/ style — vanilla JS, embedded
CSS, no framework, no build step. Four tabs:

- Sessions — filterable table (profile / status / limit), eval status
  pill, headline avg scores, click-through to detail
- Detail — session metadata + every stored eval run, axes laid out as
  axis × expert grids with inline averages, expert comments, button to
  re-evaluate this single session
- Stats — weekly per-axis means table, optional complexity-bucket split
- Run — form to trigger any scope (unevaluated / single / all), live
  status panel polling /eval/run/{id} every 2.5s, run history with
  click-to-attach

Hash routing: #detail/<session_id> deep-links to a session.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

changed llm

Add eval system Phase 4 — read endpoints and background runner ...

REST surface for the debug UI:
- GET /eval/sessions  — overview list with eval status / latest avg /
  feedback counts (single SQL: sessions ⨝ feedback ⨝ latest run)
- GET /eval/sessions/{id} — session detail with all evaluations
- GET /eval/stats — weekly per-axis means; optional complexity-bucket split
- POST /eval/run — fire-and-forget background eval, returns run_id
- GET /eval/run/{id}, GET /eval/runs — poll progress and history

Pulled the runner loop out of cli into runner.py so both the CLI and
the REST endpoint share the same loop. State for in-flight runs lives
in an in-memory registry (single-process, cleared on restart).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Add eval system Phase 3 — judge runner end to end ...

Fills in the stubs from Phase 2:
- judge.render_session: full transcript with tool_call/tool_result folding,
  reactions inlined per assistant block, planning_logs appendix, no
  compression-summary substitution
- judge.run_expert: real LLM call, fence-tolerant JSON parse, single retry
  with corrective nudge on schema or parse error
- judge.evaluate_session: asyncio.gather across the three experts
- db.EvalDB: insert_evaluation_run (txn), list_evaluations,
  evaluated_session_ids, feedback_by_index helper
- cli `run` (filters: --session, --since, --limit, --re-evaluate-all,
  --dry-run, --model, --backend) and `show` (groups by eval_run_id, prints
  per-expert axes plus averaged scores)

Verified end-to-end against a real 10-message secretary session:
all three experts returned valid JSON first try; spread between strict
critic and the others surfaced as expected.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Add eval system Phase 2 — rubric, expert prompts, judge skeleton ...

Drafts the v1 rubric (7 axes, anchors at 10/30/50/75/100, open scale),
three independent expert prompts (strict_critic / pragmatist / tech_lead)
that all return the same JSON shape, and the orchestration scaffolding:
schema.py (pydantic models), judge.py (rubric loader, score averaging,
fence-tolerant JSON parser, new_run_metadata), cli.py with argparse for
run / show / stats. Real LLM calls and transcript rendering land in
Phase 3 — the stubs raise NotImplementedError.

`python -m debug.eval` works as the entry point. Anchor `examples` are
left empty for now; user fills them with real session_ids later without
bumping rubric_version.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Add eval system Phase 1 — message feedback signal ...

Spec at docs/eval_system.md describes the full LLM-as-judge plan;
this commit lands only the in-app feedback layer:
- debug/eval/ Python package with EvalDB (asyncpg) and FastAPI router
  exposing /eval/feedback (set / clear / list)
- message_feedback postgres table keyed by (session_id, message_index)
- thumbs up / down on each completed assistant block in the webclient,
  optimistic update with rollback on failure

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

changed llm & new ollama param

changed model

Strengthen todo progress discipline

Add structured planning review and adaptive depth

Tune reflect autonomy guidance

Improve compression and memory prompts

Remove tool-call-like examples from prompts

Improve prompt resilience and project context use

Fix profile prompt inconsistencies

Tune profile sampling configs

?

temp -

Add Android client documentation ...

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Open external links in browser on Android; add NaviAndroid UA token ...

- shouldOverrideUrlLoading: external URLs open via Intent, Navi server stays in WebView
- User-Agent gets "NaviAndroid/1.0" suffix for platform detection
- webclient/composables/usePlatform.js: exports isAndroid for future Android-specific behavior

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Collapse thinking and plan cards by default ...

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Replace LaTeX math symbols with Unicode before markdown rendering ...

Handles arrows, comparison operators, logic symbols and common math notation
that LLMs produce but marked.js doesn't render.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

filesystem mkdir: parents=False to prevent accidental path chain creation ...

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Add mkdir action to filesystem tool (parents=True, exist_ok=True) ...

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Fix websocket.py: unpack 4-tuple from get_registries(), pass cp_registry to Agent ...

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Add context providers: dynamic system message injection per LLM call ...

- navi/context_providers/ registry + built-in public_url provider (global, always injected)
- context_providers/ user directory, hot-reloaded via reload_tools
- AgentProfile.context_providers field for per-profile opt-in providers
- Agent._collect_context_injections() called before every tool-calling loop
- reload_tools now reloads both user tools and user context providers
- manuals/write_context_provider.md for Navi, docs/context_providers.md reference

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Set temperature=1.0, top_k=64, top_p=0.95 for all profiles (Google recommended for gemma4) ...

Also fixes discuss profile memory tools: use combined "memory" tool name, not nonexistent split variants.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Fix discuss profile planning: phase1 on (DIRECT gate), phase3 off ...

Model can skip planning via DIRECT; if it doesn't, analysis runs silently
without producing a plan card in the UI.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Add discuss profile; responsive WelcomeScreen for 6+ profiles ...

- New 'discuss' profile: creative Q&A and idea discussion, temp=1.0,
  planning phase 3 only, tools: web_search/view, scratchpad, reflect,
  memory, image_view, todo
- WelcomeScreen mobile: 2-column grid for profile cards, compact logo
  (row layout with subtitle on second line), reduced padding/gaps

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>