v0.3.1 — full Mac Office coverage + CI

Builds on v0.3.0's cross-platform foundation: Word, PowerPoint, and Outlook now have Mac AppleScript backends matching Excel.Mac. Plus GitHub Actions CI validating the multi-target architecture, plus a comprehensive LLM-docs sweep covering everything macOS.

New Mac plugins

• ComBridge.Plugins.Word.Mac — combridge word info, extract-text, doc-stats
• ComBridge.Plugins.PowerPoint.Mac — combridge powerpoint info, list-slides
• ComBridge.Plugins.Outlook.Mac — combridge outlook info, list-accounts (limited dictionary documented)

All four Mac plugins share ComBridge.Mac.Common (the Osascript helper). A single combridge bundle now ships 9 plugin folders side-by-side; the OS filter picks the right ones at load time.

Same CLI on both OSes

# These work the same on Windows and macOS — different plugin loads under the hood:
combridge word info -
combridge powerpoint list-slides -
combridge outlook list-accounts -
combridge excel dump-sheet Sheet1 -

CI

.github/workflows/build.yml runs on every push to main + every PR. Two jobs:

• macOS runner — builds Core (net10.0 TFM), CLI (net10.0 TFM), Mac.Common, all 4 Mac plugins; smoke-tests combridge list-plugins.
• Windows runner — builds Core (both TFMs), CLI (both TFMs), all Mac plugins (proves cross-platform compile).

Windows plugins needing installed Office/SOLIDWORKS are NOT in CI — those need developer machines with the apps installed; COMBRIDGE001 validation surfaces missing interop at build time anyway.

Documentation

• LLM/plugins.md § macOS plugins — per-plugin specifics + what differs vs Windows
• LLM/authoring.md § macOS plugin pattern — drop-in skeleton + other Mac-scriptable apps to consider
• LLM/troubleshooting.md § macOS / AppleScript issues — TCC, slow loops, name typos, New Outlook for Mac
• LLM/build.md — Mac build commands + per-OS plugin availability matrix

Mac side still not live-tested

The four Mac plugins compile cleanly on Windows but cannot be functionally tested without a Mac. Expect AppleScript quirks to surface on first real run; troubleshooting.md captures the failure modes I anticipate based on the AppleScript / TCC / Office for Mac knowledge baked into Claude's training data. First Mac tester gets to fill in the gaps.