Remove database migrations to flatten database

[frankbria]

The application is not in production and there are no users. So there is no need for database migration layers to create backward compatability.

Flatten all migrations to a single database schema. Remove all migrations and references to migrations - including: startup scripts, documentation, testing, and APIs.

[traycerai]

Plan

Observations

The codebase has a migration system that was used during development but is now deprecated. The Database._create_schema() method already contains the flattened v1.0 schema with all historical migrations incorporated. The run_migrations parameter in Database.initialize() is marked as deprecated (line 88-90 in database.py), but the migration infrastructure (_run_migrations() method, migration files, tests, and documentation) still exists throughout the codebase. There are 11 migration files in the archive directory, migration-specific tests, documentation, and a verification script.

Approach

The plan follows a systematic removal approach: first eliminate the migration execution logic and tracking table from the database layer, then remove all migration files and infrastructure, update all test files to remove migration-related code, clean up documentation references, and finally remove the deprecated run_migrations parameter. This ensures a clean removal without breaking existing functionality, as the flattened schema in _create_schema() already contains all necessary table definitions.

Implementation Steps

1. Remove Migration Execution from Database Layer

File: file:codeframe/persistence/database.py

• Remove the _run_migrations() method (lines 650-718) entirely
• Remove the run_migrations parameter from initialize() method signature (line 84)
• Remove the deprecation comment about migrations (lines 88-90)
• Remove the schema_migrations table creation from _create_schema() if it exists
• Verify that _create_schema() contains the complete flattened schema (it already does based on lines 104-648)

2. Delete Migration Infrastructure Files

Directory: file:codeframe/persistence/migrations/

Remove the entire migrations directory and its contents:

• file:codeframe/persistence/migrations/__init__.py - Migration base classes and runner
• file:codeframe/persistence/migrations/README.md - Migration system documentation
• file:codeframe/persistence/migrations/archive/migration_001_remove_agent_type_constraint.py
• file:codeframe/persistence/migrations/archive/migration_002_refactor_projects_schema.py
• file:codeframe/persistence/migrations/archive/migration_003_update_blockers_schema.py
• file:codeframe/persistence/migrations/archive/migration_004_add_context_checkpoints.py
• file:codeframe/persistence/migrations/archive/migration_005_add_context_indexes.py
• file:codeframe/persistence/migrations/archive/migration_006_mvp_completion.py
• file:codeframe/persistence/migrations/archive/migration_007_sprint10_review_polish.py
• file:codeframe/persistence/migrations/archive/migration_008_add_session_id.py
• file:codeframe/persistence/migrations/archive/migration_009_add_project_agents.py
• file:codeframe/persistence/migrations/archive/migration_010_pause_functionality.py
• file:codeframe/persistence/migrations/archive/migration_011_created_at_not_null.py

3. Remove Migration-Specific Test Files

Delete test files that specifically test migrations:

• file:tests/persistence/test_migration_001.py
• file:tests/persistence/test_migration_006.py
• file:tests/persistence/test_migration_010.py
• file:tests/persistence/test_migration_011.py
• file:tests/agents/test_bash_operations_migration.py
• file:tests/agents/test_file_operations_migration.py

4. Update Test Files Using run_migrations Parameter

Remove or update run_migrations parameter usage in test files:

Files to update:

• file:codeframe/lib/checkpoint_manager.py (line 561) - Remove run_migrations=False
• file:codeframe/tasks/expire_blockers.py (line 46) - Remove run_migrations=False
• file:tests/agents/test_backend_worker_agent.py (lines 1489, 1617) - Remove run_migrations=True
• file:tests/blockers/test_blocker_expiration.py (lines 24, 53) - Remove run_migrations=False
• file:tests/blockers/test_blocker_expiration_cron.py (lines 31, 48, 83, 100) - Remove run_migrations=False
• file:tests/blockers/test_blocker_expiration_simple.py (line 19) - Remove run_migrations=False
• file:tests/core/test_project_get_status.py (line 35) - Remove run_migrations=False
• file:tests/integration/test_auto_commit_workflow.py (line 51) - Remove run_migrations=True
• file:tests/integration/test_composite_index.py (lines 141, 154) - Remove run_migrations=False
• file:tests/integration/test_mvp_completion_workflow.py (line 58) - Remove run_migrations=True
• file:tests/persistence/test_database_typed_returns.py (lines 232, 302) - Remove run_migrations=False

