Clarify UI UX roadmap follow-up

This commit is contained in:
mirivlad 2026-06-30 17:42:23 +08:00
parent b3d0de4b3b
commit 1535425986
3 changed files with 25 additions and 4 deletions

View File

@ -173,7 +173,7 @@ the plugin storage even when the Activity view is not mounted. The Activity UI
is a read/clear surface, not a manual recording toggle. It now reconstructs is a read/clear surface, not a manual recording toggle. It now reconstructs
compact worklog suggestions from scoped activity streams and exposes them compact worklog suggestions from scoped activity streams and exposes them
through the command-backed `verstak.activity.suggestWorklog` runtime contract through the command-backed `verstak.activity.suggestWorklog` runtime contract
for the future Journal plugin. for the Journal plugin.
## Sync Conflict UX Contract ## Sync Conflict UX Contract

View File

@ -50,8 +50,12 @@ Known remaining gaps:
- Sidecar host is not implemented. - Sidecar host is not implemented.
- Files/Notes are usable but not complete: chunked streaming/large-file import, - Files/Notes are usable but not complete: chunked streaming/large-file import,
richer conflict UX, and remaining Notes polish are still incomplete. richer conflict UX, and remaining Notes polish are still incomplete.
- Activity, journal, browser inbox conversion workflow, indexed search, - Activity, Journal, Browser Inbox conversion workflows, indexed Search, and
secrets, and templates plugins are not complete product features. Secrets now have baseline plugin implementations and public API contracts.
Their remaining work is product UX depth: richer Today aggregation,
actionable Activity to Journal review flows, capture/pairing discoverability,
production-grade reporting, and final polish.
- Templates plugin is not implemented yet.
- File/image preview exists as a basic provider with bounded inline image - File/image preview exists as a basic provider with bounded inline image
rendering through the public Files API. rendering through the public Files API.
- Browser extension repository has protocol, queue, and Chromium/Firefox build - Browser extension repository has protocol, queue, and Chromium/Firefox build
@ -154,6 +158,11 @@ Verification:
- provider selection tests; - provider selection tests;
- plugin lifecycle tests proving optional dependencies degrade cleanly. - plugin lifecycle tests proving optional dependencies degrade cleanly.
Status: baseline platform/product contracts are implemented. Remaining work is
tracked as UX follow-up rather than missing runtime foundation: Today should
make Activity suggestions and Journal imports actionable from the first
workspace screen, and Journal still needs reporting/timer/export depth.
### Phase 5 - Browser Inbox ### Phase 5 - Browser Inbox
Goal: capture browser context into the local vault through a public local Goal: capture browser context into the local vault through a public local
@ -180,6 +189,11 @@ Verification:
- local receiver API tests; - local receiver API tests;
- inbox plugin smoke/e2e tests. - inbox plugin smoke/e2e tests.
Status: baseline capture, routing, conversion, and Activity recording workflows
are implemented. Remaining work is UX follow-up: make extension pairing,
capture-from-clipboard/manual capture, domain binding state, and conversion
outcomes obvious in the visible app flow.
### Phase 6 - Secrets ### Phase 6 - Secrets
Goal: provide protected storage for credentials without turning secrets into Goal: provide protected storage for credentials without turning secrets into
@ -244,6 +258,11 @@ Verification:
6. [x] Browser inbox protocol design, extension scaffold, local receiver, 6. [x] Browser inbox protocol design, extension scaffold, local receiver,
minimal inbox plugin, and note/link/text-file/binary-file conversions are minimal inbox plugin, and note/link/text-file/binary-file conversions are
implemented. implemented.
7. [ ] Product UX follow-up in `verstak-desktop`: make the shell-level Today
flow the command center for captures, recent activity, Activity worklog
suggestions, and Journal import/review. This should reuse existing official
plugin contracts instead of moving Activity, Browser Inbox, or Journal into
desktop core.
This order finishes generic platform surfaces before building product features This order finishes generic platform surfaces before building product features
that depend on them. that depend on them.

View File

@ -480,7 +480,9 @@ Verification:
## Next Review Steps ## Next Review Steps
1. Design and implement the user-level Home/Today surface. 1. Design and implement the next Today follow-up: make captures, Activity
worklog suggestions, and Journal import/review actionable from the first
workspace screen.
2. Re-run: 2. Re-run:
- `GOFLAGS=-tags=webkit2_41 ./scripts/check.sh` - `GOFLAGS=-tags=webkit2_41 ./scripts/check.sh`
- `npm --prefix frontend run test:e2e` - `npm --prefix frontend run test:e2e`