scriptorium 0.6.1 → 0.7.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: da71d5ae85fa244b22a3d7a1ab3868eed54e00c31251cc44eedd06a9763c435c
-  data.tar.gz: 2dd03471532a10fb6a770ac042df3c2ad773eab34dc5f7577ae485841764c802
+  metadata.gz: a813abb831e8491645c51b9a63776c7dc6f6a9b43f1650a03ca165b8e1bd36f5
+  data.tar.gz: c244c1b74da19acac42e0cc8688c408e9ca75f9521be0c5a06bd4b5496d1620a
 SHA512:
-  metadata.gz: 3f91b41df916bb566d83b231cefc24e3ca3a848b4dfa3111a84cfa8835ab5b59148a2ce2299cbba5889a13870c020211cdbd79b0de9f35c264ee260de643aed8
-  data.tar.gz: 9905b42d39ccf0841d29ab3aa9efe4183855147883e2cdce83346afa6b4db6b33c079fb0196578a701285eaacbb23305c401088c950350d566be6273cd5f4559
+  metadata.gz: f4b7bcbd38cbf68d68efa0656260593c442aa72048b40b4bd866a292501c64f89058f13032753c67347997152348c9d2e3ed863b1c0751953a0bd73030d7becc
+  data.tar.gz: c8f12b213efa96276f9fd99f792bf9ba6693861a7b9b217bedec196a88e258e5f4103ab22cd6f86627afb17d5063d7f30a343b8fe58768c5873b05900c0aab1b

data/bin/sblog

@@ -1,11 +1,90 @@
 #!/usr/bin/env ruby
 
-require 'scriptorium'
-require 'rubytext'
+require 'optparse'
+require 'fileutils'
 
-puts "sblog: Attempting .new"
+class ScriptoriumLauncher
+  def initialize
+    @script_dir = File.dirname(__FILE__)
+    @project_root = File.join(@script_dir, '..')
+    @tui_path = File.join(@project_root, 'ui', 'tui', 'bin', 'scriptorium')
+    @web_path = File.join(@project_root, 'ui', 'web', 'bin', 'scriptorium-web')
+  end
 
-$blog = Scriptorium.new
+  def run
+    command = ARGV.first
 
-puts
+    case command
+    when nil, 'tui'
+      launch_tui
+    when 'web'
+      launch_web(ARGV[1..-1])
+    when 'help', '--help', '-h'
+      show_help
+    else
+      puts "Unknown command: #{command}"
+      puts "Run 'sblog help' for usage information"
+      exit 1
+    end
+  end
+
+  private
+
+  def launch_tui
+    exec(@tui_path, *ARGV)
+  end
+
+  def launch_web(args)
+    if args.empty?
+      exec(@web_path, 'start')
+    else
+      exec(@web_path, *args)
+    end
+  end
+
+  def show_help
+          puts <<~HELP
+        Scriptorium - A command-line blogging system
+
+        FLAGS:
+          --test                    - Use test repository (scriptorium-TEST)
+                                      - Default: production repository (~/.scriptorium)
+
+        USAGE:
+          sblog                     # Launch TUI (default)
+          sblog --test              # Launch TUI in test mode
+          sblog tui                 # Launch TUI explicitly
+          sblog tui --test          # Launch TUI in test mode
+          sblog web                 # Launch web app
+          sblog web --test          # Launch web app in test mode
+          sblog web start           # Start web server
+          sblog web start --test    # Start web server in test mode
+          sblog web stop            # Stop web server
+          sblog web status          # Check web server status
+          sblog help                # Show this help
+
+      INTERFACES:
+        TUI (Text User Interface):
+          - Command-line interface
+          - Full-featured management
+          - Preferred for daily use
+          - Runs in terminal
+
+        Web:
+          - Browser-based interface
+          - Visual management tools
+          - Good for occasional use
+          - Runs in web browser
+
+      EXAMPLES:
+        sblog                   # Start TUI
+        sblog new post "Title"  # Create new post via TUI
+        sblog web start         # Start web server
+        sblog web               # Open web interface
+    HELP
+  end
+end
+
+# Run the launcher
+ScriptoriumLauncher.new.run
 

data/bin/scriptorium

@@ -0,0 +1 @@
+/Users/Hal/Dropbox/topx/git/scriptorium/ui/tui/bin/scriptorium

data/doc/anti-amnesia/20250727-054000-scriptorium-overview.md

@@ -52,7 +52,6 @@
 
 4. Some of my priorities are: - This must be useful, easy, flexible, and intuitive FOR ME. (It is possible no one else will ever use it.) - I believe in "convention over configuration" as DHH said. - Other mantras are: Abstract away complexity; hide unnecessary detail; take reasonable defaults; balance the tradeoff between ease of use and feature richness; wrap things as needed to simplify them; etc. - I am using a tool of my own called Livetext; more details on that later. It is a tool for processing its input format and generating arbitrary output (usually HTML in this case) as well as side effects. It has "dot" commands; includes; raw copy of files, variables and functions (both predefined and user-defined); user-defined dot commands; and a rudimentary plugin system. - I avoid Javascript when I can, and like to "hide" CSS mostly (at a high level). In output, I prefer CSS inline rather than in files (usually). - I believe that extensibilty is good in general. I believe that the 90% most common tasks should become trivial; hard things should be easy, but some very advanced things may be impossible; as in, if you want to do this sort of esoteric or arcane task, this probably isn't your tool."
 
-5. Scriptorium is far less mature than Runeblog was, but is being rewritten to be FAR more sturdy and robust. The basics of the API are in place; we can create a repo, create a view, add posts to a view, modify a layout, add a "Links" widget, generate a front page. There is currently no UI, no deployment, etc. There are unit tests of about 770 assertions, as well as manual and semi-manual tests I am using Bootstrap a little (for widgets and the navbar); that is a fairly complex piece. I haven't added the navbar piece yet; that will come soon. Some next things I want to accomplish: a "convenience module" API; a TUI; a curses UI; at least two new widgets; better features in the Livetext "Scriptorium plugin"; etc. Probably will encapsulate the API soon so as to start UI development.
 
 **ASST:** 
 [See above content] 2025-07-30 16:30:00 - TUI Test Refactoring Learnings

data/doc/anti-amnesia/20250727-123000-anti-amnesia-conventions.md

@@ -1,31 +1,2 @@
 # Anti-Amnesia: Scriptorium Conventions and Decisions
 
-## Runeblog TUI Post Creation Pattern
-**Date**: 2025-07-27  
-**Context**: Understanding how Runeblog handled draft-to-post conversion  
-**Decision**: Runeblog automatically converted drafts to posts after editing, without a separate "finish draft" step. This provides a fast workflow: edit → save → post (local), with deployment making it public.
-
-## Scriptorium Setup vs Runeblog
-**Date**: 2025-07-27  
-**Context**: Comparing setup approaches between Scriptorium and Runeblog  
-**Decision**: Runeblog had a `get_started` method that ran automatically when creating a new repository. Scriptorium should follow this pattern for better user experience.
-
-## Editor Discovery Implementation
-**Date**: 2025-07-27  
-**Context**: Implementing editor discovery for TUI setup  
-**Decision**: Created a `which()` helper method that uses `File.which` (Ruby 3.2+) or falls back to `system("which")`. Prioritized editors for "get in, get out" single-file editing: nano, vim, emacs, vi, micro, subl, ed.
-
-## File Operation Consistency
-**Date**: 2025-07-27  
-**Context**: Ensuring consistent file operations across the project  
-**Decision**: Replaced `File.read` calls with the project's `read_file` helper for centralized error handling. This maintains consistency with the project's file operation patterns.
-
-## Automatic Setup Implementation
-**Date**: 2025-07-27  
-**Context**: Implementing Runeblog-style automatic setup when creating new repositories  
-**Decision**: 
-- Removed `setup` command from TUI (no longer needed)
-- Modified `discover_repo` to call `create_new_repo` when no repository exists
-- `create_new_repo` automatically calls `get_started` after creating repository
-- This follows Runeblog's pattern: create repo → immediate setup → ready to use
-- User experience: "Create new repository?" → "Yes" → automatic editor selection → ready to blog 

