feat(snowflake): adapt to derived DDL with typed options and comment support

.gitattributes

@@ -0,0 +1,11 @@
+* text=auto eol=lf
+*.py text eol=lf
+*.md text eol=lf
+*.yml text eol=lf
+*.yaml text eol=lf
+*.toml text eol=lf
+*.cfg text eol=lf
+*.ini text eol=lf
+*.sh text eol=lf
+*.bat text eol=crlf
+*.ps1 text eol=lf

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,72 @@
+---
+name: Bug Report
+about: Report a bug in the rhosocial ActiveRecord Snowflake backend
+title: '[BUG] '
+labels: 'bug'
+assignees: ''
+---
+
+## Before Submitting
+
+Please ensure this bug is specific to the Snowflake backend. For behavior shared by all database backends, please submit the bug report to the core `rhosocial-activerecord` repository instead.
+
+## Description
+
+A clear and concise description of the bug.
+
+## Environment
+
+- **rhosocial-activerecord-snowflake Version**: [e.g. 1.0.0.dev2]
+- **Python Version**: [e.g. 3.14]
+- **Snowflake Connector Version**: [e.g. 3.17.0]
+- **Snowflake Account/Region**: [e.g. account/region]
+- **Warehouse/Database/Schema**: [e.g. warehouse/database/schema]
+- **OS**: [e.g. Linux, macOS, Windows]
+
+## Steps to Reproduce
+
+1.
+2.
+3.
+
+## Expected Behavior
+
+A clear and concise description of what you expected to happen.
+
+## Actual Behavior
+
+What actually happened instead of the expected behavior.
+
+## Database Query
+
+If applicable, provide the generated SQL query that causes the issue:
+
+```sql
+-- Your problematic SQL query here
+```
+
+## Model Definition
+
+If the issue is related to a specific model, please share your model definition:
+
+```python
+# Example model definition
+class User(ActiveRecord):
+    __table_name__ = 'users'
+
+    id: Optional[int] = None
+    name: str
+    email: EmailStr
+```
+
+## Error Details
+
+If you're getting an error, include the full error message and stack trace:
+
+```
+Paste the full error message here
+```
+
+## Additional Context
+
+Any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,52 @@
+---
+name: Feature Request
+about: Suggest a feature for the rhosocial ActiveRecord Snowflake backend
+title: '[FEATURE] '
+labels: 'enhancement'
+assignees: ''
+---
+
+## Before Submitting
+
+Please ensure this feature request is specific to the Snowflake backend. For functionality that should behave consistently across all database backends, please submit the request to the core `rhosocial-activerecord` repository instead.
+
+## Description
+
+A clear and concise description of the desired feature.
+
+## Problem Statement
+
+Is your feature request related to a specific problem? Please describe.
+
+## Proposed Solution
+
+Describe the solution you'd like to see implemented.
+
+## Use Cases
+
+What specific use cases would this feature address?
+
+1.
+2.
+
+## Snowflake Scope
+
+Which Snowflake areas should this feature support? (Select all that apply)
+
+- [ ] Snowflake SQL dialect and expressions
+- [ ] Snowflake data types and adapters
+- [ ] Snowflake connection, pool, or transaction behavior
+- [ ] Snowflake DDL, DML, or warehouse features
+- [ ] Snowflake test providers and CI
+
+## Technical Considerations
+
+Are there any technical constraints or considerations for implementing this feature?
+
+## Comparison with Alternatives
+
+How does this feature compare to alternative approaches?
+
+## Additional Context
+
+Add any other context or examples about the feature request here.

.github/PULL_REQUEST_TEMPLATE/bugfix_template.md

