memora submodule

[nitheesh1122]

Summary

Brief description of what this PR accomplishes.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Performance improvement
• Refactoring (no functional changes)
• Documentation update
• Test improvements
• CI/CD improvements

Related Issues

Fixes #(issue number)
Addresses #(issue number)

Changes Made

• List key changes made in this PR
• Include any new files, deleted files, or major modifications
• Mention any architectural decisions or trade-offs

Layer Impact

Which layers of Memora are affected by this change?

• Layer 1 - Personal Memory (conversation facts, conflicts, versioning)
• Layer 2 - Document Intelligence (PDF/Word/CSV extraction)
• Layer 3 - Project Memory (branches, pack export/import, team sharing)
• Layer 4 - Code Intelligence (AST extraction, incremental ingestion)
• Layer 5 - Memory Health (decay, health score, reinforce)
• Infrastructure (CI/CD, packaging, deployment)
• Documentation

Testing

• Unit tests pass (poetry run pytest)
• Integration tests pass
• Manual testing performed
• Performance impact assessed (if applicable)

Test Coverage

• New code has appropriate test coverage
• Existing test coverage maintained or improved
• Edge cases covered

Manual Testing Steps

1. Step one
2. Step two
3. Step three

Performance Impact

• No performance impact
• Performance improvement (describe)
• Potential performance regression (explain mitigation)

Breaking Changes

If this includes breaking changes, list them here and describe migration path for users.

Documentation

• Code is self-documenting with clear names and structure
• Public APIs have docstrings
• README updated (if needed)
• CLI help text updated (if needed)
• Architecture docs updated (if needed)

Dependencies

• No new dependencies
• New dependencies added (list them and justify)
• Dependencies updated (explain why)

Security Considerations

• No security implications
• Security implications considered and addressed
• Security review required

Screenshots/Examples (if applicable)

Include screenshots, CLI output, or code examples that demonstrate the changes.

Checklist

• I have read the contributing guidelines
• My code follows the project's style guidelines
• I have performed a self-review of my code
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally
• Any dependent changes have been merged and published

Additional Notes

Any other information that reviewers should know about this PR.