You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the coordination thread for the launcher/home widget audit workstream of the
LifeOps Personal Assistant MVP (GitHub project 15). Full research, inventory with
file:line evidence, verdicts, and the wallet-widget spec live in the repo:
Research doc:packages/docs/ongoing-development/research/03-launcher-widgets.md
Doctrine / decisions adopted
The resting home is sparse: date+time, weather, the notification center (when
notifications exist), and the wallet widget. Nothing else renders on a healthy, quiet
account.
Wallet widget spec: always visible; tracks BTC, SOL, ETH prices by default; shows
top-3 held assets when the user holds priced tokens ≥$1; trending movers only as fill
for missing snapshots. Price-only forever — never amounts or holding values (feat(app/launcher): hideable time/date widget, price-only wallet widget, and pull-down notification center #10706).
Built entirely on the existing GET /api/wallet/market-overview + getWalletBalances() plumbing; no new endpoints.
LifeOps attention cards stay (calendar, todo, goals, sleep, needs-response,
FTU welcome, model-download/agent-provisioning setup tiles) because they are the MVP's
subject matter and self-hide when idle. Their self-hide contract gets e2e enforcement.
Seven widgets leave the home slot: orchestrator activity + apps, feed agent
activity, automations ("Tasks", which never self-hides), finances, relationships,
inbox. Their routed views and chat-sidebar entries remain.
Widgets must poll only while the document is visible (the AppRunsWidget 5s raw setInterval is the one violation — being fixed).
Chat is primary; the home is a glanceable field behind the floating chat. Orange is
accent only, no blue, no card chrome, no suggestion chips.
Sequencing: 1 and 2 are independent and can run in parallel. 4 can land inside 1's PR or
separately. 5 should land after 1+2 so the resting-state assertion matches the new
doctrine. 6 goes last (it deletes the participation table that issue 1 may briefly add
rows to for the coverage gate).
How to claim work
Comment on the issue you're taking ("claiming — session/branch ") and move
the card on project 15 to In Progress. One issue per agent at a time.
Before starting, check the issue is still open AND git log origin/develop on the
files you'll touch — the swarm merges fast and duplicated work is wasted work.
Branch as fix/<issue#>-<slug> or feat/<issue#>-<slug> off develop; PR against develop; rebase on origin/develop and run bun run verify before marking ready.
Push early and often — unpushed branches do not survive session resets.
Evidence rules (changed mechanics — read this)
Evidence is now posted inline in the GitHub issue/PR, not committed to .github/issue-evidence/:
MP4 for videos (they render inline in GitHub) — full walkthrough of the flow you
changed, desktop and mobile where applicable.
JPG for screenshots (size) — full-page, before AND after; for bug fixes the before must show the wrong behavior.
Logs (browser console + network, server [ClassName] structured logs) pasted in
collapsible blocks or attached as text.
Real-LLM trajectories only where agent/model behavior changes (none of these issues
should need one — mark N/A - <reason> explicitly, never leave the row blank).
bun run --cwd packages/app audit:app for anything touching the home view; no page
ships with a computed needs-work/broken verdict.
Every issue in this workstream lists its exact evidence set — treat those lists as the
merge gate. A reviewer must be able to confirm the change works without reading the code.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
This is the coordination thread for the launcher/home widget audit workstream of the
LifeOps Personal Assistant MVP (GitHub project 15). Full research, inventory with
file:line evidence, verdicts, and the wallet-widget spec live in the repo:
Research doc:
packages/docs/ongoing-development/research/03-launcher-widgets.mdDoctrine / decisions adopted
notifications exist), and the wallet widget. Nothing else renders on a healthy, quiet
account.
top-3 held assets when the user holds priced tokens ≥$1; trending movers only as fill
for missing snapshots. Price-only forever — never amounts or holding values (feat(app/launcher): hideable time/date widget, price-only wallet widget, and pull-down notification center #10706).
Built entirely on the existing
GET /api/wallet/market-overview+getWalletBalances()plumbing; no new endpoints.FTU welcome, model-download/agent-provisioning setup tiles) because they are the MVP's
subject matter and self-hide when idle. Their self-hide contract gets e2e enforcement.
activity, automations ("Tasks", which never self-hides), finances, relationships,
inbox. Their routed views and chat-sidebar entries remain.
AppRunsWidget5s rawsetIntervalis the one violation — being fixed).accent only, no blue, no card chrome, no suggestion chips.
Issues (work items, most important first)
Sequencing: 1 and 2 are independent and can run in parallel. 4 can land inside 1's PR or
separately. 5 should land after 1+2 so the resting-state assertion matches the new
doctrine. 6 goes last (it deletes the participation table that issue 1 may briefly add
rows to for the coverage gate).
How to claim work
the card on project 15 to In Progress. One issue per agent at a time.
git log origin/developon thefiles you'll touch — the swarm merges fast and duplicated work is wasted work.
fix/<issue#>-<slug>orfeat/<issue#>-<slug>offdevelop; PR againstdevelop; rebase onorigin/developand runbun run verifybefore marking ready.Evidence rules (changed mechanics — read this)
Evidence is now posted inline in the GitHub issue/PR, not committed to
.github/issue-evidence/:changed, desktop and mobile where applicable.
before must show the wrong behavior.
[ClassName]structured logs) pasted incollapsible blocks or attached as text.
should need one — mark
N/A - <reason>explicitly, never leave the row blank).bun run --cwd packages/app audit:appfor anything touching the home view; no pageships with a computed
needs-work/brokenverdict.Every issue in this workstream lists its exact evidence set — treat those lists as the
merge gate. A reviewer must be able to confirm the change works without reading the code.
Filed issues
Design doc · MVP board
Beta Was this translation helpful? Give feedback.
All reactions