docs(app): parity and handoff after landing the chat command and create lanes

This commit is contained in:
2026-10-22 22:35:26 +01:00
parent 1c5e4ed4c8
commit 59ea483aa3
2 changed files with 24 additions and 68 deletions
+1 -1
View File
@@ -40,7 +40,7 @@ or scratch servers only, never real operator sessions/runs/workflows.
| Artifact preview | Preview: image + markdown/text in-app through the chat renderer, paging, honest unsupported/external/HTTP states | video and HTML remain external-only |
| Artifact actions | Preview: external Open, Copy link, download and native share carry the recorded name/MIME bytes; progress, cancel, HTTP failure and unsupported-share states | OS share/download on Android/iOS remain unverified until the final build |
| Session audit/export repair facts | Preview: recorded export state/reason, repair request with one-shot submit and refusal, session.html external-only | rendered browser evidence for the repair control; full per-visit repair choices |
| Chat session management | Preview list + open session; shared create/rename/star/close/reopen with server-refreshed rows and full-width row refusals; local hide/undo and this device's read watermark (open rows only; a closed row never shows `New`) | dismissible web action-failed report (refusals stay under their row until the next accepted action), web `Open` badge and active/deep-linked read suppression, live `New` marks from pushed chat events, hide closing an already-open conversation, create dialog in the shell, editable create title (the web fixes `New chat`) |
| Chat session management | Preview list + open session; shared create/rename/star/close/reopen with server-refreshed rows and full-width row refusals; local hide/undo and this device's read watermark (open rows only; a closed row never shows `New`) | dismissible web action-failed report (refusals stay under their row until the next accepted action), web `Open` badge and active/deep-linked read suppression, hide closing an already-open conversation, create dialog in the shell |
| Chat history/live transport | Preview: `/chat` list and `/chat/:id` history, paging, live failure notice; composer integrated with the thread | run-detail-style reconnect verification in the real app |
| Chat message surfaces | Preview: formatted assistant markdown (safe links/headings/lists/tables/fences), user text exact, disclosures plain | exact attachments, unknown-part rendering beyond retained placeholders |
| Chat activity/reasoning/tools | Preview: one activity line, expanded native overlay with lifecycle/input/output/error/duration/edit diff | compaction wording variants |
+23 -67
View File
@@ -1,72 +1,28 @@
# Next session prompt (written 2026-10-22 ~19:00)
# Next session prompt (written 2026-10-22, late)
Paste this as the opening message:
---
Continue the Flutter port in /Users/alan/repos/pipelines. Read app/AGENTS.md,
app/WORK.md (sections "Chat tasks landing and native builds" and "Open wave
handoff") and app/PARITY.md first. Main is at 88476800 with 1563 tests passing;
the preview on port 8098 serves the published app/build/web (rollback
web-before-chat-tasks-1792688535). Use the CLI
/private/var/folders/jp/q0qvjyg54fl_c5vhhk1ylz2m0000gn/T/opencode/pipelines-cli-inlinefix-c303756
(rebuild it if the server-build warning blocks a command). Never change,
restart or rebind the Pipelines server. Keep git history free of any Claude or
AI attribution: no Co-Authored-By trailers, ever.
app/WORK.md, app/PARITY.md and this note first. Main is at the commit that
added this note; 1607 tests pass and flutter analyze is clean.
State of the open wave (Task v6 lanes on openai/gpt-6-luna, one worktree each
under tmp/flutter-<name> on branch flutter/<name>):
- Landed on their branch, ready to merge: 146 report format
(flutter/run-report-format 6eb2a7b8), 147 recent directories
(flutter/run-directories b8d18bcb), 149 background question notices
(flutter/chat-question-notice 42808814).
- Still running when I stopped: 140 /stop + /help (flutter/chat-cmd-stop), 143
runs filter menu (flutter/runs-filter-menu), 144 runs day groups
(flutter/runs-day-groups), 145 runs pipeline URL filter
(flutter/runs-pipeline-url). `pipelines inspect <id> --json` first.
- Failed: 148 composer paste (flutter/chat-paste) and 152 chat create dialog
(flutter/chat-create-dialog): read the stage outputs, preserve any uncommitted
worktree changes as a WIP commit, then fix directly or rerun with the findings
addressed. 151 live New marks is a WIP commit faa5cc00 on flutter/chat-live-new
(needs the lint fix at chat_session_local.dart:59, focused tests and clearing
activeSessionId when the conversation is left). 141/142/150 (/new /close
/rename) blocked three times on Luna; a direct Claude agent was implementing it
on flutter/chat-cmd-session — check that branch for its commit before redoing.
- Direct agent branches (worktrees under .claude/worktrees/): shell Runs-tab
attention badge worktree-agent-ab5296d8f4132ba79 (eb800928), search selection
probe worktree-agent-a81e60797507d2317 (4f0d2aab); the chat task-bar/model
chooser probe and the graph pulse/session repair probe agents had not committed
yet — check their worktrees for uncommitted tool/ and notes/ files.
Landed this session: runs-pipeline-url (main's filter menu superseded the
lane's pipeline menu; URL routing kept), chat /stop + /help (+ the web's
`Stopping the running turn…` line), live New marks (active chat cleared on
leave), /new /close /rename, and chat create dialog parity (fixed `New chat`
title, `Home (~)` sends `~`, harness picker only with >1 backend, preloaded
instructions, model note, `Start in …`).
For each green branch: merge into main, `flutter test` + `flutter analyze` in
app/, fix fixture fallout yourself, `flutter build web --output build/web-next`
then publish by renaming (keep a web-before-<name>-<ts> rollback), one commit
per landing, then update the PARITY rows. After the wave, start the remaining
lanes listed under "Still to start" in WORK.md, keeping the lane contract (one
behaviour, small file budget, exact web wording in the prompt; the briefs with
that wording are in the session scratchpad briefs/ and in the run prompts of
140-152). Mobile: the Android testing APK is at
app/build/android-testing/pipelines-next-67045f25.apk; the phone still needs a
reachable endpoint, which is the operator's decision (a tailnet TLS-terminated
forward of 127.0.0.1:8080 gives wss:// with no manifest change). Keep answers
to a few sentences.
Preview: build/web published (JS 1e4e1877); rollback
web-before-chatcmds-1792704916.
Late findings (after the prompt above was written):
- Shell Runs-tab attention badge is DONE on worktree-agent-ab5296d8f4132ba79
(eb800928, +454/-15, analyze clean, 239 focused tests green). Merge it first;
its pipelines_app.dart/runs_destination.dart/runs_list.dart/screen.dart hunks
are additive and will touch run 145's edits.
- Search selection probe is DONE on worktree-agent-a81e60797507d2317 (4f0d2aab,
22 captures in app/build/search-selection-probe/, note
app/notes/search-selection-probe.md). It found two lib defects to fix as
manager work: (1) a retired-field hit after a field hit leaves the earlier
Summary section expanded (`RunDetailTabs._selectSearchTarget` never collapses
on `section: null`, run_detail_tabs.dart); (2) a step hit opens the wrong visit,
off by one: `_openSearchResult` in pipelines_app.dart passes the server's
1-based `visit` into the zero-based `AppRoute.run.stage(visit:)`.
- Main now also carries 0acd7346 `feat(chat): add Claude Code chat backend` and
83d013f1 from another session; with it, three chat tests fail
(chat_model_picker_test, chat_screen_model_test, chat_thread_header_test: a
`chat-model` button appears where the fixture expects none, because
`supportsChatModels` now includes `claude`). Fix the fixtures or the rule
before trusting a full-suite run.
---
Superseded WIP kept for reference only: flutter/chat-paste (9baed7ea, landed
via chat-paste-2), flutter/chat-create-dialog (09d17b18, redone as
flutter/chat-create-parity).
Open decision: Flutter's /rename sends the shared server rename (matching its
own Rename dialog); the web's /rename is device-local. The usage line still
says "on this device".
Remaining functionality: dismissible action-failed report, attachment history
reconciliation, persisted endpoint at native boot, protocol-mismatch warning.
Mobile: phone needs a reachable endpoint (operator decision), then device
verification and iOS portability audit.