appydave-tools 0.18.3 → 0.18.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 224b91f6d2a3b037091d744166f54b656f408695edd9a3b4d5f8f0599f84c841
-  data.tar.gz: aad4d21145e880dd65b31073e3c83e5165173638d4192a35d1da836d75159d60
+  metadata.gz: 94b533e9d8174f22fe36c1dbc435b1051ddef31ac461184741958e75ae451c47
+  data.tar.gz: 252ea976c625cd3a473c46e219e4595e7f568d6f5fdbb96060b8e399cb52fd48
 SHA512:
-  metadata.gz: bf4d62d414afa97cd91115b7cea9e534d81641da2483528e551d4dcd043338055f8edd6be206ce0e8e0c3a1a8746568c1662110f275956c4b02fd2a201708f46
-  data.tar.gz: 198cf5f25d43543b9cc7861cfde567a3452ae35f5c18c9e525e9958fd3efe8fc2c9fb0af751123f3df2bfd5f40f47e4e943a89a188736e8056df27d7f9d8b71b
+  metadata.gz: 1078bed7c6b2b0f4144af45d572a96c10ffa8e31d34f6dc100bc4094a847be67b500dfdf00c8e67a790e71f5e6946d29105fd37466f4412a9326dbdc509d139a
+  data.tar.gz: aa2c82acd177c562f5950b0610c05d4b278e76e44b9bd3af68d89a946dd8ffeb9cfc8359dd3e91f13d738058e7c0504978f9772640a3025bb3b2905044eec5d3

data/CHANGELOG.md

