switch to wetrun

Author: ryanatkn

.changeset/odd-seas-give.md

@@ -0,0 +1,5 @@
+---
+'@fuzdev/fuz_gitops': minor
+---
+
+switch to `wetrun`

CLAUDE.md

@@ -63,7 +63,7 @@ Publishing uses fixed-point iteration to handle transitive dependency updates:
 - Auto-changesets trigger republishing in subsequent passes (transitive
   cascades)
 - Stops when no new changesets are created (converged state)
-- Single `gro gitops_publish` command handles full dependency cascades
+- Single `gro gitops_publish --wetrun` command handles full dependency cascades
 - If MAX_ITERATIONS reached without convergence, warns with pending package
   count and estimated iterations needed
 
@@ -145,13 +145,13 @@ Requires `SECRET_GITHUB_API_TOKEN` in `.env` for API access.
 
 #### Publishing Workflow
 
-- `gro gitops_publish` - publishes repos in dependency order
+- `gro gitops_publish --wetrun` - publishes repos in dependency order
   - Uses fixed-point iteration to handle transitive dependency updates
   - Converges after multiple passes (max 10 iterations)
   - Creates auto-changesets for dependent packages during publishing
 - `gro gitops_plan` - generates a publishing plan (read-only prediction)
 - `gro gitops_analyze` - analyzes dependencies and changesets
