fix(models): add missing theme_id FK to Project model

[RegardV]

User description

Summary

• Adds missing theme_id FK column to Project model (references themes.id, nullable)
• Adds theme relationship on Project
• Fixes runtime errors when theme-related API endpoints are called

🤖 Generated with Claude Code

---

PR Type

Bug fix

---

Description

• Adds missing theme_id foreign key column to Project model

• Establishes relationship between Project and Theme entities

• Resolves runtime errors in theme-related API endpoints

---

Diagram Walkthrough

flowchart LR
  Project["Project Model"]
  Theme["Theme Model"]
  Project -- "theme_id FK" --> Theme
  Project -- "theme relationship" --> Theme

Loading

File Walkthrough

	Relevant files
Bug fix	project.py Add theme_id FK and relationship to Project                            journal-platform-backend/app/models/project.py Adds theme_id column as nullable foreign key referencing themes.id Adds theme relationship property to enable access to related Theme objects Maintains existing relationships and model structure +2/-0

---

[qodo-code-review]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: review

Failed stage: Set up job [❌]

Failed test name: ""

Failure summary: The workflow failed during action preparation because GitHub Actions could not download the referenced action qodo-ai/pr-agent@v0.29.0. - Error: Unable to resolve action 'qodo-ai/pr-agent@v0.29.0', unable to find version 'v0.29.0' - This indicates the tag/branch v0.29.0 does not exist (or is not accessible) in the qodo-ai/pr-agent repository, so the runner cannot resolve the action version.

Relevant error logs: 1: ##[group]Runner Image Provisioner 2: Hosted Compute Agent ... 13: ##[group]Runner Image 14: Image: ubuntu-24.04 15: Version: 20260201.15.1 16: Included Software: https://github.com/actions/runner-images/blob/ubuntu24/20260201.15/images/ubuntu/Ubuntu2404-Readme.md 17: Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20260201.15 18: ##[endgroup] 19: ##[group]GITHUB_TOKEN Permissions 20: Contents: read 21: Metadata: read 22: Packages: read 23: ##[endgroup] 24: Secret source: Actions 25: Prepare workflow directory 26: Prepare all required actions 27: Getting action download info 28: ##[error]Unable to resolve action `qodo-ai/pr-agent@v0.29.0`, unable to find version `v0.29.0`

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Index foreign key column Add index=True to the theme_id column to improve query performance when looking up projects by theme. journal-platform-backend/app/models/project.py [19] -theme_id = Column(Integer, ForeignKey('themes.id'), nullable=True) +theme_id = Column(Integer, ForeignKey('themes.id'), nullable=True, index=True) Apply / Chat Suggestion importance[1-10]: 7 __ Why: This is a valid performance improvement, as adding an index to the theme_id foreign key will speed up queries that filter or join on this column.	Medium
	Add ondelete behavior Add ondelete='SET NULL' to the theme_id foreign key to automatically nullify the reference if the associated theme is deleted. journal-platform-backend/app/models/project.py [19] -theme_id = Column(Integer, ForeignKey('themes.id'), nullable=True) +theme_id = Column(Integer, ForeignKey('themes.id', ondelete='SET NULL'), nullable=True) Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly proposes adding ondelete='SET NULL', which is appropriate for a nullable foreign key and improves data integrity by defining explicit behavior when a related theme is deleted.	Medium
	Establish a bidirectional ORM relationship Add back_populates="projects" to the theme relationship to make it bidirectional, ensuring consistency with other relationships in the model. journal-platform-backend/app/models/project.py [82] -theme = relationship("Theme", foreign_keys=[theme_id]) +theme = relationship("Theme", back_populates="projects", foreign_keys=[theme_id]) Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies that making the new theme relationship bidirectional with back_populates aligns with existing patterns in the model and is a good practice for SQLAlchemy ORM.	Low
More