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 8284830
Browse filesBrowse the repository at this point in the historyBrowse files
authored and
coil-sync-bot
committed
style(coil): format the files this rename touched (#71)
Prettier only. The renamed directories carried pre-existing formatting drift with them, so this is
scoped to the files whose formatting this branch actually changed — verified by control-running
`vp fmt --check` on origin/main and diffing the two lists with paths normalised across the rename,
rather than reformatting everything and burying the review.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
| Name |**Coil**| A coil is both a curl and a loop, tying the Curly Cloud handle to the roadmap in four letters. `Cirrus` was the near-miss — Latin for "a curl", and a cloud type — but Cirrus CI is an established dev-tooling brand and this is a dev tool. |
21
21
| Voice | First person singular | "We" and "the community" describe a project that does not exist. One person builds this. |
22
-
| Loops on the page | Roadmap section, tagged `planned`| Loops lead the _direction_, not the feature list. Nothing loop-related has shipped: `docs/coil/loop/` is design-only, archived in `67fb23e81` when its branch was deleted. |
22
+
| Loops on the page | Roadmap section, tagged `planned`| Loops lead the _direction_, not the feature list. Nothing loop-related has shipped: `docs/coil/loop/` is design-only, archived in `67fb23e81` when its branch was deleted. |
23
23
| Page spine | Two plain sections | "What's here today" and "Where this is going". The fork graph is retired. |
24
24
| Long-term vision | Plain language, no jargon | "Forward deployed engineer" is precise for the few and opaque to everyone else. |
25
25
| Domain |`coil.curlycloud.dev`| The product is Coil, so `t3.` would be stale on arrival. |
| First renamed build | One-time manual install; the updater's refusal is reworded, not bypassed|
21
+
| Relay |`coil-update-relay` becomes authoritative; `t3x-update-relay` stays deployed as a proxy |
22
+
| GitHub secrets and repo variables | Keep the `T3X_` prefix |
23
23
24
24
Two of these have a cost that is paid by the user rather than by CI, and both are worth restating
25
25
because neither is recoverable by editing code after the fact.
26
26
27
27
**The bundle id and the certificate each cost one full round of macOS permission dialogs.** macOS
28
28
keys TCC grants — Screen Recording, Accessibility, Files & Folders — on the pair
29
-
`(service, bundle id)`, and the *designated requirement* that authenticates the app names both the
29
+
`(service, bundle id)`, and the _designated requirement_ that authenticates the app names both the
30
30
bundle id and the signing certificate. Changing either invalidates every existing grant. Changing
31
31
both at once costs one round of prompts, not two, which is the only reason to do them together.
32
32
This is the second such reset in a week (PR #85 was the first), and it should be the last: both
@@ -59,7 +59,7 @@ publish build 1, every installed client would evaluate `1 <= 26`, and all of the
59
59
forever. There is no error surface for this: skipping is the normal, expected outcome of that
60
60
branch, so it looks exactly like being up to date.
61
61
62
-
Issue #71 names this hazard but attributes it to the *version string*, and concludes the suffix
62
+
Issue #71 names this hazard but attributes it to the _version string_, and concludes the suffix
63
63
change is safe because the updater never compares versions. Both halves of that are true and
64
64
neither is the risk. The risk is the filename.
65
65
@@ -106,7 +106,7 @@ costs the same handful of lines.
106
106
107
107
**Verification before cutover, against a real old build.** The `T3X_UPDATE_RELAY_URL` override does
108
108
work when the `.app` is launched from a terminal rather than Finder, which makes it possible to
109
-
point the *currently installed* build at a throwaway shim and confirm both `/latest` and `/events`
109
+
point the _currently installed_ build at a throwaway shim and confirm both `/latest` and `/events`
110
110
behave. That is the only test that proves anything about clients in the field, so it is a gate on
111
111
the relay cutover rather than a nice-to-have.
112
112
@@ -134,7 +134,7 @@ script path moved, and a regenerated plist and an unchanged script agree by cons
134
134
the variables as well would have created a window where a hand-edited plist sets names the script
135
135
no longer reads, silently reverting to defaults for the build worktree and the applications
136
136
directory. The state files it writes (`<state-dir>/coil-autobuild-last-sha` and
137
-
`coil-autobuild-status.json`) *do* move, because losing them costs exactly one redundant rebuild.
137
+
`coil-autobuild-status.json`) _do_ move, because losing them costs exactly one redundant rebuild.
138
138
139
139
### 4. `app.setName()` sets a Keychain service name
140
140
@@ -148,7 +148,7 @@ Threads, settings and sessions are **not** affected, and this is worth stating p
148
148
adjacent literals look like they should be. `userDataDirName = "t3code"` and
149
149
`legacyUserDataDirName = "T3 Code (Alpha)"`(`DesktopEnvironment.ts:171-172`) are hardcoded, not
150
150
derived from `displayName` or from the bundle id. That is why PR #85 moved nobody's threads, and it
151
-
is why this rename does not either. Renaming *those* would orphan every thread and is out of scope.
151
+
is why this rename does not either. Renaming _those_ would orphan every thread and is out of scope.
152
152
153
153
**Resolution.** Accept the re-encrypt, but make it legible: the decode path is verified to degrade
154
154
to a per-environment "re-enter this token" state rather than an error or an empty list. No
@@ -157,13 +157,13 @@ choice is whether the user finds out from a clear prompt or from a confusing fai
157
157
158
158
## What is deliberately not renamed
159
159
160
-
| Kept | Why |
161
-
|---|---|
162
-
| `userDataDirName` / `legacyUserDataDirName` | Renaming orphans every thread, setting and session |
163
-
| GitHub secrets and repo variables (`T3X_*`) | Invisible to users and to macOS; renaming opens a window between merge and re-setting them where the release is broken, for no gain |
164
-
| `~/.t3x/mac-signing`, `t3x-signing.keychain` | Local paths on one machine; moving them adds a manual step to an already manual certificate rotation |
165
-
| `t3codeCommitHash`, `@t3tools/*`, `T3CODE_*` | Upstream's identity, not the fork's |
166
-
| `apps/marketing/` | Untouched by design — see SEAMS.md's parallel-path note |
| `userDataDirName` / `legacyUserDataDirName` | Renaming orphans every thread, setting and session |
163
+
| GitHub secrets and repo variables (`T3X_*`) | Invisible to users and to macOS; renaming opens a window between merge and re-setting them where the release is broken, for no gain |
164
+
| `~/.t3x/mac-signing`, `t3x-signing.keychain` | Local paths on one machine; moving them adds a manual step to an already manual certificate rotation |
165
+
| `t3codeCommitHash`, `@t3tools/*`, `T3CODE_*` | Upstream's identity, not the fork's |
166
+
| `apps/marketing/` | Untouched by design — see SEAMS.md's parallel-path note |
167
167
168
168
## Seam impact
169
169
@@ -190,7 +190,7 @@ rolled back by reverting a commit.
0 commit comments