You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5adcad7
Browse filesBrowse the repository at this point in the historyBrowse files
docs(coil): re-baseline the seam ledger and correct the runbooks (#71)
The ledger asked that a second displacement "argue for itself in this file the way that one did",
so it does. 47 upstream-owned files, +2074/-933 — seven new rows and two grown deletion counts,
all of them the app rename, each listed with what moves and why it could not be an insertion.
Renaming the app is not expressible as an append: `T3 Code` has to stop being the name, and every
one of those literals already exists in an upstream file. Five of the nine rows are tests, which
is the cheap half — a fixture upstream also edits conflicts loudly and resolves by reading two
lines. The four source rows are one string literal each, which is the floor for a rename, and is
why `T3 Coil (Alpha)` was chosen over an unsuffixed `T3 Coil`: dropping the stage label would have
meant restructuring resolveDesktopAppBranding instead of replacing a constant.
Also records what was declined — 31 more upstream files carry `T3 Code` in body copy, and renaming
them would nearly double the ledger to buy prose consistency.
The mac-signing runbook carried a "`productName` stays `T3 Code (Alpha)`" note that this issue
invalidates. Replaced rather than deleted: the hazard it described is real, it was accepted rather
than avoided, and the note now says so and points at the one-time manual install. Its #71 entry
moves from a warning to the sequence that was actually followed. The two `codesign` transcripts
that still show the old name are historical output and stay as they are.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Copy file name to clipboardExpand all lines: docs/coil/SEAMS.md
+43-15Lines changed: 43 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,17 @@
1
-
# t3x seam ledger
1
+
# coil seam ledger
2
2
3
3
**The authoritative list of every upstream-owned file this fork edits.**
4
4
5
-
Measured, not asserted: **40 upstream-owned files, +2197 / -1047 lines**, against merge-base
6
-
`78f462c4e` (upstream v0.0.33, the 2026-08-10 sync). The only deletion added since the
7
-
2026-08-10 baseline is `scripts/build-desktop-artifact.ts` (row 38) — one line for #70, deliberately shaped as
8
-
an env escape hatch so upstream's default and its tests survive it. Rows 39 and 40 (`README.md`,
9
-
`docs/user/install.md`, #72) are pure insertions above upstream's own text. The −134 that #58 added
10
-
on 2026-08-11 are **all**`pnpm-lock.yaml`, the one row the additive invariant below has never
11
-
covered because it is regenerated rather than merged. Everything else the fork adds lives in new
5
+
Measured, not asserted: **PLACEHOLDER_FILES upstream-owned files, +PLACEHOLDER_ADD / -PLACEHOLDER_DEL lines**, against merge-base
6
+
`78f462c4e` (upstream v0.0.33, the 2026-08-10 sync). Everything else the fork adds lives in new
12
7
files upstream has never seen and cannot conflict.
13
8
9
+
> **Re-baselined 2026-08-12 for #71**, which renamed the fork's identity from `t3x` to `coil` and
10
+
> the app from `T3 Code (Alpha)` to `T3 Coil (Alpha)`. The directory and symbol renames cost
11
+
> nothing here — they move fork-owned files, and the fork-added lines inside upstream files change
12
+
> content without changing count. The app rename is what moved these numbers: **7 new rows and 2
13
+
> grown deletion counts**, argued for below.
14
+
14
15
> **Corrected 2026-08-11 (#40).** The header read +1968 while the regeneration recipe below returned
15
16
> +1981 against the same `origin/main` — a 13-line drift in the `pnpm-lock.yaml` row (see its own
16
17
> note). The drift is persistent, not new: it was +1957 against a recipe run of +1970 before #70 landed,
@@ -30,6 +31,33 @@ files upstream has never seen and cannot conflict.
30
31
> file, and the invariant above weakens from "no deletions anywhere" to "one known deletion, at a known
31
32
> line". Keep it that way. The additive rule is what makes a clean rebase evidence of anything, so a
32
33
> second displacement should have to argue for itself in this file the way that one did.
34
+
>
35
+
> **2026-08-12 (#71): the argument for the second set.** Renaming the app is not expressible as an
36
+
> insertion. `T3 Code` has to stop being the name, and every one of these is a literal that already
37
+
> exists in an upstream file, so each is a replacement:
38
+
>
39
+
> | File || What moves |
40
+
> | --- | --- | --- |
41
+
> |`apps/desktop/src/app/DesktopEnvironment.ts`| +9/-1 |`APP_BASE_NAME`. The only one that really matters — `displayName` is derived from it and reaches `app.setName()`, the About panel, window titles, the Linux `.desktop` entry, and the whole web UI through `getAppBranding()`. The other 8 lines are a comment explaining why `legacyUserDataDirName` two lines below must NOT follow it |
42
+
> |`apps/desktop/package.json`| -1 → -2 |`productName`, the `.app` bundle name |
43
+
> |`apps/desktop/scripts/electron-launcher.mjs`| +1/-1 | the dev-mode display name |
44
+
> |`apps/web/src/branding.ts`| +1/-1 | the browser-only fallback, used when no desktop branding is injected |
45
+
> |`apps/web/index.html`| -0 → -1 | the boot `<title>`|
46
+
> |`apps/desktop/src/app/DesktopAppIdentity.test.ts`| +5/-2 | asserts the new name AND keeps the legacy-userData assertions on the old one |
47
+
> |`apps/web/src/branding.test.ts`| +14/-11 | fixtures, minus the injected-branding case which deliberately keeps `T3 Code`|
0 commit comments