[fredsimard]

Closes #7.

What

Adds an .osType return type for the properties that are documented as enumerations and cannot answer with anything else — a disk's format in the Finder, a range's format in Numbers. .wildCard already reached those as AppleScriptValue.constant, but the caller had to switch on a type they already knew to get at the code. .osType declares it up front and the raw FourCharCode comes back directly:

let code = try AppleScriptBridge.executeAppleScript(diskFormat, with: ["diskName": "Macintosh HD"]) as? FourCharCode

if code == "dfap".appleScriptFourCharCode { … }

The open question in #7

Settled on the raw FourCharCode, not a mapping to dictionary terms. The terminology lives in each application's sdef, which the package has no access to at the point where a result is decoded, so a mapping would mean shipping per-application tables or asking the caller to supply one — and a caller who can supply the table can already compare against the codes in it. String.appleScriptFourCharCode and String(appleScriptFourCharCode:) cover the ergonomics, and the result stays the same shape as .wildCard's .constant, so moving between the two return types is a cast, not a rewrite.

Behaviour

What the script answered	What comes back
A constant ('enum', 'type', 'prop', 'keyw')	Its FourCharCode, raw.
missing value	The code 'msng', comparable against FourCharCode(cMissingValue). Not singled out as it is in AppleScriptValue.
Text of exactly four characters, or a boolean	The code it coerces to — a boolean is 'true' or 'fals' underneath.
Anything else — a number, a date, a list, longer text	nil, rather than a code read out of unrelated bytes, which is what enumCodeValue hands over on its own.

Like .wildCard, .osType needs the Apple event descriptor, so executeAppleScriptViaCommandLine(_:with:) throws .unsupportedReturnType before launching the process: osascript prints the term its dictionary defines, APFS format, with the code nowhere in it.

Upgrade note

AppleScriptReturnType gained a case, so code that switches over it exhaustively without a default stops compiling until .osType is handled. Nothing else changes.

Tests

Ten new tests in OSTypeTests.swift: the four constant-carrying descriptor types, missing value, the coercible descriptors, the non-constant ones, two execution suites running self-contained scripts through NSAppleScript (no Automation permission needed), and the command-line refusal. swift build, swift test (53 tests) and the CI-style example build pass locally; SwiftLint is not installed on this machine, so the lint job is unverified here.

Docs updated: README, Documentation/API.md, Examples/AppleScripts.swift (an .osType script and its call site next to the .wildCard ones), and a 1.3.0 CHANGELOG entry.

🤖 Generated with Claude Code