Adopt LumaControl bundle identity and start the 1.0.0 line

[shay2000]

What

Completes the LumaControl migration. The visible rename (README, UI strings, all localization files, install script, repo name, appcast) already landed in 542e00c / v0.3.0. What remained was the internal identity:

	Before	After
App bundle ID	com.shay2000.XDRMonitorControl	com.shay2000.LumaControl
Helper bundle ID	com.shay2000.XDRMonitorControlHelper	com.shay2000.LumaControlHelper
Tests bundle ID	com.shay2000.XDRMonitorControlTests	com.shay2000.LumaControlTests
Marketing version	0.3.0	1.0.0
Build number	39	1

The Helper suffix is load-bearing: MonitorControlHelper/main.swift strips "Helper" off its own bundle ID to find the app, and AppDelegate appends it when registering the login item. Both keep working with no code change.

Verified

xcodebuild test — TEST SUCCEEDED, 14/14. The built app reports com.shay2000.LumaControl / 1.0.0, with the helper embedded at Contents/Library/LoginItems/MonitorControlHelper.app and identifying as com.shay2000.LumaControlHelper.

Deliberately not changed

• SUPublicEDKey — rotating it would permanently break Sparkle updates for every installed copy.
• SUFeedURL — already points at shay2000/LumaControl.
• MIT copyright and attribution in License.txt and NSHumanReadableCopyright — required by the license.
• Dated historical records (HANDOFF.md, build14-changes.html, build21-permissions.html) and the comment in SettingsPanesTests.swift — these describe the app by the name it actually had at the time; rewriting them would falsify the record.

Reviewer notes

• 29 inherited upstream release tags (v1.0 … v4.3.3) were deleted locally. They were never pushed, so origin is unaffected and still carries only v0.1.0, v0.2.0, v0.3.0.
• Follow-up handled after merge, not in this diff: the Accessibility grant and the SMLoginItemSetEnabled login item must be re-established under the new bundle ID, and saved preferences move to the new defaults domain.

[greptile-apps]

Greptile Summary

Updates the application, helper, and test bundle identifiers to the LumaControl identity and begins the 1.0.0 marketing-version line.

• Changes app identity to com.shay2000.LumaControl.
• Preserves the helper’s required Helper suffix and aligns test identity.
• Sets both app and helper build numbers to 45, maintaining Sparkle’s monotonic version ordering.
• Updates issue templates to request LumaControl v1.0.0 environment details.

Confidence Score: 5/5

The PR appears safe to merge because the bundle identities are consistently updated and the corrected build number preserves Sparkle update ordering.

No actionable new issue remains. The previous build-number thread was manually resolved without an explanatory reply, and the current value of 45 fully fixes the reported regression by remaining above published build 39.

Important Files Changed

Filename	Overview
MonitorControl.xcodeproj/project.pbxproj	Updates app, helper, and test bundle identifiers and sets app and helper marketing versions to 1.0.0.
MonitorControl/Info.plist	Raises the application build number to 45, preserving update ordering.
MonitorControlHelper/Info.plist	Keeps the helper build number aligned with the application at 45.
.github/ISSUE_TEMPLATE/bug_report.yml	Updates the example reported application version to v1.0.0.
.github/ISSUE_TEMPLATE/monitor-issue.yml	Updates the monitor issue template’s example application version to v1.0.0.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  App["LumaControl.app<br/>com.shay2000.LumaControl<br/>1.0.0 (45)"]
  Helper["MonitorControlHelper.app<br/>com.shay2000.LumaControlHelper<br/>1.0.0 (45)"]
  Tests["MonitorControlTests<br/>com.shay2000.LumaControlTests"]
  App -->|registers login item by appending Helper| Helper
  Helper -->|locates app by removing Helper| App
  Tests -->|tests| App

Loading

_{Reviews (2): Last reviewed commit: "Keep CFBundleVersion above every publish..." | Re-trigger Greptile}

[shay2000]

Fixed in 3878bd1 — raised CFBundleVersion to 45 on both the app and the helper.

Greptile suggested 40, which is correct against the published build 39. I went to 45 because the local dev install is build 44, so anything ≤ 44 would still compare as not-newer and Sparkle would skip it. MARKETING_VERSION stays 1.0.0, so this is still version 1 as far as the tag and the UI are concerned.