Current Status
There is no Purchases CLI command group and no CLI entitlement workflow.
Purchases are intentionally GUI-owned today because StoreKit purchase, restore, and entitlement presentation belong in the native macOS app. The CLI can run project, Firestore, Auth, and Storage workflows, but it should not present itself as a purchase surface or a way to avoid paid feature gates.
Current CLI Implication
The CLI currently exposes project/module selection and Firestore query/create/update/delete. It does not yet document or enforce the full GUI StoreKit purchase flow.
Before broadening CLI mutation coverage, CLI Pro enforcement should be designed explicitly so command-line automation cannot bypass GUI access rules.
For internal testing, treat CLI mutation access as an implementation detail rather than a product entitlement promise. Any public automation path that creates, updates, deletes, imports, exports, transfers, uploads, deploys, runs scripts, sends push notifications, applies seeds, or applies migrations should respect the same commercial and safety boundaries shown in the app.
Support conversations should direct users to the Purchases and Pro Access GUI article for plan details, restore behavior, and paywall expectations. CLI scripts can still be documented for read-only inspection and emulator-safe workflows, but the purchase decision and restore state should remain clear to the user before paid actions begin.
Future CLI Shape
Expected future commands:
pro status
pro restore
StoreKit purchase itself is likely to remain GUI-native.
Source Anchors
Sources/FirestructApp/Features/Purchases/Model/ProAccessState.swiftSources/FirestructApp/Features/Purchases/Services/AppModel+Purchases.swift