tasks: a row says its state once, an abandoned call is said in whole seconds, and a conversation root names its folder only where that is news

[santoshkumarradha]

Part of #884 — lane T, the first of two. Lane P builds the record pane on top of the table
that follows this.

Three defects on the owner's screenshot, and all three were the same shape: one fact with
two writers.

stopped · stopped

internal/session's taskGradeOutcome spells a stopped node's own outcome as the literal
"stopped", and tasksMiddle hung that outcome off taskStateWord(entry) — so the page said
one reading twice because each writer thought it was the one saying it.

The fix is not a string. session.TaskStatus.RowWord() is the join, written down once: the
word, the reason, and the rule that a reason merely restating the word is not said again. It
is what the column beside a conversation already reads (tierRowBody), so the two surfaces
now say the same sentence about one row by construction rather than by agreement. Three
hand-rolled compositions in tasksMiddle collapse into it, and tasksNote stops spelling a
state word at all — it is now only which window the work is in.

Consequence, and it is #884's own ruling for the table arriving a PR early: the record's raw
outcome sentence leaves the row. On every row the engine grades, that sentence WAS the state
word in different clothes; where it is real prose it belongs on the record card, which is one
enter away. The row's degradation ladder is now 2 files · your call · nobody could check it
→ your call · nobody could check it → your call: the word a list is scanned for is the last
thing a narrow frame gives up.

one call ran 29.24078975s without answering and was abandoned

time.Duration.String is the engine talking to itself — eight decimal places of a figure
nobody can act on, and the nanoseconds were never a fact about the run, only the resolution of
the clock. checkerStalled now spells the bound with taskSpanWord, this package's one
spelling of how long something took.

The ~ at the right of a conversation root

docs/design/home-mission-control/DESIGN.md §1 retired ~ as a project name and the project
tag on rows in this window's own folder. Home obeyed it; the tasks place drew both. New
internal/tui3/projecttag.go holds chatProjectWord — that rule, once — and home's
chatProjectTag is now two lines delegating to it.

The bar

• One abstraction: session.TaskStatus.RowWord() reused rather than re-spelled, and
  chatProjectWord extracted so two pages ask one rule. Anyone drawing a list of work or a
  list of conversations can use both.
• Deleted: three compositions in tasksMiddle, the state-word branch of tasksNote, the
  session.TaskReasonOf and refused() calls this page made for itself, and the raw-outcome
  fact on the row.
• Guarded by: TestARowSaysItsStateWordOnce, TestTheRowTakesItsStateAndReasonFromTheOneJoin,
  TestAConversationRootWearsAFolderTagOnlyWhereItIsNews, TestAnAbandonedCallIsSaidInWholeSeconds.
• Seam reported, not patched: checkerRanOut still says window.String() (5m0s). That
  window is a configured ceiling rather than a measured elapsed, and taskSpanWord's 5m 0s
  is not an improvement; it wants a ceiling spelling, which is a different question.
• Other lane's file: six lines in internal/tui3/homepanel_recent.go (lane H's), turning
  chatProjectTag into a delegation.

🤖 Generated with Claude Code