@@ -1,3 +1,18 @@
+## [0.18.4](https://github.com/appydave/appydave-tools/compare/v0.18.3...v0.18.4) (2025-11-10)
+
+
+### Bug Fixes
+
+* document dry-run and force flag support for all DAM commands in usage guide and test plan ([b4f54da](https://github.com/appydave/appydave-tools/commit/b4f54da17589b31c029d5ef62c92af8b3724ee2f))
+
+## [0.18.3](https://github.com/appydave/appydave-tools/compare/v0.18.2...v0.18.3) (2025-11-10)
+
+
+### Bug Fixes
+
+* resolve archived structure detection and range folder calculation for DAM manifest and sync ([dec1400](https://github.com/appydave/appydave-tools/commit/dec1400c561f11959fb6aecd7761e916ca525082))
+* resolve rubocop violations in manifest_generator (refactor build_project_entry, simplify SSD check) ([ced61be](https://github.com/appydave/appydave-tools/commit/ced61be41c3da352831d46e3486968f5ee55842c))
+
 ## [0.18.2](https://github.com/appydave/appydave-tools/compare/v0.18.1...v0.18.2) (2025-11-10)
 
 

data/docs/dam/{vat-testing-plan.md → dam-testing-plan.md}

@@ -30,17 +30,32 @@
 **Commands - Phase 2 Complete** (CLI args + auto-detect):
 - ✅ `dam s3-down` - Download from S3
 - ✅ `dam s3-status` - Check sync status
-- ✅ `dam s3-cleanup` - Delete S3 files
+- ✅ `dam s3-cleanup-remote` / `s3-cleanup-local` - Delete S3/local files
 
-**Commands - Not Yet Migrated**:
-- ⏳ `dam manifest` - Generate project manifest
-- ⏳ `dam archive` - Archive to SSD
-- ⏳ `dam sync-ssd` - Sync from SSD
+**Commands - Phase 3 Complete** (Archive & Manifest):
+- ✅ `dam manifest` - Generate project manifest (supports `--all` for all brands)
+- ✅ `dam archive` - Archive to SSD with dry-run and force options
+- ✅ `dam sync-ssd` - Restore light files from SSD (dry-run supported)
 
-**Utilities - Not Migrated** (not DAM commands):
-- ❌ `status-all.sh` - Git status for all repos (workflow script, not needed in gem)
-- ❌ `sync-all.sh` - Git pull for all repos (workflow script, not needed in gem)
-- ❌ `clone-all.sh` - Clone all repos (workflow script, not needed in gem)
+**Git Repository Management Scripts - Intentionally Not Migrated**:
+
+These are **shell scripts** for managing the multi-repo video-projects git structure, NOT video asset management commands:
+
+- ❌ `status-all.sh` - Runs `git status` on all v-* brand repos (git workflow, not asset management)
+- ❌ `sync-all.sh` - Runs `git pull` on all v-* brand repos (git workflow, not asset management)
+- ❌ `clone-all.sh` - Clones all v-* brand repos if missing (git workflow, not asset management)
+
+**Why not migrated:**
+1. These manage **git repositories**, not **video assets**
+2. They loop through brand folders running git commands
+3. They're workflow automation for the video-projects repo structure
+4. They belong in `/video-projects/v-shared/`, not in the appydave-tools gem
+5. Different use case: repo management vs. video file management
+
+**If you want these migrated:** We could add `dam repo-status`, `dam repo-sync`, `dam repo-clone` commands, but they would:
+- Need Ruby implementations of multi-repo git operations
+- Duplicate functionality that shell scripts handle well
+- Mix concerns (video assets vs. git repos)
 
 ---
 
@@ -113,6 +128,62 @@ dam list
 
 ---
 
+## Command Safety Features Reference
+
+### Dry-Run and Force Flag Support
+
+All filesystem-modifying commands support `--dry-run` to preview changes before execution:
+
+| Command | Dry-Run Support | Force Flag Required | What It Does |
+|---------|----------------|---------------------|--------------|
+| **s3-up** | ✅ Yes | No | Preview files to upload to S3 |
+| **s3-down** | ✅ Yes | No | Preview files to download from S3 |
+| **s3-cleanup-remote** | ✅ Yes | **Yes (`--force`)** | Preview S3 files to delete |
+| **s3-cleanup-local** | ✅ Yes | **Yes (`--force`)** | Preview local s3-staging files to delete |
+| **archive** | ✅ Yes | Optional (`--force` = delete local) | Preview project copy to SSD |
+| **sync-ssd** | ✅ Yes | No | Preview light files to restore from SSD |
+
+### Read-Only Commands (No Dry-Run Needed)
+
+These commands only read data and don't modify files:
+
+| Command | Type | What It Does |
+|---------|------|--------------|
+| **list** | Read-only | List brands/projects |
+| **manifest** | Generates JSON | Generate `projects.json` manifest |
+| **s3-status** | Read-only | Check sync status |
+| **help** | Read-only | Show help information |
+
+### Force Flag Behavior
+
+Commands requiring `--force` provide extra protection for destructive operations:
+
+- **s3-cleanup-remote**: Must use `--force` to delete S3 files (prevents accidental deletion)
+- **s3-cleanup-local**: Must use `--force` to delete local staging files
+- **archive**: Optional `--force` flag deletes local copy after successful SSD backup
+  - Without `--force`: Copies to SSD, keeps local copy intact
+  - With `--force`: Copies to SSD, then deletes local copy (frees disk space)
+
+### Safety Testing Workflow
+
+**Always test with dry-run first:**
+
+```bash
+# 1. Preview with dry-run
+dam s3-up appydave b65 --dry-run
+dam s3-cleanup-remote appydave b65 --force --dry-run
+dam archive appydave b63 --dry-run
+
+# 2. Review output carefully
+
+# 3. Execute if safe
+dam s3-up appydave b65
+dam s3-cleanup-remote appydave b65 --force
+dam archive appydave b63
+```
+
+---
+
 ## Test Suite
 
 ### Phase 1: Unit Tests (Automated - RSpec)
@@ -579,51 +650,51 @@ done
 
 ---
 
-## Not Yet Implemented (Future Work)
+## ✅ All DAM Commands Implemented
 
-### Commands Migrated but Not Updated for CLI Args
+All video asset management commands have been successfully migrated and are fully functional:
 
-These commands were copied from the original DAM but still need Phase 2 updates:
+### Phase 1: Core Commands
+- ✅ `dam help` - Comprehensive help system
+- ✅ `dam list` - Project discovery with 4 modes
 
-#### ⏳ Generate Manifest
-```bash
-# Current: bin/generate_manifest.rb
-# Expected: dam manifest appydave
-```
-**Status**: Copied but needs CLI arg support
-**Priority**: Low (utility command, not core workflow)
+### Phase 2: S3 Collaboration
+- ✅ `dam s3-up` - Upload to S3 with dry-run
+- ✅ `dam s3-down` - Download from S3 with dry-run
+- ✅ `dam s3-status` - Check sync status
+- ✅ `dam s3-cleanup-remote` - Delete S3 files (force + dry-run)
+- ✅ `dam s3-cleanup-local` - Delete local staging (force + dry-run)
 
----
+### Phase 3: Archive & Manifest
+- ✅ `dam manifest` - Generate project manifest (single brand or `--all`)
+- ✅ `dam archive` - Archive to SSD (dry-run + optional force)
+- ✅ `dam sync-ssd` - Restore light files from SSD (dry-run)
 
-#### ⏳ Archive Project
-```bash
-# Current: bin/archive_project.rb
-# Expected: dam archive appydave b63
-```
-**Status**: Copied but needs CLI arg support
-**Priority**: Medium (used for completed projects)
+### All Commands Support:
+- **CLI args**: `dam <command> <brand> <project>`
+- **Auto-detect**: Works from project directory (where applicable)
+- **Dry-run**: All destructive operations support `--dry-run`
+- **Force flags**: Extra safety for deletions
 
 ---
 
-#### ⏳ Sync from SSD
-```bash
-# Current: bin/sync_from_ssd.rb
-# Expected: dam sync-ssd appydave
-```
-**Status**: Copied but needs CLI arg support
-**Priority**: Medium (used for recovery)
+## Git Repository Scripts - Separate Concern
 
----
+The following shell scripts are **intentionally not migrated** as they manage git repositories, not video assets:
 
-### Workflow Scripts (Not Migrating to Gem)
+### `/video-projects/v-shared/*.sh`
 
-These are repository management scripts, not DAM commands:
+- `status-all.sh` - Runs `git status` on all v-* brand repos
+- `sync-all.sh` - Runs `git pull` on all v-* brand repos
+- `clone-all.sh` - Clones missing v-* brand repos
 
-- ❌ `status-all.sh` - Git status for all v-* repos
-- ❌ `sync-all.sh` - Git pull for all repos
-- ❌ `clone-all.sh` - Clone all brand repos
+**Why separate:**
+1. Different domain: Git repository management vs. video asset management
+2. Different tools: Shell + git commands vs. Ruby + AWS/file operations
+3. Different location: Belongs in video-projects workspace, not in distributed gem
+4. Shell scripts work perfectly for this use case
 
-**Rationale**: These are development workflow tools for managing the video-projects repository structure, not video asset operations. They belong in the video-projects folder, not the appydave-tools gem.
+**If migration is desired:** Could add `dam repo-status/sync/clone` but would duplicate working shell functionality and mix concerns.
 
 ---
 
@@ -683,14 +754,15 @@ These are repository management scripts, not DAM commands:
 - [x] `dam s3-up` - Upload to S3
 - [x] `dam s3-down` - Download from S3 ⭐ Phase 2 complete
 - [x] `dam s3-status` - Check sync status ⭐ Phase 2 complete
-- [x] `dam s3-cleanup` - Delete S3 files ⭐ Phase 2 complete
+- [x] `dam s3-cleanup-remote` / `s3-cleanup-local` - Delete S3/local files ⭐ Phase 2 complete
+- [x] `dam manifest` - Generate project manifest ⭐ Phase 3 complete
+- [x] `dam archive` - Archive to SSD (dry-run + force) ⭐ Phase 3 complete
+- [x] `dam sync-ssd` - Sync from SSD (dry-run) ⭐ Phase 3 complete
 
 ### ⏳ Pending Implementation
 
-**Commands (Copied but need CLI arg support)**:
-- [ ] `dam manifest` - Generate project manifest
-- [ ] `dam archive` - Archive to SSD
-- [ ] `dam sync-ssd` - Sync from SSD
+**Commands**:
+- [x] All DAM commands ✅ COMPLETE
 
 **Testing**:
 - [ ] Manual integration tests (Phase 2)

data/docs/dam/usage.md

@@ -561,17 +561,70 @@ dam s3-down
 dam s3-status
 ```
 
-### Dry-Run Mode
+### Command Safety Features
 
-Preview actions without making changes:
+#### Dry-Run Support
+
+All filesystem-modifying commands support `--dry-run` to preview changes before execution:
+
+| Command | Dry-Run Support | Force Flag Required | What It Previews |
+|---------|----------------|---------------------|------------------|
+| **s3-up** | ✅ Yes | No | Files to upload to S3 |
+| **s3-down** | ✅ Yes | No | Files to download from S3 |
+| **s3-cleanup-remote** | ✅ Yes | **Yes (`--force`)** | S3 files to delete |
+| **s3-cleanup-local** | ✅ Yes | **Yes (`--force`)** | Local s3-staging files to delete |
+| **archive** | ✅ Yes | Optional (`--force` = delete local) | Project to copy to SSD |
+| **sync-ssd** | ✅ Yes | No | Light files to restore from SSD |
+
+#### Read-Only Commands (No Dry-Run Needed)
+
+These commands only read data and don't modify files:
+
+| Command | Type | What It Does |
+|---------|------|--------------|
+| **list** | Read-only | List brands/projects |
+| **manifest** | Generates JSON | Generate `projects.json` manifest |
+| **s3-status** | Read-only | Check sync status |
+| **help** | Read-only | Show help information |
+
+#### Safety Workflow Examples
+
+**Always preview destructive operations first:**
 
 ```bash
+# Preview S3 upload
 dam s3-up appydave b65 --dry-run
-dam s3-down voz boy-baker --dry-run
-dam s3-cleanup-remote aitldr movie-posters --dry-run
-dam s3-cleanup-local appydave b65 --dry-run
+# Review output, then execute
+dam s3-up appydave b65
+
+# Preview S3 cleanup (requires --force)
+dam s3-cleanup-remote appydave b65 --force --dry-run
+# Review output, then execute
+dam s3-cleanup-remote appydave b65 --force
+
+# Preview archive (with or without local deletion)
+dam archive appydave b63 --dry-run              # Copy only
+dam archive appydave b63 --force --dry-run      # Copy + delete local
+# Review output, then execute
+dam archive appydave b63                        # Copy only
+dam archive appydave b63 --force                # Copy + delete local
+
+# Preview SSD sync
+dam sync-ssd appydave --dry-run
+# Review output, then execute
+dam sync-ssd appydave
 ```
 
+#### Force Flag Behavior
+
+Commands requiring `--force` provide extra protection for destructive operations:
+
+- **s3-cleanup-remote**: Must use `--force` to delete S3 files (prevents accidental deletion)
+- **s3-cleanup-local**: Must use `--force` to delete local staging files
+- **archive**: Optional `--force` flag deletes local copy after successful SSD backup
+  - Without `--force`: Copies to SSD, keeps local copy intact
+  - With `--force`: Copies to SSD, then deletes local copy (frees disk space)
+
 ### Interactive Selection
 
 When multiple projects match short name:

data/lib/appydave/tools/version.rb

@@ -2,6 +2,6 @@
 
 module Appydave
   module Tools
-    VERSION = '0.18.3'
+    VERSION = '0.18.5'
   end
 end

data/package.json

@@ -1,6 +1,6 @@
 {
   "name": "appydave-tools",
-  "version": "0.18.3",
+  "version": "0.18.5",
   "description": "AppyDave YouTube Automation Tools",
   "scripts": {
     "release": "semantic-release"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: appydave-tools
 version: !ruby/object:Gem::Version
-  version: 0.18.3
+  version: 0.18.5
 platform: ruby
 authors:
 - David Cruwys
@@ -241,10 +241,10 @@ files:
 - docs/configuration/README.md
 - docs/configuration/channels.example.json
 - docs/configuration/settings.example.json
+- docs/dam/dam-testing-plan.md
 - docs/dam/dam-vision.md
 - docs/dam/session-summary-2025-11-09.md
 - docs/dam/usage.md
-- docs/dam/vat-testing-plan.md
 - docs/dam/windows-testing-guide.md
 - docs/development/CODEX-recommendations.md
 - docs/development/README.md