@@ -0,0 +1,110 @@
+---
+name: "Bugfix Pull Request"
+about: Propose a bug fix for the rhosocial-activerecord Snowflake backend, targeting a pre-release branch (e.g., release/vX.Y.Z).
+title: "fix(<scope>): <description>"
+labels: "bug"
+assignees: ""
+---
+
+## Description
+
+<!--
+Please include a summary of the bug and the fix.
+Describe the impact of the bug and why this fix addresses it.
+-->
+
+Fixes # (issue)
+
+## Reproduction Steps
+
+<!--
+Please provide clear and detailed steps to reproduce the bug.
+This is crucial for verifying the fix. Include code snippets, configurations,
+and expected vs. actual behavior.
+-->
+
+1.
+2.
+3.
+
+## Type of change
+
+<!--
+Please delete options that are not relevant.
+Remember to follow the Conventional Commits specification.
+-->
+
+- [ ] `fix`: A bug fix
+- [ ] `docs`: Documentation only changes (if related to the bug or fix)
+- [ ] `test`: Adding missing tests or correcting existing tests (for the bug or fix)
+- [ ] `refactor`: A code change that neither fixes a bug nor adds a feature (if part of the fix)
+- [ ] `perf`: A code change that improves performance (if part of the fix)
+- [ ] `chore`: Changes to the build process or auxiliary tools and libraries such as documentation generation (if related to the bug or fix)
+- [ ] `ci`: Changes to our CI configuration files and scripts (if related to the bug or fix)
+- [ ] `build`: Changes that affect the build system or external dependencies (if related to the bug or fix)
+- [ ] `revert`: Reverts a previous commit
+
+## Breaking Change
+
+<!--
+Does this PR introduce a breaking change?
+- If YES, please describe the impact and migration path for existing applications.
+- If NO, please indicate N/A.
+-->
+
+- [ ] Yes, for end-users (backward-incompatible API changes)
+- [ ] Yes, for backend developers (internal architectural changes that may affect custom implementations)
+- [ ] No breaking changes
+(If Yes, please describe the impact and migration path below):
+
+**Impact on End-Users:**
+<!-- Describe backward-incompatible changes for typical end-user applications consuming the public API. If none, state "No backward-incompatible changes are expected for typical end-user applications." -->
+
+**Impact on Backend Developers (Custom Implementations):**
+<!-- Describe backward-incompatible changes for developers with custom backend implementations or those directly interacting with internal mechanisms. If none, state "No backward-incompatible changes are expected for backend developers using custom implementations." -->
+
+
+
+## Related Repositories/Packages
+
+<!--
+If this change affects other repositories in the rhosocial-activerecord ecosystem (e.g., core, testsuite, or another backend),
+please list them and describe the coordinated changes needed.
+-->
+
+
+## Testing
+
+<!--
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
+Also, list any relevant configuration details (e.g., Snowflake connector version, Python version).
+-->
+
+- [ ] I have added new tests to cover my changes.
+- [ ] I have updated existing tests to reflect my changes.
+- [ ] All existing tests pass.
+- [ ] This change has been tested on [specify backend/DB versions].
+
+**Test Plan:**
+<!-- e.g., "Ran `pytest tests/rhosocial/activerecord_test/bug/my_bug_fix.py`" -->
+
+
+## Checklist
+
+<!--
+Go over all the following points, and put an `x` in all the boxes that apply.
+If you're unsure about any of these, don't hesitate to ask. We're here to help!
+-->
+
+- [ ] My code follows the project's code style guidelines in `.claude/code_style.md`.
+- [ ] I have performed a self-review of my own code.
+- [ ] I have commented my code, particularly in hard-to-understand areas.
+- [ ] I have made corresponding changes to the documentation (Docstrings, `README.md`, etc.).
+- [ ] My changes generate no new warnings.
+- [ ] I have added a Changelog fragment as described in `.claude/version_control.md` (`changelog.d/<issue_number>.<type>.md`).
+- [ ] I have verified that my changes do not introduce SQL injection vulnerabilities.
+- [ ] I have checked for potential performance regressions.
+
+## Additional Notes
+
+<!-- Any additional information, context, or questions for reviewers. -->

