Drop TachiyomiSY mentions from comments

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

dep_freshness/_tables.py

@@ -208,7 +208,7 @@ ALLOWLIST_MAX_DAYS: Final = 90
 TRANSITIVE_PREFIX: Final = "transitive:"
 # A fork's predicate: the entry holds only while the upstream repository's own
 # copy of the same manifest pins the same version, and dies the day upstream
-# bumps. TachiyomiSY cannot take moko-resources 0.27.0 (a 300-file accessor
+# bumps. A fork that cannot take a release (e.g. a 300-file accessor rewrite
-# rewrite that breaks every future upstream string) before jobobby04 does.
+# that breaks every future upstream string) before its upstream does.
 UPSTREAM_PREFIX: Final = "upstream:"
 GITHUB_RAW: Final = "https://raw.githubusercontent.com/{repo}/HEAD/{path}"

dep_freshness/parsers/gradle.py

@@ -3,7 +3,7 @@
 The version catalog is the one place a Gradle build should declare versions,
 which makes it a manifest the gate can read without evaluating Kotlin DSL.
 A build may have several (`settings.gradle.kts` can `from(files(...))` any
-`*.versions.toml`; TachiyomiSY has three), so the suffix is what is matched.
+`*.versions.toml`; a large app can have several), so the suffix is what is matched.
 Three shapes appear in `[libraries]` and `[plugins]`:
 
     foo = "group:artifact:1.2.3"                         # inline string
@@ -12,7 +12,7 @@ Three shapes appear in `[libraries]` and `[plugins]`:
     plug = { id = "com.example.plugin", version.ref = "x" }
 
 A library with no version is managed by a BOM (`junit-platform-launcher`
-in TachiyomiSY) and is skipped: the BOM's own entry is the pin that counts.
+in a typical app) and is skipped: the BOM's own entry is the pin that counts.
 A rich version table (`{ strictly = "1.2" }`) is read as the constraint it
 spells and lands as unpinned when it is a range, like every other ecosystem.
 

dep_freshness/registries/gitcommit.py

@@ -1,6 +1,6 @@
 """JitPack artifacts pinned to a commit: "newest" is the default branch's HEAD.
 
-Seven of TachiyomiSY's dependencies are `com.github.<owner>:<repo>` at a
+Some Android builds depend on `com.github.<owner>:<repo>` at a
 short hash. No registry lists a "latest" for those, and a hash is not a
 version, so the gate's question becomes the only one a commit pin admits:
 is the pinned commit still what the source repository's default branch

dep_freshness/upstream.py

@@ -1,8 +1,8 @@
 """The `upstream:` predicate: does the fork's upstream still pin this version?
 
 A fork cannot always take a release before the project it tracks does --
-moko-resources 0.27.0 rewrites every string accessor across 300 files of
+a library that rewrites every string accessor across 300 files of the fork
-TachiyomiSY and would break each future upstream commit that adds a string.
+would break each future upstream commit that adds a string.
 "Wait for upstream" is the honest reason, and it is checkable: fetch the
 upstream repository's copy of the SAME manifest, parse it with the same
 parser, and compare the pin. Equal means the entry holds; different means

file_length/repo_exempt.py

@@ -2,7 +2,7 @@
 
 The shared tables in :mod:`file_length._tables` hold exemptions that are true
 everywhere (generated, vendored, wordlists). A fork of a third-party project
-can also carry data that is code only by extension -- TachiyomiSY's
+can also carry data that is code only by extension -- e.g. a fork's
 ``exh/eh/tags/*.kt`` are 6000-line string tables that upstream regenerates --
 and that knowledge belongs next to the data, in the repo, not in a shared
 list every other repo loads.
@@ -60,7 +60,7 @@ def glob_to_regex(pattern: str) -> re.Pattern[str]:
     `**` spans directories, `*` and `?` stop at a slash. Hand-rolled rather
     than `PurePath.full_match` because that needs Python 3.13 and the gate
     runs on whatever `python3` a CI runner ships (3.12 broke it in the
-    TachiyomiSY fork's first CI run).
+    a fork's first CI run).
     """
     out: list[str] = []
     i = 0