ios client for sourcehut. swiftui. http://git.krz.sh/krz/hutch.git/atom?h=main 2026-07-16T21:59:55+00:00 2026-07-16T21:59:55+00:00 Christian Cleberg hello@cleberg.net 2026-07-16T21:59:55+00:00 urn:sha1:7b817a1d2aed0e8b89f36b410f2779f4a6b35407 Replace the disruption-only banner on the Home tab with a persistent circular status indicator in the navigation bar, next to the "Home" title. The badge reflects the existing status logic — green/check when operational, orange/exclamation on disruption, gray otherwise — and taps through to System Status. SystemStatusSummaryRow is unchanged and still used by the More tab. Resolve the system-status result first in HomeViewModel.loadDashboard so the badge settles from cache immediately instead of waiting on the slower projects/jobs/tickets/inbox loads, which had left it spinning for several seconds. Bump MARKETING_VERSION to 3.8.2 and record it in ROADMAP. 2026-07-16T15:13:46+00:00 Christian Cleberg hello@cleberg.net 2026-07-16T15:13:46+00:00 urn:sha1:65412ee9818bf251fd5caac231746b04c7eca23f loadDashboard(forceRefresh:) fanned the flag out to five loaders, but loadProjects and loadSystemStatusSnapshot dropped it: they called fetchProjects() and snapshotResult() with no policy, so pull-to-refresh returned cached projects and status while the other three sections refreshed. SonarCloud flagged both params as unused (swift:S1172). Thread forceRefresh through ProjectService.fetchProjects into the page policy (refreshIgnoringCache when forced), and pass it to snapshotResult, which already accepted it. ProjectsListView carried the same latent bug via its own .refreshable — fixed there too now that fetchProjects can force. 2026-07-16T04:18:20+00:00 Christian Cleberg hello@cleberg.net 2026-07-16T04:18:20+00:00 urn:sha1:97e8b49fcb56751fa0e80a332484db8252753417 Thread.updated is the root email's insert time. It never advances when a reply arrives, despite the name and despite the schema describing threads as ordered "most recently bumped". sr.ht returns updated seven seconds after root.date on a thread carrying four replies: subject: "Re: test post" updated: 2026-07-16T03:44:55Z replies: 4 root: { date: 2026-07-15T22:44:48-05:00 } The app fed that field into lastActivityAt everywhere, so a reply to an old thread was invisible: it did not mark the thread unread, did not raise it in the list, and did not update the timestamp beside it. This was inert until the unread baseline landed, because an absent view record returned unread unconditionally and the date was never compared to anything. The baseline did not break unread; it was the first code to depend on that field meaning what it says. Use MailingList.emails instead, which is real reverse-chronological arrival data, keyed by thread root id. The scan stops once it is older than the cutoff, so a quiet list costs one page and a busy one costs only what is new. Threads with nothing in the window keep the root timestamp and stay read, which they already were. Failure returns empty activity rather than throwing: unread is a decoration and should not take the thread list down with it. Uses Email.received rather than Email.date — received is server-side and non-null, date comes from the sender's header and is neither. 2026-07-16T03:51:41+00:00 Christian Cleberg hello@cleberg.net 2026-07-16T03:51:41+00:00 urn:sha1:91023a6572354af7770309715d1d77e978298b0d New mail showed as unread inside a mailing list but not on Home. The list view reads threads with client.execute, so it always sees the server. Home reads them with executeCached under cacheFirstThenRefresh, which returns the cached value and only schedules a background fetch. loadDashboard had no way to bypass that, so pulling to refresh could not surface mail that arrived after the last fetch — it returned the same cache it already had and Home stayed a cycle behind. Thread forceRefresh through loadDashboard to the cached reads, and use it from the pull to refresh on Home and Work. Matches loadSystemStatus(forceRefresh:), which MoreView already refreshes this way. The staleness predates the unread baseline. It was invisible while every thread counted as unread, because Home always had a large number to show; now that Home correctly ignores mail older than sign-in, a stale cache reads as a truthful 0. 2026-07-16T00:31:17+00:00 Christian Cleberg hello@cleberg.net 2026-07-16T00:31:17+00:00 urn:sha1:eff81f34bb51ecc6e0aa5d831567db2cea0527a9 InboxThreadSummary.id returned threadGroupingKey, which is listRID plus the subject with Re:/Fwd: stripped. Two unrelated threads on one list sharing a subject therefore shared an id — common on sourcehut, where "[PATCH] test" is an ordinary subject — which collides under Identifiable in every list that renders these summaries. Key id on the root Message-ID, which is unique per thread, and leave threadGroupingKey subject-based so replies still collapse into one conversation. Read state moves to threadGroupingKey at each call site. It was already keyed on that string via id, so persisted keys are unchanged and marking a conversation read still covers the whole subject group, matching how HomeViewModel already builds the key for isUnread. 2026-05-14T18:27:41+00:00 Christian Cleberg hello@cleberg.net 2026-05-14T18:18:55+00:00 urn:sha1:51b2eb0e6296734960f37cebd40fee34a1f261f9 - add read-only App Intents for core Hutch workflows - route intents through the existing Hutch navigation/deep-link model - expose Work Queue, Recent Activity, System Status, pinned resources, projects, failed builds, assigned tickets, saved searches, and search where supported - keep App Intents non-mutating for the initial implementation - preserve existing widget, Safari extension, and hutch:// routing behavior References: https://todo.sr.ht/~ccleberg/hutch/71 2026-05-07T01:41:49+00:00 Christian Cleberg hello@cleberg.net 2026-05-07T01:41:49+00:00 urn:sha1:205cf2687ce48f3d004792ff223422a86cc6bdbc Add a bounded stale-while-revalidate cache at the Sourcehut API boundary with stable keys, centralized TTLs, request coalescing, payload hashing, and LRU disk pruning. Cache high-value read-only repo, build, ticket, project, profile, paste, and Home/Work Queue data while keeping mutations network-only and invalidating related prefixes after successful writes. Add focused cache tests and implementation notes. 2026-04-23T22:39:13+00:00 Christian Cleberg hello@cleberg.net 2026-04-23T22:39:13+00:00 urn:sha1:66601a8091a73f3e31f4fb534c38b3eca4756e93 2026-04-20T18:15:04+00:00 Christian Cleberg hello@cleberg.net 2026-04-20T18:15:04+00:00 urn:sha1:380fb866d090c5f13b2ad3f88f1fe23c4ade4801 2026-04-20T18:04:57+00:00 Christian Cleberg hello@cleberg.net 2026-04-20T18:04:57+00:00 urn:sha1:8b73fd9cd43753b36b3ab3ca5e4dc83a47ea3480