.github/PULL_REQUEST_TEMPLATE/feature_template.md

@@ -0,0 +1,97 @@
+---
+name: "Feature Pull Request"
+about: Propose a new feature for the rhosocial-activerecord Snowflake backend, targeting a pre-release branch (e.g., release/vX.Y.Z).
+title: "feat(<scope>): <description>"
+labels: "enhancement"
+assignees: ""
+---
+
+## Description
+
+<!--
+Please include a summary of the new feature and its motivation.
+Describe the problem it solves or the new capability it provides.
+List any dependencies that are required for this change.
+-->
+
+Adds # (issue)
+
+## Type of change
+
+<!--
+Please delete options that are not relevant.
+Remember to follow the Conventional Commits specification.
+-->
+
+- [ ] `feat`: A new feature
+- [ ] `docs`: Documentation only changes (if related to the new feature)
+- [ ] `perf`: A code change that improves performance (if part of the feature)
+- [ ] `test`: Adding missing tests or correcting existing tests (for the new feature)
+- [ ] `chore`: Changes to the build process or auxiliary tools and libraries such as documentation generation (if related to the new feature)
+- [ ] `ci`: Changes to our CI configuration files and scripts (if related to the new feature)
+- [ ] `build`: Changes that affect the build system or external dependencies (if related to the new feature)
+- [ ] `revert`: Reverts a previous commit
+
+## Breaking Change
+
+<!--
+Does this PR introduce a breaking change?
+- If YES, please describe the impact and migration path for existing applications.
+- If NO, please indicate N/A.
+-->
+
+- [ ] Yes, for end-users (backward-incompatible API changes)
+- [ ] Yes, for backend developers (internal architectural changes that may affect custom implementations)
+- [ ] No breaking changes
+(If Yes, please describe the impact and migration path below):
+
+**Impact on End-Users:**
+<!-- Describe backward-incompatible changes for typical end-user applications consuming the public API. If none, state "No backward-incompatible changes are expected for typical end-user applications." -->
+
+**Impact on Backend Developers (Custom Implementations):**
+<!-- Describe backward-incompatible changes for developers with custom backend implementations or those directly interacting with internal mechanisms. If none, state "No backward-incompatible changes are expected for backend developers using custom implementations." -->
+
+
+## Related Repositories/Packages
+
+<!--
+If this change affects other repositories in the rhosocial-activerecord ecosystem (e.g., core, testsuite, or another backend),
+please list them and describe the coordinated changes needed.
+-->
+
+
+## Testing
+
+<!--
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
+Also, list any relevant configuration details (e.g., Snowflake connector version, Python version).
+-->
+
+- [ ] I have added new tests to cover my changes.
+- [ ] I have updated existing tests to reflect my changes.
+- [ ] All existing tests pass.
+- [ ] This change has been tested on [specify backend/DB versions].
+
+**Test Plan:**
+<!-- e.g., "Ran `pytest tests/rhosocial/activerecord_test/feature/my_new_feature.py`" -->
+
+
+## Checklist
+
+<!--
+Go over all the following points, and put an `x` in all the boxes that apply.
+If you're unsure about any of these, don't hesitate to ask. We're here to help!
+-->
+
+- [ ] My code follows the project's code style guidelines in `.claude/code_style.md`.
+- [ ] I have performed a self-review of my own code.
+- [ ] I have commented my code, particularly in hard-to-understand areas.
+- [ ] I have made corresponding changes to the documentation (Docstrings, `README.md`, etc.).
+- [ ] My changes generate no new warnings.
+- [ ] I have added a Changelog fragment as described in `.claude/version_control.md` (`changelog.d/<issue_number>.<type>.md`).
+- [ ] I have verified that my changes do not introduce SQL injection vulnerabilities.
+- [ ] I have checked for potential performance regressions.
+
+## Additional Notes
+
+<!-- Any additional information, context, or questions for reviewers. -->