Core tables with tuva_last_run as a varchar should be a timestamp

[davidshimamoto]

---

Describe the bug - Required
Some core tables have tuva_last_run as a VARCHAR/STRING, but it should be a TIMESTAMP/DATETIME.

• eligibility
• member_months
• pharmacy_claim

---

Environment - Required

• Tuva project package version (e.g. 0.6.0): 0.15.0
• dbt version (e.g. 1.7):
• dbt type (e.g. dbt cloud or dbt CLI): CLI
• Data warehouse (e.g. Snowflake): DuckDB

---

To Reproduce
Steps to reproduce the behavior:
See table definitions after dbt run

---

Expected behavior
tuva_last_run should be a timestamp or other data type that includes date and time.

---

Screenshots
If applicable, add screenshots to help explain your problem.

---

Additional context
Consider also tracing this back through the lineage and adjusting those as well (e.g. core._stg_claims_eligibility also has this as a varchar).