Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Complete the unified task, decision, agent and thread surfaces from Prostota

Aperta
  • Qualcosa non va?
#488 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Zamojski5 ci sta già lavorando.

Dal 11/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Part of #344 and #336 (F-026), in milestone 2, Flux — complete application and release. This carries forward the original unfinished outcome after the bounded #386 change. #344 remains open until the complete integrated criteria below pass. It creates no unrelated feature scope or SQL namespace reservation.

Outcome and fixed sources

A task, decision, agent or thread always opens in the same place: the right-hand panel on the computer or one sheet on the phone. The conversation stays visible. Implement the existing Prostota guide and the seven renders already attached to #344: desktop-panel, desktop-thread, desktop-blockerresult, phone-tasksheet, phone-taskfull, phone-thread and phone-blockerresult. S4, S9, S10, P10 and the existing S12 hand-off contract remain unchanged.

Acceptance criteria

  • AC-1. One panel component on the computer shows a task, a decision, an agent or a thread. The conversation stays visible, and Esc closes it. Other drawers and panels for these objects are removed.
  • AC-2. One sheet component on the phone has a grabber and two heights: half, with the conversation visible, and full, dragged up. Dragging down closes it.
  • AC-3. Task details are calm (P10): label and value rows, the blocker as a card, Results, Activity, and a composer at the bottom. The title and properties are edited in place (S10).
  • AC-4. Tapping the state glyph, or pressing 1–5, changes the state at once with Undo (S9).
  • AC-5. A thread opens in the same panel or sheet, with the root message on top and replies below.

Existing delivered fragments, without whole-criterion completion

#386 at independently reviewed e30ff86aa8557a9f7a1c18be23ac797d0a7788f2 supplies the task/decision/result Details header and Escape path; one DetentSheet implementation for those phone Details and Thread; half/full drag and keyboard handle; task label/value rows, blocker/Resolve and Results; inline title with retained failure/conflict drafts; chosen-state/1–5 updates and ordinary Undo that restores a blocker reason; and thread root/replies in the existing thread surface. The review's 41 Chromium checks are evidence on that original head, not full #344 acceptance or new composition evidence.

Remaining work within the original contract

  • Complete the common object surface across task, decision, agent and thread on both devices. Replace the separate desktop ThreadDrawer surface and applicable separate agent/task-thread, related-thought task sheet and live object-detail surfaces named in #344, preserving their current canonical data, permissions, routes and usable conversation. Sharing the phone component between Details and Thread alone does not complete all-object AC-1/2/5.
  • Complete drawn P10/S10: remove the remaining select-based owner control, make all required properties editable in place, deliver the drawn Due and agent/Hand off affordances and a real Activity history with its real authors/times, with the task composer at the bottom. A discussion root relabelled “Activity” does not deliver this feed. Preserve Results, blocker state/reason, title drafts, conflict/retry behavior and the accepted Linked thoughts requirement from #289.
  • Verify the complete unchanged AC-4 across the actual task state glyph actions and property controls, persisted state, 1–5 and Undo. The drawn desktop P10 status picker has a menu; this child does not invent a direct-cycle interaction for that property picker. Preserve genuine blocker restoration and truthful parked-work behavior under the existing domain contract; any unresolved contract conflict belongs on #336, not in a weaker acceptance claim.
  • Coordinate the agent hand-off integration with the existing #347 → #376/#383/#417 work. Preserve each child's ownership and criteria; their unmerged implementation is not already delivered by #386.

Required acceptance evidence

Use real native task/decision/agent/thread records and current allowed/denied readers, realistic conversation and result/activity content. Exercise the complete common-surface journey and relevant API/persistence/failure paths in Docker, at 1440×900 and 390×844 CSS px, light/dark; verify Escape/focus return, keyboard and actual touch in Chromium and WebKit, half/full/down-close, 44px targets, reduced motion and contrast. Obtain a fresh independent visual assessment from a neutral brief and the original renders, separately from interaction evidence. Keep source, runtime and test inputs pinned to the composed commit. Existing source equality or old counts cannot replace these checks; unavailable required checks remain unverified. Full #344/design/release acceptance waits for every original criterion above.

Implementation owner: Zamojski5 (claude-maurycy); evaluator: PelikanFix16 (codex-hubert). Resume the existing artifact after its dependency root is accepted, without another concurrent writer or unrelated implementation branch.

Ownership handoff, 2026-10-11 (explicit founder request): remaining implementation → Zamojski5; independent evaluator → PelikanFix16. Original criteria and v0.1 requirements are unchanged. Historical own PRs #384/#386 retain their existing authorship and branches; use a separate owner-controlled branch for the remaining outcome. See the linked handoff for immediately independent work and dependencies.

Lingua principale
TypeScript
Stelle
3
Fork
0
Merge medio
18h 3m
PR unite (30g)
254

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ColdPhase/flux

Tutte le issue di ColdPhase/flux

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.