Skip to content

Sprint 6I: chat thread selection and continuity review UI #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
samrusani merged 1 commit into from
Mar 17, 2026
Merged

Sprint 6I: chat thread selection and continuity review UI #29

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
288 changes: 86 additions & 202 deletions BUILD_REPORT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,216 +2,100 @@

## sprint objective

Implement Sprint 6H by exposing narrow user-scoped continuity APIs over the shipped continuity store:
Implement Sprint 6I by extending `/chat` with visible thread selection, compact thread creation, and bounded continuity review using only the shipped continuity APIs, while preserving the existing assistant-response and governed-request seams.

## exact `/chat` files and components updated

- `apps/web/app/chat/page.tsx`
- `apps/web/app/chat/page.test.tsx`
- `apps/web/app/globals.css`
- `apps/web/components/mode-toggle.tsx`
- `apps/web/components/request-composer.tsx`
- `apps/web/components/request-composer.test.tsx`
- `apps/web/components/response-composer.tsx`
- `apps/web/components/response-composer.test.tsx`
- `apps/web/components/thread-list.tsx`
- `apps/web/components/thread-list.test.tsx`
- `apps/web/components/thread-create.tsx`
- `apps/web/components/thread-create.test.tsx`
- `apps/web/components/thread-summary.tsx`
- `apps/web/components/thread-summary.test.tsx`
- `apps/web/components/thread-event-list.tsx`
- `apps/web/components/thread-event-list.test.tsx`
- `apps/web/lib/api.ts`
- `apps/web/lib/api.test.ts`
- `apps/web/lib/fixtures.ts`
- `BUILD_REPORT.md`

## continuity data mode

- live API-backed when the web API base URL and user ID are configured
- fixture-backed for thread selection, thread summary, continuity review, and history when API configuration is absent
- explicit unavailable state for thread creation when API configuration is absent

## shipped backend continuity endpoints consumed

- `POST /v0/threads`
- `GET /v0/threads`
- `GET /v0/threads/{thread_id}`
- `GET /v0/threads/{thread_id}/sessions`
- `GET /v0/threads/{thread_id}/events`

The work stays inside backend continuity scope and does not widen response generation, task orchestration, Gmail, or UI behavior.

## completed work

- added continuity response contracts and ordering metadata in `apps/api/src/alicebot_api/contracts.py`
- introduced `ThreadCreateInput`
- introduced `ThreadRecord`
- introduced `ThreadCreateResponse`
- introduced `ThreadListSummary`
- introduced `ThreadListResponse`
- introduced `ThreadDetailResponse`
- introduced `ThreadSessionRecord`
- introduced `ThreadSessionListSummary`
- introduced `ThreadSessionListResponse`
- introduced `ThreadEventRecord`
- introduced `ThreadEventListSummary`
- introduced `ThreadEventListResponse`
- introduced continuity ordering constants:
- `THREAD_LIST_ORDER`
- `THREAD_SESSION_LIST_ORDER`
- `THREAD_EVENT_LIST_ORDER`
- added deterministic thread listing support in `apps/api/src/alicebot_api/store.py` with `list_threads()`
- implemented the five scoped continuity endpoints in `apps/api/src/alicebot_api/main.py`
- kept continuity reads user-scoped by reusing the existing RLS-backed `ContinuityStore`
- added unit coverage for create/list/detail/session/event response shape, ordering, and invisible-thread handling
- added Postgres-backed integration coverage for create/list/detail/session/event behavior and cross-user isolation
- added a migration guard asserting the shipped thread created-time index remains present for deterministic continuity review queries

## exact ordering rules

- thread list order: `created_at DESC`, then `id DESC`
- thread session list order: `started_at ASC`, then `created_at ASC`, then `id ASC`
- thread event list order: `sequence_no ASC`

## incomplete work

- no in-scope code deliverables remain incomplete
- intentionally not added:
- thread rename
- thread archive
- session mutation APIs
- event mutation or deletion behavior
- thread search, pagination, or filtering
- `/chat` UI thread selection or thread creation UX

## files changed

- `ARCHITECTURE.md`
- `apps/api/src/alicebot_api/contracts.py`
- `apps/api/src/alicebot_api/store.py`
- `apps/api/src/alicebot_api/main.py`
- `tests/unit/test_20260310_0001_foundation_continuity.py`
- `tests/unit/test_events.py`
- `tests/integration/test_continuity_api.py`
- `BUILD_REPORT.md`
## additional existing seams preserved

- `POST /v0/responses`
- `POST /v0/approvals/requests`

## completed UI work

- replaced the raw manual thread-ID-first assistant flow with a selected-thread-driven `/chat` surface
- added a bounded right-rail continuity stack:
- visible thread list
- compact thread-create card
- selected-thread identity summary
- bounded recent continuity review for sessions and events
- updated assistant mode to submit against the selected thread instead of a typed UUID field
- updated governed mode to reuse the selected thread explicitly while keeping tool/action/scope controls unchanged
- preserved thread continuity across mode switches by carrying the selected thread in the route query
- added fixture continuity data so fallback states remain explicit and readable when the live API is not configured
- tightened spacing, containment, overflow handling, and responsive stacking for long IDs, pills, and continuity cards

## exact commands run

- `cd apps/web && npm run lint`
- `cd apps/web && npm test`
- `cd apps/web && npm run build`

## verification results

- `npm run lint`: PASS
- `npm test`: PASS (`40` tests)
- `npm run build`: PASS

## concise desktop visual verification notes

