fix: add missing TCC resource-access entitlements and usage strings

[skkap]

Fixes #396. Same mechanism as #142, one layer down: that was a missing usage string, these are missing hardened-runtime entitlements.

agterm is signed with hardened runtime, under which Apple gates seven resource-access entitlements. agterm carried one (device.audio-input). For the other six, tccd refuses to prompt and records nothing — so a tool run inside a session cannot obtain the permission, and the user cannot grant it by hand either, because with no TCC record agterm never appears in the relevant Privacy & Security pane. Grants agterm already holds keep working, which is why this went unnoticed: only new grants are impossible.

Changes

agterm/agterm.entitlements — the six missing resource-access entitlements:

automation.apple-events   device.camera   personal-information.addressbook
personal-information.calendars   personal-information.location   personal-information.photos-library

agterm/Info.plist — usage strings for the services with a real command-line path, worded to match the existing microphone string: AppleEvents, Camera, Contacts, Calendars (+ full-access, + write-only), Reminders (+ full-access), PhotoLibrary, Location, Bluetooth, LocalNetwork, SpeechRecognition.

Every key was checked against Apple's documented platform availability rather than copied from other terminals — that caught three keys iTerm2/Ghostty/kitty ship which are iOS/iPadOS/visionOS only and do nothing on macOS (NSLocationWhenInUseUsageDescription, NSLocationAlwaysAndWhenInUseUsageDescription, NSPhotoLibraryAddUsageDescription). The macOS key is NSLocationUsageDescription — 10.14+, not deprecated there.

The deprecated NSCalendarsUsageDescription / NSRemindersUsageDescription are kept deliberately. Both are deprecated at macOS 14, but agterm is the responsible app for third-party tools of unknown SDK vintage, and one linked against a pre-14 SDK still resolves against the legacy key.

project.yml — the reseal applied --deep --entitlements, which stamped the app's entitlement set onto the bundled agtermctl, a standalone CLI on the user's PATH. Measured before the fix, the helper carried all six TCC entitlements. Now --deep signs without entitlements and a second non-deep pass applies them to the app alone. Shipped artifacts were never affected — release.sh re-signs the helper itself — only make build / make deploy output.

Verification

Each service was exercised from a CLI inside agterm 0.20.2 / macOS 26.5.2, against the released build — the failures this PR fixes, reproduced per service:

Service	Result	tccd
Apple Events	-1743, no prompt	kTCCServiceAppleEvents requires entitlement …automation.apple-events but it is missing
Camera	denied	kTCCServiceCamera requires …device.camera…
Contacts	denied	kTCCServiceAddressBook requires …addressbook…
Calendars	denied	kTCCServiceCalendar requires …calendars…
Photos	denied	kTCCServicePhotos requires …photos-library…
Location	notDetermined, no prompt	none — handled by locationd, not tccd

All carry promptPolicy = 4 and responsible={com.umputun.agterm}.

That the entitlements are the cure was then shown with two minimal apps identical except for the entitlements passed to codesign — same binary, same usage strings, both flags=0x10002(adhoc,runtime), distinct bundle ids:

	no entitlements	with entitlements
Apple Events	-1743, no prompt	prompt → granted
Camera	denied, no prompt	prompt → granted
Location	notDetermined	prompt → authorizedAlways

tccd un-entitled: Policy disallows prompt … denied. Entitled: AUTHREQ_PROMPTING, all three dialogs confirmed on screen. This also settles location, which produces no tccd line of its own.

Build: make build and the signing phase pass from an empty DerivedData, with agtermctl carrying no entitlements, the app all six, and codesign --verify --deep --strict clean.

✅ Resolved — NSSystemAdministrationUsageDescription

Decision reached and addressed. Approved in review; the key is in the diff as of b5f641c. The
follow-up asked alongside it — whether a missing purpose string terminates the process rather than
denying — was checked: it denies. Details in the review thread.

Original question kept below for the record.

I think this should go in, and I'd like to add it. It is not in the diff because you asked me to leave it out, and I'm not going to include it over that without checking first — but I don't think the reason it was excluded holds up:

1. The exclusion tested a different subsystem. It was ruled out because CLIInstaller.elevatedSymlink already elevates without it. That path is do shell script … with administrator privileges — Authorization Services, not TCC. This key gates a TCC service, so the installer working says nothing either way about it.
2. Apple documents it as macOS-only and required. macOS 10.14+, not deprecated: "A message in macOS that tells people why the app is requesting to manipulate the system configuration", "This key is required if your app uses APIs that manipulate the system configuration", naming ODRecordSetValue — the OpenDirectory API behind dscl. A tool running dscl . -create in a session lands exactly here, with agterm responsible.
3. It is the same class as every other key here, and all three peers ship it. Leaving this one out makes agterm the lone outlier for no mechanical reason, and the failure mode is the silent one this whole PR exists to remove.

One word and I'll push it.

Still deliberately out of scope: the Files & Folders family (NSDesktopFolderUsageDescription and friends). Those prompts already work — the keys would only replace Apple's generic wording with agterm's — so that is a copy improvement, not a fix, and belongs in its own change.

✅ Resolved — local make test-app failure

Decision reached and addressed. Already fixed on master by 16d8cbc; this branch is rebased onto it
and make test-app is green. The diagnosis below was wrong — see #400, which is closed as redundant.

Original note kept below for the record.

make test-app fails locally on LiveMenuKeyEquivalentsTests.testUppercaseKeyEquivalentReportsImpliedShift(), on unmodified master too. Unrelated to this PR and fixed separately in #400 — the fixture uses the title "Paste and Match Style", which AppKit recognises as a standard item and rewrites to ⇧⌘V on addItem, before the code under test runs.

[umputun]

add it.

your read on the exclusion is right: the CLI installer path is do shell script ... with administrator privileges, which is Authorization Services, not TCC, so it says nothing about NSSystemAdministrationUsageDescription either way. And dscl . -create in a session is exactly the "real command-line path" test the other strings pass, so leaving this one out is the outlier.

one thing worth checking while you have the scratch apps out: this key has no hardened-runtime entitlement behind it, unlike the six in the diff. If a TCC service that requires a purpose string and has none terminates the touching process instead of denying it, the failure mode here is the tool dying rather than the silent deny the rest of this PR fixes. I have not verified that, so treat it as a guess until you check.

push it and I'll merge.

[skkap]

Rebased on master — you were right about #400, I should have pulled first.

✅ Decision reached and addressed — NSSystemAdministrationUsageDescription

Added in b5f641c, worded to match the rest:

Command-line tools you run inside agterm (for example, dscl editing a directory record) request permission to change system configuration through agterm.

✅ Decision reached and addressed — missing purpose string

Checked it with the scratch apps: it denies, it does not terminate. Same binary in two bundles differing only in the usage string — the stringed one prompts and is granted, the string-less one gets a plain "Access Denied" and runs to completion with no crash. So the failure mode here is the same silent deny as the rest of this PR, not a dying tool. Full measurements on request.

Two limits, since you asked me to treat it as a guess until checked: I could not drive the SysAdmin service itself to a TCC decision — OpenDirectory rejects the write on credentials before TCC is consulted — and the behaviour may vary by framework. So that result is measured for Contacts and expected, not verified, for the rest.

Gates

Clean on the rebase: swift test 2411 tests, make test-app 176 tests, swiftlint --strict 0 violations.

Description

Both open items are marked ✅ Resolved with what was decided and where it landed, originals kept struck through.

[umputun]

lgtm