-- `gro gitops_publish --dry_run` - simulates publishing without preflight checks
+- `gro gitops_publish` - simulates publishing (dry run) without preflight checks
   or state persistence
 - Handles circular dev dependencies by excluding from topological sort
 - Waits for NPM propagation with exponential backoff (10 minute default
@@ -162,7 +162,7 @@ Requires `SECRET_GITHUB_API_TOKEN` in `.env` for API access.
     publishing dependents
 - Updates cross-repo dependencies automatically
 - Preflight checks validate clean workspaces, branches, builds, and npm
-  authentication (skipped for --dry_run runs)
+  authentication (skipped for dry runs)
 
 **Build Validation (Fail-Fast Safety)**
 
@@ -218,7 +218,7 @@ The publishing workflow automatically installs dependencies after package.json u
   auto-generated changesets, and no changes
 - No side effects - does not modify any files or state
 
-`gro gitops_publish --dry_run`:
+`gro gitops_publish` (dry run, default):
 
 - **Simulated execution** - Runs the same code path as real publishing
 - Skips preflight checks (workspace, branch, npm auth)
@@ -324,14 +324,14 @@ gro gitops_run "npm audit" --concurrency 3  # limit parallelism
 gro gitops_run "gro check" --format json    # JSON output for scripting
 
 # Publishing
-gro gitops_validate          # validate configuration (runs analyze, plan, and dry run)
-gro gitops_analyze           # analyze dependencies and changesets
-gro gitops_plan              # generate publishing plan
-gro gitops_plan --verbose    # show additional details
-gro gitops_publish           # publish repos in dependency order (interactive y/n prompt)
-gro gitops_publish --dry_run # dry run without preflight checks
-gro gitops_publish --no-plan # skip interactive plan confirmation
-gro gitops_publish --verbose # show additional details in plan
+gro gitops_validate              # validate configuration (runs analyze, plan, and dry run)
+gro gitops_analyze               # analyze dependencies and changesets
+gro gitops_plan                  # generate publishing plan
+gro gitops_plan --verbose        # show additional details
+gro gitops_publish               # dry run (default, simulates publishing)
+gro gitops_publish --wetrun      # actually publish repos in dependency order
+gro gitops_publish --wetrun --no-plan # skip interactive plan confirmation
+gro gitops_publish --verbose     # show additional details in plan
 
 # Output formats (analyze, plan, publish)
 gro gitops_analyze --format json --outfile analysis.json
@@ -355,7 +355,7 @@ gro test src/test/fixtures/check     # validate gitops commands against fixture
 - `gro gitops_plan` - Generate publishing plan showing version changes and
   cascades
 - `gro gitops_validate` - Run all validation checks (analyze + plan + dry run)
-- `gro gitops_publish --dry_run` - Simulate publishing without preflight checks
+- `gro gitops_publish` - Simulate publishing without preflight checks (dry run default)
 
 **Data Sync (Local Changes Only):**
 
@@ -376,13 +376,13 @@ gro test src/test/fixtures/check     # validate gitops commands against fixture
 
 **Publishing (Git & NPM Side Effects):**
 
-- `gro gitops_publish` - Publish packages, update dependencies, git commits
+- `gro gitops_publish --wetrun` - Publish packages, update dependencies, git commits
 
 ### Command Workflow
 
 - `gitops_validate` runs: `gitops_analyze` + `gitops_plan` +
-  `gitops_publish --dry_run`
-- `gitops_publish` runs: `gitops_plan` (with confirmation) + actual publish
+  `gitops_publish` (dry run)
+- `gitops_publish --wetrun` runs: `gitops_plan` (with confirmation) + actual publish
 
 ## Dependencies
 

README.md

@@ -96,17 +96,17 @@ gro gitops_sync --download    # clone missing repos first
 ### Diagnostic commands (read-only)
 
 ```bash
-gro gitops_validate      # run all validation checks (analyze + plan + dry run)
-gro gitops_analyze       # analyze dependency graph and detect cycles
-gro gitops_plan          # generate publishing plan showing version changes and cascades
-gro gitops_publish --dry_run # simulate publishing without side effects
+gro gitops_validate   # run all validation checks (analyze + plan + dry run)
+gro gitops_analyze    # analyze dependency graph and detect cycles
+gro gitops_plan       # generate publishing plan showing version changes and cascades
+gro gitops_publish    # simulate publishing without side effects (dry run default)
 ```
 
 ### Publishing packages
 
 ```bash
-gro gitops_publish  # publish all repos with changesets (interactive y/n prompt)
-gro gitops_publish --no-plan  # skip plan confirmation
+gro gitops_publish --wetrun  # actually publish all repos with changesets
+gro gitops_publish --wetrun --no-plan  # skip plan confirmation
 ```
 
 **Note:** If publishing fails, simply re-run the same command. Already-published packages are automatically skipped (changesets consumed), failed packages retried naturally.

docs/publishing.md

@@ -22,8 +22,8 @@ gro gitops_validate
 # 2. Review what will be published
 gro gitops_plan
 
-# 3. Publish
-gro gitops_publish
+# 3. Publish (after dry run looks good)
+gro gitops_publish --wetrun
 ```
 
 ## Changeset Semantics
@@ -84,7 +84,7 @@ production/peer takes priority for dependency graph calculations.
   auto-generated changesets, and no changes
 - No side effects - does not modify any files or state
 
-### `gro gitops_publish --dry_run`
+### `gro gitops_publish` (dry run, default)
 
 - **Simulated execution** - Runs the same code path as real publishing
 - Skips preflight checks (workspace, branch, npm auth)
@@ -164,11 +164,11 @@ gro gitops_analyze
 # 3. Review plan to see what will be published
 gro gitops_plan
 
-# 4. Test with dry run
-gro gitops_publish --dry_run
-
-# 5. If everything looks good, publish
+# 4. Test with dry run (default)
 gro gitops_publish
+
+# 5. If everything looks good, actually publish
+gro gitops_publish --wetrun
 ```
 
 ### Output Formats
@@ -195,7 +195,7 @@ gro gitops_plan
 # Output shows: my-package: 1.0.0 → 1.1.0 (minor)
 
 # Publish
-gro gitops_publish
+gro gitops_publish --wetrun
 ```
 
 ### Publishing multiple packages with cascading dependencies
@@ -211,18 +211,18 @@ gro gitops_plan
 #   @my/ui: 1.5.0 → 2.0.0 (auto-changeset, BREAKING cascade)
 
 # Publish in dependency order
-gro gitops_publish
+gro gitops_publish --wetrun
 ```
 
 ### Recovering from failures (natural resumption)
 
 ```bash
 # Publishing failed midway through
-gro gitops_publish
+gro gitops_publish --wetrun
 # Error: Failed to publish @my/package-5
 
 # Fix the issue, then re-run the same command
-gro gitops_publish
+gro gitops_publish --wetrun
 # Already-published packages have no changesets → skipped automatically
 # Failed packages still have changesets → retried automatically
 ```
@@ -240,5 +240,5 @@ gro gitops_plan
 #   @my/app: 2.0.0 → 3.0.0 (patch → major, escalated)
 
 # Publish handles escalation automatically
-gro gitops_publish
+gro gitops_publish --wetrun
 ```

docs/troubleshooting.md

@@ -78,7 +78,7 @@ NPM propagation can be slow. Either:
 - Increase timeout with `--max-wait` (default is 10 minutes / 600000ms)
 - Check NPM registry status
 - Verify package was actually published
-- If verified published, re-run `gro gitops_publish` to continue
+- If verified published, re-run `gro gitops_publish --wetrun` to continue
   (already-published packages will be skipped)
 
 ## Unexpected Behavior
@@ -118,12 +118,12 @@ Check:
 Resumption is **automatic** and **natural**:
 
 1. When `gro publish` succeeds, it consumes changesets
-2. Single `gro gitops_publish` run handles full dependency cascades via
+2. Single `gro gitops_publish --wetrun` run handles full dependency cascades via
    iteration (max 10 passes)
-3. If publishing fails mid-way, re-run `gro gitops_publish`:
+3. If publishing fails mid-way, re-run `gro gitops_publish --wetrun`:
    - Already-published packages have no changesets → skipped automatically
    - Failed packages still have changesets → retried automatically
-4. No flags needed, no state files, just re-run the same command!
+4. No state files needed, just re-run the same command!
 
 This is safer than explicit state tracking because:
 
@@ -146,8 +146,8 @@ gro gitops_analyze --format markdown --outfile deps.md
 # Before publishing
 gro gitops_plan --format markdown --outfile plan.md
 
-# After publishing (dry run)
-gro gitops_publish --dry_run --format markdown --outfile actual.md
+# After publishing (dry run, which is the default)
+gro gitops_publish --format markdown --outfile actual.md
 
 # Compare files
 diff plan.md actual.md

src/lib/gitops_publish.task.ts

@@ -27,10 +27,7 @@ export const Args = z.strictObject({
 		.enum(['exact', 'caret', 'tilde'])
 		.meta({description: 'version strategy for peer dependencies'})
 		.default('caret' as const),
-	dry_run: z
-		.boolean()
-		.meta({description: 'perform a dry run without actually publishing'})
-		.default(false),
+	wetrun: z.boolean().meta({description: 'actually publish (default is dry run)'}).default(false),
 	format: z
 		.enum(['stdout', 'json', 'markdown'])
 		.meta({description: 'output format'})
@@ -63,7 +60,7 @@ export const task: Task<Args> = {
 			config,
 			dir,
 			peer_strategy,
-			dry_run,
+			wetrun,
 			format,
 			deploy,
 			plan,
@@ -82,7 +79,7 @@ export const task: Task<Args> = {
 		});
 
 		// Show plan if requested (skip for dry runs)
-		if (plan && !dry_run) {
+		if (plan && wetrun) {
 			log.info(st('cyan', 'Publishing Plan'));
 			const plan_result = await generate_publishing_plan(repos, {log, verbose});
 			log_publishing_plan(plan_result, log, {verbose});
@@ -103,7 +100,7 @@ export const task: Task<Args> = {
 
 		// Publishing options
 		const options: PublishingOptions = {
-			dry_run,
+			wetrun,
 			update_deps: true, // Always update dependencies
 			version_strategy: peer_strategy,
 			deploy,

src/lib/gitops_validate.task.ts

@@ -153,12 +153,12 @@ export const task: Task<Args> = {
 			log.error(st('red', `  ✗ gitops_plan failed: ${error}`));
 		}
 
-		// 3. Run gitops_publish --dry_run
-		log.info(st('yellow', 'Running gitops_publish --dry_run...'));
+		// 3. Run gitops_publish (dry run)
+		log.info(st('yellow', 'Running gitops_publish (dry run)...'));
 		const dry_start = Date.now();
 		try {
 			const options: PublishingOptions = {
-				dry_run: true,
+				wetrun: false,
 				update_deps: true,
 				log: undefined, // Silent for validation
 			};
@@ -171,27 +171,27 @@ export const task: Task<Args> = {
 			const errors = result.ok ? 0 : result.failed.length;
 
 			results.push({
-				command: 'gitops_publish --dry_run',
+				command: 'gitops_publish (dry run)',
 				success: result.ok,
 				warnings: 0,
 				errors,
 				duration: dry_duration,
 			});
 
-			log.info(st('green', `  ✓ gitops_publish --dry_run completed in ${dry_duration}ms`));
+			log.info(st('green', `  ✓ gitops_publish (dry run) completed in ${dry_duration}ms`));
 			if (errors > 0) {
 				log.error(st('red', `  ❌ Found ${errors} error(s)`));
 			}
 		} catch (error) {
 			const dry_duration = Date.now() - dry_start;
 			results.push({
-				command: 'gitops_publish --dry_run',
+				command: 'gitops_publish (dry run)',
 				success: false,
 				warnings: 0,
 				errors: 1,
 				duration: dry_duration,
 			});
-			log.error(st('red', `  ✗ gitops_publish --dry_run failed: ${error}`));
+			log.error(st('red', `  ✗ gitops_publish (dry run) failed: ${error}`));
 		}
 
 		// Summary