docs(app): set the remaining autonomous queue in dependency order

This commit is contained in:
2026-10-22 01:09:06 +01:00
parent d5f24b8259
commit cb0242b709
+40
View File
@@ -473,3 +473,43 @@ resuming or retrying; preserve partial work. On success inspect actual diff and
checks, integrate, verify ancestry, then launch the next ready item. Do not
rerun completed work just because session export or landing failed. Keep source,
tests, landing and preview states separate. No production cutover in this phase.
## Remaining queue after the 95-101 wave
Autonomous target: finish every row in `PARITY.md` except the mobile build, which
stays last by agreement. Each item is one reviewed slice with focused tests and a
both-host browser probe where it is visible.
In flight: 95 recorded visit pane; 96 chat permission/question cards; 97 start a
pipeline; 98 chat list create/rename/star/close; 99 artifact download/share as
named files; 100 notification capability + transition dedupe; 101 graph
pan/zoom/expanded view.
Then, in dependency order:
1. Manager wiring: notification permission tile into Settings and transition
notifications from the Runs attention controller; graph expanded view opened
from the pipeline Graph tab.
2. Search result target routing (pipeline/version/field/visit/artifact) in
`application/search_destination.dart` plus the minimum public selection APIs in
the owning features.
3. Chat attachments: picker + paste, 1 MiB bounded envelope, named removable
chips, history reconciliation.
4. Chat activity/reasoning/tools overlays with lifecycle, input/output, error,
duration and edit diff.
5. Chat model selection, numeric Info (unknown != 0) and bounded background-task
pages.
6. Chat slash command palette, unknown-command send-as-message, dismissible local
notices, saved scroll/follow.
7. Run summary fields and exact empty/unknown wording; changes per-visit capture
entry and paging; session audit/export repair facts.
8. Artifact turn documents in the gallery (input/memory/output/session.html).
9. Pipeline list summary metadata/miniatures and pinned detail URLs; schedules
list entry/route, timer provenance and schedule-this-run seeding.
10. Deep links: pipeline/version/stage/template/chat URLs and action/visit
queries; transport foreground recovery, persisted endpoint boot, protocol
warning, complete refresh semantics.
11. Templates link from a run detail; authenticated preview smoke notes.
12. Android testing build, iOS portability audit, device verification.
Standing rules: keep the preview published with a rollback after each landing;
never claim authenticated production mutations, OS sharing/notifications on
mobile or device behaviour from web fixture evidence; keep mobile labelled
unverified until the final build.