summaryrefslogtreecommitdiff
path: root/Shared/SourceHutWebDeepLinkMapper.swift
diff options
context:
space:
mode:
authorChristian Cleberg <[email protected]>2026-07-16 01:31:26 -0500
committerChristian Cleberg <[email protected]>2026-07-16 01:33:49 -0500
commit784d9bcc7dffe36525767c86e768d4a877585718 (patch)
tree4f13e414aab89d9c018b12076f2443cb341f871e /Shared/SourceHutWebDeepLinkMapper.swift
parent8e585a709d8979d493fef3ed4015db93687f48e8 (diff)
downloadhutch-784d9bcc7dffe36525767c86e768d4a877585718.tar.gz
hutch-784d9bcc7dffe36525767c86e768d4a877585718.tar.bz2
hutch-784d9bcc7dffe36525767c86e768d4a877585718.zip
docs: record the SonarCloud backlog and the What's cooking task
Two additions to Phase 3. SonarCloud, with the breakdown rather than the headline: 51 open issues are 0 bugs, 0 vulnerabilities and 51 code smells, and 35 of those are hardcoded-URI warnings against a deep-link mapper's test fixtures and a one-forge client's endpoint constants. Those want triaging as Won't Fix, not refactoring. The part worth real thought is the 3 hotspots — the sr.ht token is stored without a SecAccessControl, so an unlocked phone hands it over, which is a product decision rather than a lint nit. Ingesting sr.ht's quarterly "What's cooking" posts, because nothing here tracks the API's evolution and this repo's assumptions rot silently. Already proven worthwhile: SCOPE.md claimed pronouns were not in the schema while AppState queries them and UserProfileView displays them. That entry is struck through and kept as evidence. Q2 2026 also reports a writable hub.sr.ht API and finished deploy keys, both of which contradict what is written here.
Diffstat (limited to 'Shared/SourceHutWebDeepLinkMapper.swift')
0 files changed, 0 insertions, 0 deletions