Drilldown sections: State Banner & अपडेट

The two sections at a glance

Every task drilldown opens with the same two cards at the top. They look similar but answer different questions.

Install drilldown — every banner state

Mapped in InstallStateBanner.kt → bannerVariantFor().

Service Ticket (Restore) drilldown — every banner state

Mapped in RestoreDrilldownContent.kt → RestoreStateBanner().

अपडेट section — deep dive

Purpose

The अपडेट section is the chronological event log for a task. While the banner answers "where are we now?", अपडेट answers "how did we get here?". Every state morph, slot proposal, technician assignment, or system action that happens to this task gets appended as a row.

Visual anatomy

• Header: timeline icon + title ("अपडेट" / "Updates") + optional unseen-count badge + expand/collapse chevron in a circular tap-target.
• Body: vertical list, newest at top. Each row = event description (left, weight 1f) + timestamp (right, fixed).
• Unseen rows: rendered with bgBrandTint background and textPrimary color (vs textSecondary for read rows).
• "और देखें" link in brand-magenta sits below the list when more pages remain on the server.

Data model

data class TimelineEventInfo(
    val timestamp: String,        // pre-formatted by BE, e.g. "10 Apr, 10:14 AM"
    val description: String,      // Hindi copy from BE
    val timestampEn: String = "",
    val descriptionEn: String = "", // English copy from BE
)

// On TaskDetail:
val timeline: List<TimelineEventInfo> = emptyList()  // current visible page(s)
val timelineTotalElements: Int = 0                    // total on server
val timelineLoadedPage: Int = -1                      // highest page idx loaded

Backend returns the timeline ordered DESC (newest first). The client never re-sorts — it just appends incoming pages to the end.

Pagination — how "और देखें" works

Link copy: "और देखें ({count} और)" / "See more ({count} more)". The displayed count always advertises the next page size (5) so the copy doesn't decrement on every tap (15→10→5 would feel like progress is slowing down). The final tap may load fewer than 5 if the total isn't a multiple of the page size — that smaller count is shown then.

Unseen handling — the pink-tint rule

Each task carries unseenCount on its drilldown payload (latest_attention_version − acked_attention_version on the backend).

• Snapshot at entry: when the drilldown opens, the composable captures initialUnseenCount = remember { task.unseenCount }. This freezes which rows are "new" for the lifetime of this drilldown view.
• Tint logic: isUnread = index < initialUnseenCount. Since the list is DESC, the top N rows are the unseen ones.
• Auto-expand: section opens automatically iff unseenCount > 0. The remember(task.unseenCount) key on expanded means a fresh push (e.g. an in-session event arriving) re-expands the section even if the user had previously collapsed it.
• Dismissal: HomeViewModel.onDismissTaskDrilldown ACKs the latest attention version server-side, dropping unseenCount to 0. Next time the drilldown opens, no rows are tinted.

States that trigger a new timeline entry (Install)

Behaviour-rules summary

Install vs Restore — differences

Worked example: Wiom wants to nudge a slow CSP

Scenario: An install task is in AWAITING_TECHNICIAN_ASSIGNMENT, the slot day is approaching, and Wiom decides the CSP needs to hurry up. Where does that message live — banner or अपडेट?

How the nudge cascades through the app

Wiom's backend doesn't transition the state — it pushes one new TimelineEventInfo with unseenCount bumped. That single signal lights up multiple surfaces:

What the partner sees, step by step

1. Wiom backend posts the nudge → push notification arrives on the phone.
2. CSP opens the app → the नया काम chip on Home has a pink dot.
3. CSP taps into the task drilldown.
4. Banner is still warning yellow, still saying "टेक्निशियन चुनना बाकी है" — but the deadline pill now reads "2 घंटे बाकी" in urgent colour.
5. अपडेट section is auto-expanded with a pink "1" badge.
6. The new row sits at the top, pink-tinted:

Why this design is intentional

1. Banner is predictable: the title is a function of state. If "hurry up" messages overwrote the banner, the CSP would never know whether the visible copy reflects the actual task state or a transient nudge.
2. History is preserved: a nudge in अपडेट stays visible forever (paginated). The CSP can scroll back and see "Wiom told me to hurry at 10:14 AM" even after they've taken action.
3. One signal, many surfaces: bumping unseenCount is the single switch that lights up the chip dot, section badge, task card dot, and bell — without each surface needing its own urgency channel.

The dividing line — when banner WOULD change

Banner colour families — visual reference