The bundle-ID and display-name renames weren't enough — the actual Xcode target/product name was still "Jarvis", which drives CFBundleName, Xcode's Organizer archive list, the .xcodeproj filename, and the scheme name. Renamed all the way through: - project.yml: top-level name, target key, PRODUCT_NAME, source/info paths - Jarvis/ -> Jervis/ (source folder, git-tracked as renames, no content diffs on the moved files) - .gitignore, CI workflows, README, CONTRIBUTING: Jarvis.xcodeproj / scheme Jarvis -> Jervis.xcodeproj / scheme Jervis Verified: xcodebuild -scheme Jervis succeeds, produces Jervis.app, CFBundleName/CFBundleExecutable/CFBundleDisplayName all read "Jervis". CFBundleIdentifier intentionally stays com.kisani.jarvis (per prior decision — bundle ID isn't user-facing anywhere including Organizer). Swift type names (JarvisApp, JarvisWordmark, etc.) and the Gitea repo name/URL are unchanged — pure internal source identifiers, not user or developer-facing product identity. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
39 lines
689 B
JSON
39 lines
689 B
JSON
{
|
|
"colors" : [
|
|
{
|
|
"color" : {
|
|
"color-space" : "srgb",
|
|
"components" : {
|
|
"alpha" : "1.000",
|
|
"blue" : "0x00",
|
|
"green" : "0x5C",
|
|
"red" : "0xFF"
|
|
}
|
|
},
|
|
"idiom" : "universal"
|
|
},
|
|
{
|
|
"appearances" : [
|
|
{
|
|
"appearance" : "luminosity",
|
|
"value" : "dark"
|
|
}
|
|
],
|
|
"color" : {
|
|
"color-space" : "srgb",
|
|
"components" : {
|
|
"alpha" : "1.000",
|
|
"blue" : "0x00",
|
|
"green" : "0x5C",
|
|
"red" : "0xFF"
|
|
}
|
|
},
|
|
"idiom" : "universal"
|
|
}
|
|
],
|
|
"info" : {
|
|
"author" : "xcode",
|
|
"version" : 1
|
|
}
|
|
}
|