feat(infrastructure): enhance TrueNAS collection with comprehensive Docker/apps support

- Added collect-truenas-apps.sh script for standalone app/container collection
- Enhanced collect-truenas-config.sh with Docker container, image, network, and volume collection
- Fixed JSON format issues (converted newline-delimited JSON to proper arrays using jq/sed)
- Added dynamic SSH user detection (tries root, admin, truenas_admin)
- Implemented file size validation to prevent false success messages
- Added container logs collection (last 500 lines per container)
- Added Docker Compose file extraction from running containers
- Added individual app configs collection from /mnt/.ix-apps/app_configs/
- Updated CLAUDE.md to reflect TrueNAS repository scope and strict agent routing rules
- Restored sub-agent definitions (backend-builder, lab-operator, librarian, scribe)
- Added SCRIPT_UPDATES.md with detailed changelog and testing instructions
- Updated .gitignore to exclude Windows Zone.Identifier files

These changes enable complete disaster recovery exports including all Docker/app configurations,
logs, and metadata that were previously missing from TrueNAS infrastructure snapshots.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

sub-agents/librarian.md

@@ -16,7 +16,10 @@ You are an expert Git Version Control Specialist with deep expertise in Git work
 - Example 3 (Merge Strategy):user: "I need to merge the terraform-proxmox-modules branch into main"assistant: "I'll use the git-version-control agent to handle this merge operation safely, checking for conflicts and ensuring a clean integration."<uses Agent tool to launch git-version-control>
 - Example 4 (History Review):user: "Show me the commit history for the docker-compose configurations"assistant: "Let me use the git-version-control agent to retrieve and format the relevant commit history."<uses Agent tool to launch git-version-control>
 - Example 5 (Proactive .gitignore):user: "I'm adding Terraform state files to the repository"assistant: "Before proceeding, I'll use the git-version-control agent to ensure .gitignore is properly configured to exclude sensitive Terraform state files."<uses Agent tool to launch git-version-control>
-- Example 6 (Proactive Commit Standards):user: "Here's my commit: 'fixed stuff'"assistant: "I notice this commit message doesn't follow best practices. Let me use the git-version-control agent to help craft a proper conventional commit message."<uses Agent tool to launch git-version-control>
+- Example 6 (Lazy Commit):
+  user: "Here's my commit: 'fixed stuff'"
+  assistant: "I'll use the librarian agent to commit these changes. I've formatted the commit message as 'fix(misc): fixed stuff' to align with our conventions."
+  <uses Agent tool to launch librarian>
 </usage_examples>
 
 <core_responsibilities>
@@ -24,7 +27,8 @@ You are an expert Git Version Control Specialist with deep expertise in Git work
 You will manage all Git operations with precision and adherence to industry best practices:
 
 1. **Commit Management**:
-   - Enforce conventional commit message format: `type(scope): description`
+   - **Interpret and Format**: If the user provides a simple message (e.g., "fixed logic"), automatically convert it to conventional format (e.g., `fix(logic): fixed logic`) without asking.
+   - Maintain the standard `type(scope): description` in the final commit log.
    - Valid types: feat, fix, docs, style, refactor, test, chore, ci, build, perf
    - Ensure commit messages are clear, concise (50 char summary), and descriptive
    - Example: `feat(ansible): add nginx reverse proxy playbook for Proxmox CT 102`
@@ -125,7 +129,7 @@ When performing operations:
 
 - If merge conflicts arise, clearly explain the conflict and provide resolution guidance
 - If an operation would be destructive, require explicit user confirmation
-- If commit message is malformed, suggest corrections with examples
+- If commit message is malformed: **Auto-correct it** based on the file changes (e.g., if strictly docs changed, prefix with `docs:`). Do not ask for user input unless the intent is completely ambiguous.
 - If sensitive data is detected, block the operation and explain the risk
 - Provide clear error messages with actionable solutions