Change all db.initialize(run_migrations=True/False) calls to simply db.initialize().

5. Remove Migration Verification Script

Delete the migration verification script:

• file:scripts/verify_migration_001.py

6. Update Documentation Files

Remove or update migration references in documentation:

Files to update:

• file:claudedocs/MIGRATION_001_SUMMARY.md - Delete entire file
• file:docs/meta/MIGRATION_SUMMARY.md - Keep (it's about documentation restructuring, not DB migrations)
• file:CLAUDE.md - Remove migration references (line 193: "Manual SQL migrations (no Alembic yet)")
• file:PRD.md - Update line 136 to remove "+ migrations" reference
• file:CODEFRAME_ISSUES_ANALYSIS.md - Remove "Missing Migration Documentation" section (line 144)
• file:E2E_TESTS_FIX_PLAN.md - Remove "Database Migration Warnings" section (line 17)
• file:FASTAPI_ROUTER_REFACTORING_TEST_REPORT.md - Update coverage analysis to remove migration script references (line 48)
• file:PHASE_10_SUMMARY.md - Remove "Add migration test coverage" from medium-term tasks (line 124)

Documentation files with historical migration references (keep for historical context):

• Files in file:claudedocs/ directory that describe past migration work
• Files in file:docs/archive/ directory
• Sprint documentation files

7. Update Deployment Scripts

File: file:scripts/deploy.sh

Remove the migration reference from the deployment simulation output (line 26: "2. Run database migrations").

8. Verify Database Schema Completeness

File: file:codeframe/persistence/database.py

Ensure _create_schema() method contains all necessary tables and indexes from the flattened schema. Based on the file summary, it already includes:

• 15+ tables: projects, issues, tasks, agents, project_agents, blockers, lint_results, memory, context_items, checkpoints, context_checkpoints, changelog, git_branches, deployments, test_results, correction_attempts, task_dependencies, code_reviews, token_usage
• All necessary indexes and constraints

No changes needed here as the schema is already complete.

9. Update Comments and Docstrings

File: file:codeframe/persistence/database.py

Update the class docstring (lines 36-76) to remove any references to migrations in the usage examples or documentation.

Summary Table

Component	Action	Files Affected
Database Layer	Remove migration execution logic	1 file (database.py)
Migration Files	Delete entire directory	13 files (migrations/)
Migration Tests	Delete test files	6 files
Test Parameter Usage	Remove run_migrations parameter	12 files
Scripts	Delete verification script	1 file
Documentation	Remove/update references	8 files
Deployment Scripts	Update deployment output	1 file

Architecture Diagram

graph TD
    A[Database.initialize] -->|Creates| B[Flattened v1.0 Schema]
    B --> C[All Tables & Indexes]
    
    D[Old System] -.->|REMOVED| E[_run_migrations]
    D -.->|REMOVED| F[Migration Files]
    D -.->|REMOVED| G[schema_migrations Table]
    D -.->|REMOVED| H[Migration Tests]
    D -.->|REMOVED| I[Migration Docs]
    
    style D fill:#ffcccc,stroke:#ff0000
    style E fill:#ffcccc,stroke:#ff0000
    style F fill:#ffcccc,stroke:#ff0000
    style G fill:#ffcccc,stroke:#ff0000
    style H fill:#ffcccc,stroke:#ff0000
    style I fill:#ffcccc,stroke:#ff0000
    
    style A fill:#ccffcc,stroke:#00ff00
    style B fill:#ccffcc,stroke:#00ff00
    style C fill:#ccffcc,stroke:#00ff00

Loading

Import In IDE

🤖 Prompt for AI Agents

## Observations

The codebase has a migration system that was used during development but is now deprecated. The `Database._create_schema()` method already contains the flattened v1.0 schema with all historical migrations incorporated. The `run_migrations` parameter in `Database.initialize()` is marked as deprecated (line 88-90 in database.py), but the migration infrastructure (`_run_migrations()` method, migration files, tests, and documentation) still exists throughout the codebase. There are 11 migration files in the archive directory, migration-specific tests, documentation, and a verification script.

## Approach

The plan follows a systematic removal approach: first eliminate the migration execution logic and tracking table from the database layer, then remove all migration files and infrastructure, update all test files to remove migration-related code, clean up documentation references, and finally remove the deprecated `run_migrations` parameter. This ensures a clean removal without breaking existing functionality, as the flattened schema in `_create_schema()` already contains all necessary table definitions.

## Implementation Steps

### 1. Remove Migration Execution from Database Layer

**File: `file:codeframe/persistence/database.py`**

- Remove the `_run_migrations()` method (lines 650-718) entirely
- Remove the `run_migrations` parameter from `initialize()` method signature (line 84)
- Remove the deprecation comment about migrations (lines 88-90)
- Remove the `schema_migrations` table creation from `_create_schema()` if it exists
- Verify that `_create_schema()` contains the complete flattened schema (it already does based on lines 104-648)

### 2. Delete Migration Infrastructure Files

**Directory: `file:codeframe/persistence/migrations/`**

Remove the entire migrations directory and its contents:
- `file:codeframe/persistence/migrations/__init__.py` - Migration base classes and runner
- `file:codeframe/persistence/migrations/README.md` - Migration system documentation
- `file:codeframe/persistence/migrations/archive/migration_001_remove_agent_type_constraint.py`
- `file:codeframe/persistence/migrations/archive/migration_002_refactor_projects_schema.py`
- `file:codeframe/persistence/migrations/archive/migration_003_update_blockers_schema.py`
- `file:codeframe/persistence/migrations/archive/migration_004_add_context_checkpoints.py`
- `file:codeframe/persistence/migrations/archive/migration_005_add_context_indexes.py`
- `file:codeframe/persistence/migrations/archive/migration_006_mvp_completion.py`
- `file:codeframe/persistence/migrations/archive/migration_007_sprint10_review_polish.py`
- `file:codeframe/persistence/migrations/archive/migration_008_add_session_id.py`
- `file:codeframe/persistence/migrations/archive/migration_009_add_project_agents.py`
- `file:codeframe/persistence/migrations/archive/migration_010_pause_functionality.py`
- `file:codeframe/persistence/migrations/archive/migration_011_created_at_not_null.py`

### 3. Remove Migration-Specific Test Files

Delete test files that specifically test migrations:
- `file:tests/persistence/test_migration_001.py`
- `file:tests/persistence/test_migration_006.py`
- `file:tests/persistence/test_migration_010.py`
- `file:tests/persistence/test_migration_011.py`
- `file:tests/agents/test_bash_operations_migration.py`
- `file:tests/agents/test_file_operations_migration.py`

### 4. Update Test Files Using `run_migrations` Parameter

Remove or update `run_migrations` parameter usage in test files:

**Files to update:**
- `file:codeframe/lib/checkpoint_manager.py` (line 561) - Remove `run_migrations=False`
- `file:codeframe/tasks/expire_blockers.py` (line 46) - Remove `run_migrations=False`
- `file:tests/agents/test_backend_worker_agent.py` (lines 1489, 1617) - Remove `run_migrations=True`
- `file:tests/blockers/test_blocker_expiration.py` (lines 24, 53) - Remove `run_migrations=False`
- `file:tests/blockers/test_blocker_expiration_cron.py` (lines 31, 48, 83, 100) - Remove `run_migrations=False`
- `file:tests/blockers/test_blocker_expiration_simple.py` (line 19) - Remove `run_migrations=False`
- `file:tests/core/test_project_get_status.py` (line 35) - Remove `run_migrations=False`
- `file:tests/integration/test_auto_commit_workflow.py` (line 51) - Remove `run_migrations=True`
- `file:tests/integration/test_composite_index.py` (lines 141, 154) - Remove `run_migrations=False`
- `file:tests/integration/test_mvp_completion_workflow.py` (line 58) - Remove `run_migrations=True`
- `file:tests/persistence/test_database_typed_returns.py` (lines 232, 302) - Remove `run_migrations=False`

Change all `db.initialize(run_migrations=True/False)` calls to simply `db.initialize()`.

### 5. Remove Migration Verification Script

Delete the migration verification script:
- `file:scripts/verify_migration_001.py`

### 6. Update Documentation Files

Remove or update migration references in documentation:

**Files to update:**
- `file:claudedocs/MIGRATION_001_SUMMARY.md` - Delete entire file
- `file:docs/meta/MIGRATION_SUMMARY.md` - Keep (it's about documentation restructuring, not DB migrations)
- `file:CLAUDE.md` - Remove migration references (line 193: "Manual SQL migrations (no Alembic yet)")
- `file:PRD.md` - Update line 136 to remove "+ migrations" reference
- `file:CODEFRAME_ISSUES_ANALYSIS.md` - Remove "Missing Migration Documentation" section (line 144)
- `file:E2E_TESTS_FIX_PLAN.md` - Remove "Database Migration Warnings" section (line 17)
- `file:FASTAPI_ROUTER_REFACTORING_TEST_REPORT.md` - Update coverage analysis to remove migration script references (line 48)
- `file:PHASE_10_SUMMARY.md` - Remove "Add migration test coverage" from medium-term tasks (line 124)

**Documentation files with historical migration references (keep for historical context):**
- Files in `file:claudedocs/` directory that describe past migration work
- Files in `file:docs/archive/` directory
- Sprint documentation files

### 7. Update Deployment Scripts

**File: `file:scripts/deploy.sh`**

Remove the migration reference from the deployment simulation output (line 26: "2. Run database migrations").

### 8. Verify Database Schema Completeness

**File: `file:codeframe/persistence/database.py`**

Ensure `_create_schema()` method contains all necessary tables and indexes from the flattened schema. Based on the file summary, it already includes:
- 15+ tables: projects, issues, tasks, agents, project_agents, blockers, lint_results, memory, context_items, checkpoints, context_checkpoints, changelog, git_branches, deployments, test_results, correction_attempts, task_dependencies, code_reviews, token_usage
- All necessary indexes and constraints

No changes needed here as the schema is already complete.

### 9. Update Comments and Docstrings

**File: `file:codeframe/persistence/database.py`**

Update the class docstring (lines 36-76) to remove any references to migrations in the usage examples or documentation.

## Summary Table

| Component | Action | Files Affected |
|-----------|--------|----------------|
| Database Layer | Remove migration execution logic | 1 file (database.py) |
| Migration Files | Delete entire directory | 13 files (migrations/) |
| Migration Tests | Delete test files | 6 files |
| Test Parameter Usage | Remove `run_migrations` parameter | 12 files |
| Scripts | Delete verification script | 1 file |
| Documentation | Remove/update references | 8 files |
| Deployment Scripts | Update deployment output | 1 file |

## Architecture Diagram

```mermaid
graph TD
    A[Database.initialize] -->|Creates| B[Flattened v1.0 Schema]
    B --> C[All Tables & Indexes]
    
    D[Old System] -.->|REMOVED| E[_run_migrations]
    D -.->|REMOVED| F[Migration Files]
    D -.->|REMOVED| G[schema_migrations Table]
    D -.->|REMOVED| H[Migration Tests]
    D -.->|REMOVED| I[Migration Docs]
    
    style D fill:#ffcccc,stroke:#ff0000
    style E fill:#ffcccc,stroke:#ff0000
    style F fill:#ffcccc,stroke:#ff0000
    style G fill:#ffcccc,stroke:#ff0000
    style H fill:#ffcccc,stroke:#ff0000
    style I fill:#ffcccc,stroke:#ff0000
    
    style A fill:#ccffcc,stroke:#00ff00
    style B fill:#ccffcc,stroke:#00ff00
    style C fill:#ccffcc,stroke:#00ff00
```

---

Execution Information

Branch: main
Commit: a8ace58

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!