Current Status
There is no first-class Seed Studio command group in the current CLI implementation.
Seed generation and apply flows currently belong to the macOS module because users need to review generated data, snapshots, drift output, target project/database labels, and overwrite behavior before writes occur. This page documents the expected future command shape without implying that terminal seed execution exists today.
GUI-Only Coverage Today
Use the macOS Seed Studio module for:
- schema/template editing
- deterministic seed generation
- snapshot review
- seed apply
- drift comparison
The GUI workflow is the supported place to choose a deterministic seed, inspect generated Firestore document paths, compare snapshot values against current project data, and decide whether applying the seed is appropriate. That review step matters for emulator setup and is mandatory for production-like targets.
When preparing future CLI automation, keep the template, deterministic seed options, expected output path, target project, target database, and confirmation requirements together. A CLI should generate and diff safely before it applies, and any apply command must expose overwrite behavior and route longer work through Tasks.
Future CLI Shape
Expected future commands:
seed generate --template seed.json --output snapshot.json
seed apply --snapshot snapshot.json --confirm
seed diff --snapshot snapshot.json
Source Anchors
Sources/FirestructCore/SeedStudioService.swiftSources/FirestructCore/SeedStudioService+GenerationUtilities.swift