Skip to content

Simplify homepage and add evidence, follow-ups, and live progress - #7

Merged
minhajuddin2510 merged 1 commit into
mainfrom
codex/simplify-homepage
Sep 15, 2026
Merged

minhajuddin2510 merged 1 commit into
mainfrom
codex/simplify-homepage

Conversation

@minhajuddin2510

Copy link
Copy Markdown
Collaborator

Summary

The homepage repeated navigation, trust panels, and suggested questions, while answers hid source dates and query progress advanced on a timer. This change keeps the initial page focused on one question and makes the answer workflow easier to understand and control.

  • Center the question box, show three starter prompts with an optional expansion, simplify navigation/footer, and start the sidebar minimized on every visit.
  • Add a compact sources and data dates disclosure with separate observation coverage, retrieval, source update, and human review dates. Missing legacy metadata stays explicitly unknown; saved answers retain their original provenance.
  • Add contextual follow-up actions for trends, comparisons, explanations, methods, and dataset discovery. Follow-ups preserve their topic and request new analysis instead of repeating the original cached answer.
  • Replace simulated stages with authenticated SSE progress from actual pipeline and tool operations, elapsed time, Stop, and retry controls. Disconnecting cancels and awaits the request worker; results stay attached to the originating conversation.

The existing JSON query endpoint and notebook workflow remain supported. Stream state is request-scoped and works without an instance-local job registry.

Validation

  • 124 focused Python tests passed, including provenance, authenticated route validation, concurrent stream isolation, ASGI disconnect cancellation, graph trace preservation, follow-up interpretation, verified matching, and notebook generation.
  • 15 Node tests passed for evidence escaping, unknown dates, contextual actions, query length limits, fragmented SSE, interrupted streams, and abort handling.
  • Ruff passed for changed Python files; mypy passed for the three new backend modules.
  • Browser smoke checks covered responsive layout, dark mode, sidebar defaults, notebook preview, evidence disclosure, and follow-up sign-in handling.

The roborev post-commit review could not run because its standalone Claude CLI authentication has expired.

@minhajuddin2510
minhajuddin2510 merged commit ba739b1 into main Sep 15, 2026
4 of 5 checks passed
jqnatividad added a commit that referenced this pull request Sep 16, 2026
tests/unit/test_query_stream.py::test_cancelled_stream_reader_cancels_worker
deadlocks on Python 3.11 only. gateway/query_stream.py::query_events cancels
its worker and then awaits it inside an anyio.CancelScope(shield=True) in the
finally block; on 3.11 that shielded await never completes when the consumer
task is cancelled, so the cancelled reader never finishes and the loop sits
idle with nothing runnable. Reproduced in a 3.11 venv; passes on 3.12 and 3.14.

Introduced by fa50bfb (#7) — every CI run since has hung, and with no
timeout-minutes on any job each one ran toward the 6-hour default.

3.14 stays in the matrix because the Dockerfile ships python:3.14-slim, so the
deployed interpreter was the one version CI never exercised.

This removes the interpreter that exposes the deadlock; it does not fix
query_events. Restoring 3.11 would meet it again.

Verified: 802 passed, 2 skipped on both 3.12 and 3.14; ruff clean under the new
py312 target; uv lock --check clean.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant