Implement repeatable import process for CloverCoin Pillowing masterlist

Summary

Set up a repeatable import process for the entire CloverCoin Pillowing masterlist that is idempotent, automated, visible, and reliable.

Requirements

Import Process

• Idempotent: Can be run multiple times without creating duplicates or breaking existing data
• Automated: Minimal manual intervention required
• Visible: Clear progress reporting and logging
• Reliable: Robust error handling and recovery mechanisms

Data Source

The masterlist is located at: https://www.deviantart.com/pillowing-archive/gallery/55976959/official-pillowings

Key Features Needed

1. Nullable Owner Support

• Make owner field nullable in the database schema
• Allow pillowings to be imported with NO OWNER initially
• Support claiming orphaned characters later

2. Orphaned Characters View

• Add a view for "orphaned" characters that belong to a community/species but have no current owner
• Enable browsing and claiming of unclaimed pillowings

3. Character Claiming Process

• Allow users to claim orphaned pillowings
• Implement verification mechanism (depends on DeviantArt account linking from #62)
• Secure claiming process to prevent unauthorized claims

Technical Considerations

• Database schema updates for nullable owners
• DeviantArt API integration or web scraping strategy for import
• Import validation and conflict resolution
• Progress tracking and resumable imports
• Error handling and retry mechanisms
• Character claiming workflow

Dependencies

• DeviantArt account linking (#62) - Required for users to claim their existing characters

Acceptance Criteria

• Import process can fetch all pillowings from the masterlist
• Process is idempotent and can be safely re-run
• Pillowings can be imported without owners
• Orphaned characters view is implemented
• Users can claim orphaned pillowings (requires #62)
• Import process provides clear progress reporting
• Robust error handling and recovery
• Database schema supports nullable owners

No files, tests, or entry points are named. Start by locating the database schema and any import or DeviantArt integration entry points, then map the dependency on #62; done means the masterlist imports repeatably with nullable owners, progress and recovery reporting, orphan browsing, and secure claiming.