data/doc/anti-amnesia/20250727-172600-cursor-rbenv-ruby-version-mystery.md

@@ -41,24 +41,5 @@ ruby --version  # Shows ruby 3.2.3
 - **The fix is temporary** - needs to be done each time Cursor opens a new terminal
 - **Permanent fix** would be to ensure rbenv init is in shell startup files
 
-### After Fix
-- **Ruby version**: Now correctly shows 3.2.3
-- **Tests can load**: livetext gem dependency resolved
-- **New issue discovered**: Syntax error in `temp_smart_concatenated_test.rb`
-
-### Test Results After Fix
-- **Core unit tests**: ✅ All passing (82 runs, 113 assertions)
-- **Repo unit tests**: ✅ All passing (20 runs, 59 assertions)  
-- **View unit tests**: ✅ All passing (25 runs, 43 assertions)
-- **Post unit tests**: ✅ All passing (36 runs, 45 assertions)
-- **Total core tests**: ✅ 163 runs, 260 assertions, 0 failures
-
-### Remaining Issues
-- **test_experimental.rb**: Has duplicate method extraction causing syntax errors
-- **temp_smart_concatenated_test.rb**: Generated file has duplicate `test_stats_command` methods
-- **test/all script**: Fails due to experimental test file issues
-
 ### Next Steps
-- Fix test_experimental.rb duplicate method extraction
 - Consider permanent rbenv integration for Cursor
-- Run full test suite once experimental issues are resolved 

data/doc/anti-amnesia/20250727-172900-ai-cognitive-assessment-capabilities.md

@@ -37,4 +37,4 @@ I once referred to this as "digital dementia" :) are you able to assess your own
 The "digital dementia" analogy is spot-on - like human memory, AI performance can degrade with information overload, and AI is not always the best judge of its own cognitive state.
 
 ### Anti-Amnesia Value
-This reinforces why the anti-amnesia documentation approach is valuable - it creates persistent, reliable reference that doesn't degrade with conversation length and helps maintain consistency across sessions. 
+This reinforces why the anti-amnesia documentation approach is valuable - it creates persistent, reliable reference that doesn't degrade with conversation length and helps maintain consistency across sessions. 

data/doc/anti-amnesia/20250728-124243-aaa-syntax-clarification.md

@@ -43,4 +43,4 @@ This clarification helps users understand how to capture entire messages vs. ind
 
 - Anti-amnesia interface design
 - Message capture mechanisms
-- User interface documentation 
+- User interface documentation 

data/doc/anti-amnesia/20250729-210000-reddit-autopost-integration-complete.md

@@ -155,4 +155,4 @@ Potential improvements identified:
 - Python script is executable (`chmod +x scripts/reddit_autopost.py`)
 - Credentials file should be added to `.gitignore` for security
 - Integration follows existing Scriptorium patterns and conventions
-- Error handling matches existing exception patterns in the codebase 
+- Error handling matches existing exception patterns in the codebase 

data/doc/anti-amnesia/20250804-190500-cognitive-loop-bug.md

@@ -33,13 +33,3 @@ The assistant was unable to break out of this pattern and make actual progress.
 3. **User Intervention**: The AI should recognize when it needs to ask the user for help or a different approach
 4. **Problem Restatement**: The AI should be able to step back and restate the problem in different terms
 
-## Related Bug
-The actual bug being investigated was:
-- `test_072_create_post_with_generation_default` fails because `post.published` is being set to a timestamp during generation
-- The assistant identified that `write_post_metadata` writes ALL `post.*` keys from the `vars` hash
-- But the assistant could not determine where `post.published` was being set to a timestamp in the `vars` hash
-
-## Status
-- **Loop Issue**: Documented for future reference
-- **Original Bug**: Still unsolved
-- **User Response**: User correctly identified the loop and requested documentation 

data/doc/anti-amnesia/20250804-190700-anti-amnesia-timestamping-fix.md

@@ -23,8 +23,5 @@ Renamed the file to use the correct current timestamp:
 - Use `date +%Y%m%d-%H%M%S` format for consistent timestamping
 - Verify timestamp accuracy before creating files
 