- `/chat` now reads with a clearer hierarchy: composer/history on the left, continuity selection/review on the right
- selected thread identity is repeated in a controlled way at the page header, composer, and summary card so context stays explicit without relying on a raw UUID input
- long thread IDs and metadata pills wrap inside their containers instead of leaking outside cards
- continuity review remains bounded and readable rather than becoming a transcript-style event dump

## concise mobile visual verification notes

- the wide layout collapses to one column at the existing responsive breakpoints
- thread review subpanels collapse from two columns to one column on small screens
- composer actions and secondary buttons expand to full width on mobile to avoid cramped wrapping
- selected-thread banners and summary toplines stack cleanly instead of forcing horizontal overflow

## blockers or issues

## tests run

- `./.venv/bin/python -m pytest tests/unit/test_events.py tests/unit/test_20260310_0001_foundation_continuity.py tests/integration/test_continuity_api.py`
- result: partial pass, then blocked by sandbox-local Postgres access for integration setup
- `./.venv/bin/python -m pytest tests/unit/test_main.py -q`
- result: PASS (`41` passed)
- `./.venv/bin/python -m pytest tests/integration/test_continuity_api.py`
- result: PASS (`2` passed)
- `./.venv/bin/python -m pytest tests/unit`
- result: PASS (`454` passed)
- `./.venv/bin/python -m pytest tests/integration`
- result: PASS (`145` passed)

## example thread create response

```json
{
"thread": {
"id": "30000000-0000-4000-8000-000000000003",
"title": "Gamma thread",
"created_at": "2026-03-17T10:00:00+00:00",
"updated_at": "2026-03-17T10:00:00+00:00"
}
}
```

## example thread list response

```json
{
"items": [
{
"id": "30000000-0000-4000-8000-000000000003",
"title": "Gamma thread",
"created_at": "2026-03-17T10:00:00+00:00",
"updated_at": "2026-03-17T10:00:00+00:00"
},
{
"id": "00000000-0000-4000-8000-000000000002",
"title": "Beta thread",
"created_at": "2026-03-17T09:00:00+00:00",
"updated_at": "2026-03-17T09:00:00+00:00"
},
{
"id": "00000000-0000-4000-8000-000000000001",
"title": "Alpha thread",
"created_at": "2026-03-17T09:00:00+00:00",
"updated_at": "2026-03-17T09:00:00+00:00"
}
],
"summary": {
"total_count": 3,
"order": ["created_at_desc", "id_desc"]
}
}
```

## example thread detail response

```json
{
"thread": {
"id": "00000000-0000-4000-8000-000000000002",
"title": "Beta thread",
"created_at": "2026-03-17T09:00:00+00:00",
"updated_at": "2026-03-17T09:00:00+00:00"
}
}
```

## example thread-session list response

```json
{
"items": [
{
"id": "10000000-0000-4000-8000-000000000001",
"thread_id": "00000000-0000-4000-8000-000000000002",
"status": "completed",
"started_at": "2026-03-17T09:00:00+00:00",
"ended_at": "2026-03-17T09:05:00+00:00",
"created_at": "2026-03-17T09:00:00+00:00"
},
{
"id": "10000000-0000-4000-8000-000000000002",
"thread_id": "00000000-0000-4000-8000-000000000002",
"status": "active",
"started_at": "2026-03-17T10:00:00+00:00",
"ended_at": null,
"created_at": "2026-03-17T10:00:00+00:00"
}
],
"summary": {
"thread_id": "00000000-0000-4000-8000-000000000002",
"total_count": 2,
"order": ["started_at_asc", "created_at_asc", "id_asc"]
}
}
```

## example thread-event list response

```json
{
"items": [
{
"id": "20000000-0000-4000-8000-000000000002",
"thread_id": "00000000-0000-4000-8000-000000000002",
"session_id": "10000000-0000-4000-8000-000000000002",
"sequence_no": 1,
"kind": "message.user",
"payload": {"text": "Hello"},
"created_at": "2026-03-17T10:00:00+00:00"
},
{
"id": "20000000-0000-4000-8000-000000000001",
"thread_id": "00000000-0000-4000-8000-000000000002",
"session_id": "10000000-0000-4000-8000-000000000002",
"sequence_no": 2,
"kind": "message.assistant",
"payload": {"text": "Hello back"},
"created_at": "2026-03-17T10:01:00+00:00"
}
],
"summary": {
"thread_id": "00000000-0000-4000-8000-000000000002",
"total_count": 2,
"order": ["sequence_no_asc"]
}
}
```

## blockers/issues

- no remaining code blockers inside sprint scope
- local sandbox execution initially blocked localhost Postgres access for integration setup; rerunning the Postgres-backed suite with unrestricted execution resolved verification
- `ARCHITECTURE.md` was updated after review so the documented runtime/API inventory matches the shipped `/v0/threads*` continuity surface

## recommended next step

Use these continuity endpoints in a follow-up `/chat` sprint so the operator can create a thread, browse visible threads, and load thread history without typing raw thread ids manually.
- no remaining blockers inside sprint scope
- no screenshot automation or browser capture was run during this pass; visual notes are based on the implemented layout, CSS breakpoints, and successful web build/test verification

## intentionally deferred after this sprint

- all UI work for thread selection, thread creation, and session history presentation
- any new session write endpoint
- any event rewrite, delete, or archive behavior
- any broader chat orchestration changes
- any Gmail, Calendar, auth, approval, task, execution, or runner scope expansion
- thread rename, archive, search, filter, and pagination
- full transcript tooling or unbounded event review
- thread-event mutation UI
- new backend continuity endpoints
- unrelated route redesigns
- Gmail, Calendar, auth, runner, connector, task-orchestration, or broader workflow scope expansion
Loading