krz/hutch

 1# Out of Scope Features
 2
 3- Universal links (requires Sourcehut to host an apple-app-site-association
 4  file)
 5- Push notifications for builds and tickets (requires a backend relay server)
 6  - ref: https://git.sr.ht/~ccleberg/hutch-notify
 7- Explore / search (hub.sr.ht) (no public discovery API)
 8- ~~Pronouns on profile (not in GraphQL schema)~~ — **stale**. sr.ht added
 9  pronouns (see the Q1 2026 "What's cooking"), and Hutch already queries them in
10  `AppState` and shows them in `UserProfileView`. Left here struck through as
11  evidence for the ingestion task in ROADMAP.md: this entry spent months telling
12  people not to build something that was already built.
13- Revoke personal access tokens (`@internal` in schema, inaccessible)
14- Archive a message to a list (`archiveMessage` is `@internal`, inaccessible)
15- Ticket activity feed (todo.sr.ht's root `events` query is broken upstream and
16  returns an empty list for every user). `event.participant_id` references
17  `participant(id)`, but the resolver joins it against `participant.user_id`:
18
19  ```sql
20  FROM event ev
21  JOIN participant p ON p.user_id = ev.participant_id   -- id space vs user id space
22  WHERE p.user_id = <viewer>
23  ```
24
25  The rows exist — the writer inserts `participant.ID` for the submitter and for
26  every subscriber — but that join cannot find them. `Ticket.events` is
27  unaffected because it filters on `ev.ticket_id`, which is why ticket timelines
28  work. Nothing a client can do fixes this; revisit only if sr.ht changes the
29  resolver.
30- Subscribe to a mailing list (`mailingListSubscribe` exists, but `MailingList`
31  has no `subscription` field and sr.ht has no discovery API, so there is no way
32  to find a list you are not already subscribed to — see hub.sr.ht above)
33- Submitting patches (a `git send-email` flow, not a GraphQL mutation; Hutch
34  reviews patchsets but cannot send them)
35
36## Declined rather than blocked
37
38These are reachable in the API. They are left out on judgement, not capability.
39
40- **Webhook management** (24 fields across five services). A webhook needs an
41  HTTPS endpoint you control to receive POSTs. Without the relay above, this
42  only serves someone already running their own endpoint, and that person is not
43  managing it from a phone. Reconsider if `hutch-notify` ever ships.
44- **`shareSecret`.** Shares a build secret — an SSH key or PAT — with another
45  user. A mistap grants someone else a credential, and nothing in the app can
46  take it back. That belongs on the web behind a full-size confirmation. The
47  read-only `secrets` list would be fine on its own.
48- **Build groups** (`createGroup`, `startGroup`). Multi-job pipelines are
49  authored in `.build.yml`, not composed on a phone.