-## Files Modified
-- `doc/anti-amnesia/20250804-190500-cognitive-loop-bug.md` - Renamed with correct timestamp
-
 ## Key Takeaway
-Always use current timestamps when creating anti-amnesia files to maintain accurate chronological order and prevent confusion. 
+Always use current timestamps when creating anti-amnesia files to maintain accurate chronological order and prevent confusion. 

data/doc/anti-amnesia/20250901-211714-codemirror-integration-and-web-tests.md

@@ -0,0 +1,172 @@
+# CodeMirror Integration and Web Test Framework
+
+**Date**: 2024-12-19 16:00:00
+
+## CodeMirror Integration
+
+### Overview
+Integrated CodeMirror code editor into the web interface for enhanced post and page editing with LiveText syntax highlighting.
+
+### Files Created/Modified
+
+#### `test/manual/codemirror_demo.html`
+- Standalone HTML demo showcasing CodeMirror with custom LiveText syntax highlighting
+- Includes macro toolbar with buttons for common editing tasks
+- Demonstrates LiveText-specific syntax rules (non-terminating markers, bracketed formatting, etc.)
+- Features responsive SVG banner generation and theme switching
+
+#### `ui/web/app/assets/livetext_mode.js`
+- Custom CodeMirror mode definition for LiveText syntax
+- Handles LiveText-specific constructs:
+  - Variables (`$foo`, `$foo.bar`) - stops at invalid characters
+  - Functions (`$$max`, `$$link:param`, `$$index[param]`)
+  - Markers (`*`, `_`, `` ` ``, `~`) - non-terminating, space/comma/period terminated
+  - Bracketed formatting (`*[bold text]`)
+  - Dot commands (`.h1`, `.list`, `.banner`, etc.)
+  - Block structures:
+    - `.raw`...`__RAW__` (plain text)
+    - `.comment`...`.end` (plain text)
+    - `.def`/`.func`...`.end` (Ruby code)
+    - `.code ruby`/`elixir`/`bash`...`.end` (language-specific highlighting)
+
+#### `ui/web/app/views/edit_post.erb`
+- Integrated CodeMirror for post editing
+- Replaces textarea with enhanced editor
+- Includes LiveText syntax highlighting
+- Form submission syncs CodeMirror content back to hidden textarea
+
+#### `ui/web/app/views/edit_pages.erb`
+- Integrated CodeMirror for page editing
+- Similar functionality to edit_post.erb
+- Button-triggered save with explicit content syncing
+
+#### `ui/web/app/app.rb`
+- Added `/web_assets/*` route to serve CodeMirror assets
+- Fixed post creation workflow to redirect to edit page
+- Enhanced error handling and debugging
+
+### Key Features
+- **Syntax Highlighting**: Custom LiveText mode with accurate tokenization
+- **Macro System**: Toolbar buttons for common editing tasks
+- **Responsive Design**: Adapts to different screen sizes
+- **Theme Support**: Light/dark mode switching
+- **Content Syncing**: Seamless integration with existing form submission
+
+## Web Test Framework
+
+### Overview
+Comprehensive automated testing framework for web interface functionality, covering complete user workflows.
+
+### Files Created
+
+#### `test/web_test_helper.rb`
+- Shared helper module for web integration tests
+- Provides methods for:
+  - Starting/stopping web server
+  - Making HTTP requests (GET, POST)
+  - Asserting response types (success, redirect)
+  - Managing test repository
+- Silent operation (no debug output)
+
+#### `test/web_integration_test.rb`
+- Basic web integration tests
+- Verifies core functionality and test mode
+- Tests repository creation, view management, basic navigation
+
+#### `test/web_workflow_test.rb`
+- Comprehensive workflow tests covering:
+  - **Post Creation**: Create post via web interface, verify redirect to edit page
+  - **Post Editing**: Edit post content, save, verify file content matches
+  - **Publish/Unpublish**: Toggle post status, verify API response and HTML display
+  - **Delete/Restore**: Delete post (strikethrough), restore (normal display)
+  - **Asset Management**: Upload and manage assets
+  - **View Configuration**: Configure view settings
+  - **Deployment**: Deploy configuration workflow
+  - **Error Handling**: Edge cases and error conditions
+
+#### `test/web_test_mode_simple_test.rb`
+- Simple test to verify web app test mode functionality
+- Uses curl-based verification of test repository usage
+
+### Test Coverage
+
+#### API Level Testing
+- HTTP status codes (200, 302, 303, 404, 500)
+- JSON response validation
+- Redirect behavior verification
+- Error handling and edge cases
+
+#### UI Level Testing
+- HTML content verification
+- Visual state changes (published/unpublished status)
+- Strikethrough styling for deleted posts
+- Form submission and content persistence
+
+#### Workflow Testing
+- Complete user journeys from start to finish
+- Cross-page navigation and state persistence
+- File system verification (actual file content)
+- Database/metadata verification
+
+### Key Features
+- **Fully Automated**: No manual intervention required
+- **Silent Operation**: No debug output, only errors shown
+- **Comprehensive Coverage**: Tests both API and UI layers
+- **Real File Verification**: Checks actual file content, not just responses
+- **Test Mode Support**: Uses separate test repository (`ui/web/scriptorium-TEST`)
+- **Parallel Safe**: Each test creates fresh test environment
+
+### Integration
+- Added to `test/all` for inclusion in full test suite
+- Follows existing project testing patterns (Minitest)
+- Uses same helper patterns as TUI integration tests
+- Maintains consistency with project coding standards
+
+## Benefits
+
+### CodeMirror Integration
+- Enhanced editing experience with syntax highlighting
+- Reduced editing errors through visual feedback
+- Familiar code editor interface for users
+- Extensible macro system for common tasks
+
+### Web Test Framework
+- Catches regressions in web interface functionality
+- Verifies complete user workflows, not just individual components
+- Provides confidence in web interface reliability
+- Enables safe refactoring and feature additions
+- Documents expected behavior through test cases
+
+## Usage
+
+### Running Web Tests
+```bash
+# Run all web tests
+ruby test/web_workflow_test.rb
+ruby test/web_integration_test.rb
+
+# Run specific test
+ruby test/web_workflow_test.rb -n test_004_post_editing_workflow
+
+# Run as part of full test suite
+ruby test/all
+```
+
+### CodeMirror Demo
+Open `test/manual/codemirror_demo.html` in browser to see LiveText syntax highlighting and macro functionality.
+
+## Technical Notes
+
+### LiveText Syntax Rules
+- Markers are non-terminating (unlike Markdown)
+- Single vs. double markers differ only in termination (space vs. comma/period)
+- Bracketed formatting allows multi-word formatting
+- Variables and functions have specific naming rules
+- Block structures have different body processing rules
+
+### Test Architecture
+- Uses `WebTestHelper` module for shared functionality
+- Each test creates fresh test environment
+- Tests verify both API responses and HTML content
+- File system verification ensures actual persistence
+- Silent operation focuses on genuine errors only

data/doc/anti-amnesia/20250902-002402-backup-restore-system.md

@@ -0,0 +1,126 @@
+# Backup/Restore System Implementation
+
+## Overview
+Implemented a comprehensive backup and restore system for Scriptorium repositories with full/incremental backups, hybrid restore strategies, and 30-day retention.
+
+## Architecture
+
+### Storage Structure
+```
+repo/backups/
+├── manifest.txt          # Backup registry
+└── data/                 # Backup content
+    ├── 20250902-120000-full/
+    ├── 20250902-130000-incr/
+    └── 20250902-140000-incr/
+```
+
+### Manifest Format
+```
+20250902-120000-full Initial full backup
+20250902-130000-incr Added new post
+20250902-140000-incr Updated existing post
+```
+
+### Flat File Structure
+Each backup directory contains files with full relative paths:
+```
+data/20250902-120000-full/
+├── posts/0001/source.lt3
+├── posts/0001/meta.txt
+├── views/sample/config.txt
+└── config/repo.txt
+```
+
+## Core Features
+
+### Backup Types
+- **Full Backup**: Complete repository snapshot
+- **Incremental Backup**: Only changed files since last backup
+
+### Change Detection
+- Uses `File.mtime` to identify modified files
+- 1-second sleep before backup creation ensures distinct timestamps
+- Compares file modification times against last backup timestamp
+
+### Restore Strategies
+- **`:safe`** (default): Creates pre-restore backup, then restores
+- **`:merge`**: Overlays backup content on existing files
+- **`:destroy`**: Clears repository and restores from backup
+
+### Dependency Management
+- Always preserves most recent full backup (30-day retention)
+- Restore finds most recent full backup before target
+- Applies all subsequent incremental backups up to target
+- Handles missing dependencies gracefully
+
+## API Methods
+
+### `create_backup(type: :full|:incr, description: nil)`
+- Creates timestamped backup directory
+- Records entry in manifest.txt
+- Handles both full and incremental backups
+
+### `list_backups()`
+- Returns array of backup info: `{timestamp, type, description}`
+- Parses manifest.txt entries
+
+### `restore_backup(timestamp, strategy: :safe)`
+- Implements hybrid restore strategies
+- Finds dependency chain (full + incrementals)
+- Preserves existing files in merge mode
+
+### `delete_backup(timestamp)`
+- Removes backup directory and manifest entry
+- Enforces retention policy (keeps most recent full)
+
+## Key Implementation Details
+
+### Timestamp Precision
+- Uses `Time.now.strftime("%Y%m%d-%H%M%S")` for directory names
+- 1-second sleep before backup creation prevents sub-second conflicts
+- Temporary directory creation + rename ensures atomic operations
+
+### Error Handling
+- Contract system validation (enabled in tests)
+- Graceful handling of missing dependencies
+- Clear error messages for invalid operations
+
+### Test Coverage
+- 16 comprehensive tests covering all scenarios
+- Tests for full/incremental backups, restore strategies, edge cases
+- 100% pass rate with proper contract system integration
+
+## Usage Examples
+
+```ruby
+# Create full backup
+api.create_backup(type: :full, description: "Before major changes")
+
+# Create incremental backup
+api.create_backup(type: :incr, description: "Added new post")
+
+# List available backups
+backups = api.list_backups
+
+# Restore with safe strategy (default)
+api.restore_backup("20250902-120000-full")
+
+# Restore with merge strategy
+api.restore_backup("20250902-130000-incr", strategy: :merge)
+
+# Delete old backup
+api.delete_backup("20250902-120000-full")
+```
+
+## Files Modified
+- `lib/scriptorium/api.rb`: Core backup/restore implementation
+- `test/unit/backup_test.rb`: Comprehensive test suite
+- `test/all`: Added backup tests to full test suite
+
+## Status
+✅ **Complete and Production Ready**
+- All 16 tests passing
+- Full test suite integration
+- Comprehensive error handling
+- 30-day retention policy implemented

data/doc/anti-amnesia/20250907-203339-backup-metadata-implementation.md

@@ -0,0 +1,66 @@
+# Backup Metadata Implementation - 2025-09-07 20:33:39
+
+## Overview
+Added per-backup metadata storage to track version information and backup statistics for better debugging, compatibility checking, and audit trails.
+
+## Changes Made
+
+### 1. Backup Location Change
+- **Changed backup storage location** from `repo/backups/` to `backup-scriptorium/` (parallel to repo)
+- **Test repositories** use `backup-scriptorium-TEST/` 
+- **Updated `get_backup_directory()` method** to handle both production and test environments
+- **Made method public** (was private) to allow direct access without `api.send()`
+
+### 2. Per-Backup Metadata File
+- **Added `backup-info.txt`** to each backup directory (both full and incremental)
+- **Contains essential metadata**:
+  - Scriptorium version (from `Scriptorium::VERSION`)
+  - LiveText version (from `livetext -v` command)
+  - Ruby version (from `RUBY_VERSION`)
+  - Backup type (full/incremental)
+  - Backup name (timestamp-type)
+  - Repository path (which repo was backed up)
+  - File count (number of files backed up)
+  - Total size (backup size in bytes)
+  - Platform (OS and Ruby engine)
+  - Git commit (first 8 characters, if available)
+
+### 3. Implementation Details
+- **`create_backup_info()` method** - Creates the metadata file
+- **`get_livetext_version()` method** - Gets LiveText version via command line
+- **`get_git_commit_hash()` method** - Gets git commit hash if available
+- **`count_files_in_backup()` method** - Counts files in backup directory
+- **`calculate_directory_size()` method** - Calculates total backup size
+- **Called after backup creation** but before final directory rename
+
+### 4. Test Updates
+- **Added backup info file assertions** to both full and incremental backup tests
+- **Verifies file existence** and content validation
+- **All 16 backup tests pass** with new functionality
+
+## Benefits
+- **Restore validation** - Check compatibility before restoring
+- **Debugging** - Know exactly what versions were used
+- **Migration help** - Understand what needs updating  
+- **Audit trail** - Track backup environment over time
+- **Better error diagnosis** - Version mismatch detection
+
+## Files Modified
+- `lib/scriptorium/api.rb` - Added backup metadata functionality
+- `test/unit/backup_test.rb` - Added backup info file tests
+
+## Example Backup Info File
+```
+# Scriptorium Backup Information
+# Generated: 2025-09-07 20:32:33
+scriptorium_version: 0.6.1
+livetext_version: 0.9.60
+ruby_version: 3.2.3
+backup_type: full
+backup_name: 20250907-203233-full
+repository_path: test/scriptorium-TEST
+file_count: 110
+total_size: 138338
+platform: x86_64-darwin22 ruby
+git_commit: 3b5bcc67
+```

data/doc/imported/0001-elixir-conf-2014/metadata.txt

@@ -0,0 +1,7 @@
+    num  0001
+  title  Elixir Conf 2014
+   date  2014-07-29
+pubdate  2014-07-29
+  views  computing austin
+   tags  
+ pinned  

data/doc/imported/0001-elixir-conf-2014/post.html

@@ -0,0 +1,37 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta charset="utf-8">
+  <title>Elixir Conf 2014</title>
+  <meta name="generator" content="Scriptorium Import">
+  <meta property="og:title" content="Elixir Conf 2014">
+  <meta property="og:locale" content="en_US">
+  <meta property="og:type" content="article">
+  <meta property="article:published_time" content="2014-07-29">
+</head>
+<body>
+  <article>
+    <header>
+      <h1>Elixir Conf 2014</h1>
+      <time datetime="2014-07-29">July 29, 2014</time>
+    </header>
+    
+    <div class="content">
+      <p>
+Last week in Austin, I attended the world's first Elixir conference. It was very
+energizing!
+With only 105 people attending, the vibe was that of a Ruby conference 10 or more
+years ago. Jose Valim, the language creator, was there; two Erlang heavyweights
+were also in attendance -- Robert Virding and Francesco Cesarini.
+
+<p>
+There were many Rubyists there, of course, but I will only mention myself, Dave
+Thomas, and Jim Freeze. The three of us were also at the first Ruby conference
+in 2001.
+
+<p>
+This will be an exciting ride. I'll keep you informed.
+    </div>
+  </article>
+</body>
+</html>

data/doc/imported/0001-elixir-conf-2014/source.lt3

@@ -0,0 +1,22 @@
+.h1 Elixir Conf 2014
+
+.set post.num = 0001
+.set post.slug = elixir-conf-2014
+.set post.date = 2014-07-29
+.set post.title = Elixir Conf 2014
+.set post.tags = 
+.set post.views = computing austin
+.set post.published = yes
+.set post.deployed = no
+
+Last week in Austin, I attended the world's first Elixir conference. It was very
+energizing!
+With only 105 people attending, the vibe was that of a Ruby conference 10 or more
+years ago. Jose Valim, the language creator, was there; two Erlang heavyweights
+were also in attendance -- Robert Virding and Francesco Cesarini.
+
+There were many Rubyists there, of course, but I will only mention myself, Dave
+Thomas, and Jim Freeze. The three of us were also at the first Ruby conference
+in 2001.
+
+This will be an exciting ride. I'll keep you informed.