hutch.git, branch v3.5.0

docs: add roadmap

2026-07-16T00:33:51+00:00

Four phases ordered by dependency, with feature gaps identified by diffing the schema dumps in Docs/API against actual call sites. Records Phase 0 as done and what unblocking CI turned up.

ci: run the test plan on macOS

2026-07-16T00:33:30+00:00

The builds.sr.ht job runs on Ubuntu and can only do secret scanning and structure checks, so the 214 tests ran only when someone remembered to run them in Xcode. That is why the suite had rotted to ten failures. builds.sr.ht has no macOS image and its maintainer has ruled them out, so xcodebuild cannot run there. Add a job on the GitHub mirror instead. Pinned to macos-26 because macos-latest still points at macOS 15, which lacks the iOS 26 SDK. The simulator is resolved at runtime rather than pinned by name, since device names shift between runner images.

fix: give inbox threads identity distinct from their grouping key

2026-07-16T00:31:17+00:00

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.

fix: render code span contents literally

2026-07-16T00:29:57+00:00

processInline protected allowlisted HTML tags before it handled code spans, so a `` written inside backticks was carried through as a live tag and applied formatting instead of rendering as text. Every other inline pass ran against code span contents for the same reason, so `**x**` in backticks was emitted as bold. Protect code spans first with their contents escaped, which takes them out of reach of the tag, emphasis, and link passes.

test: match cached incident fixture to its RSS source

2026-07-16T00:28:21+00:00
The expected incident declared url: nil while the cachedIncidentRSS it stands in for carries https://status.sr.ht/issues/1/, so the fixture contradicted its own input. The repository parses and persists the link correctly.

fix: stop shadowing serviceNotProvisioned classification

2026-07-16T00:26:27+00:00
"No such repository or user found" matched the broad "no such" test for .notFound, which ran first and made the .serviceNotProvisioned rule below it unreachable. Users hitting a service they have not activated were told the content was no longer available rather than that the account needs to enable the service. Order the specific check ahead of the general one.

fix: allow clearing a repository description

2026-07-16T00:25:27+00:00
metadataInputForSave assigned nil through the dictionary subscript to clear a description. Swift removes the key on a nil subscript assignment, so the mutation was sent with no `description` field and the old value survived — clearing a description silently did nothing. Store the nil with updateValue so the key is retained; AnyCodable already encodes an unmatched value as a JSON null.

test: assert image URLs are not double-escaped

2026-07-16T00:22:12+00:00
markdownImageQueryStringPreservesAmpersands rejected any "amp;metric" in the rendered HTML, but `&` is the correct encoding for `&` in an attribute value and is what a browser needs to request a literal `&`. The assertion conflated the URL with its HTML encoding. Target the real failure mode instead: double-escaping, which would send "&" through as part of the query string and break badge images.

test: repair stale expectations and request-body capture

2026-07-16T00:19:43+00:00
These tests drifted from the code and went unnoticed because CI never ran them. All four are test-side errors; no app behavior is involved. - TicketListViewModelTests asserted lowercase "resolved"/"fixed"/"reported" against TicketStatus/TicketResolution rawValues, which are uppercase to match the todo.sr.ht GraphQL enums. - HomeViewModelTests expected failedBuilds in ascending id order. Ordering moved to newest-first when sortBuildItemsForTriage landed in 5f6d545; the filtering the test covers is unchanged. - SettingsViewModelTests read request.httpBody inside a URLProtocol, where it is always nil because URLSession moves the body onto httpBodyStream. The stub now reads the body off the stream at capture time.

fix: repair test plan reference in Hutch scheme

2026-07-16T00:11:56+00:00
The Hutch scheme referenced `container:HutchTests`, omitting the `.xctestplan` extension, so `xcodebuild test -scheme Hutch` failed with "the test plan HutchTests could not be read". HutchTests.xcscheme already used the correct reference. The README directs contributors to the Hutch scheme, so this path needs to work before it can be wired into CI.