appydave-tools 0.18.4 → 0.18.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 13697577cf21ab548b3ab152ad3a12194cf26c034eeaf2fdf5325b49730fe120
-  data.tar.gz: b1d7ee7daf7b60c00b80b0ec399ca7d5664d38d41cdacec959f8f8ba3f440d64
+  metadata.gz: 94b533e9d8174f22fe36c1dbc435b1051ddef31ac461184741958e75ae451c47
+  data.tar.gz: 252ea976c625cd3a473c46e219e4595e7f568d6f5fdbb96060b8e399cb52fd48
 SHA512:
-  metadata.gz: 8d6d9643703e76b3946ca0f5923b74972e04b3981a5cd2ca3ebbac315d2d42c98064dc5e6dc12dbc0833073e1b7b36c5b41f1276b38acb5a01dd86802f7aabce
-  data.tar.gz: 390852362fe0ecc9c45bf4c45bfb87ef8fc697051026b89e3f93eacdfd55a8ed9796f2892870e2d661ab4491fc0183ac07d4046ae6051588fe4111b1b0140c21
+  metadata.gz: 1078bed7c6b2b0f4144af45d572a96c10ffa8e31d34f6dc100bc4094a847be67b500dfdf00c8e67a790e71f5e6946d29105fd37466f4412a9326dbdc509d139a
+  data.tar.gz: aa2c82acd177c562f5950b0610c05d4b278e76e44b9bd3af68d89a946dd8ffeb9cfc8359dd3e91f13d738058e7c0504978f9772640a3025bb3b2905044eec5d3

data/CHANGELOG.md

@@ -1,3 +1,10 @@
+## [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)
 
 

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)
 
 ---
 
@@ -635,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.
 
 ---
 
@@ -739,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/lib/appydave/tools/version.rb

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

data/package.json

@@ -1,6 +1,6 @@
 {
   "name": "appydave-tools",
-  "version": "0.18.4",
+  "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.4
+  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