Skip to content

docs: correct Preflight TTL mechanism in ADR 002#2477

Merged
GeezerPelletier merged 2 commits into
mainfrom
docs/fix-preflight-ttl-adr
May 25, 2026
Merged

docs: correct Preflight TTL mechanism in ADR 002#2477
GeezerPelletier merged 2 commits into
mainfrom
docs/fix-preflight-ttl-adr

Conversation

@GeezerPelletier
Copy link
Copy Markdown
Contributor

@GeezerPelletier GeezerPelletier commented May 22, 2026

Corrects the TTL/expiry description in ADR 002 to reflect the actual implementation.

withRecordExpiry is a DynamoDB-era SchemaBuilder helper marked postgrestIgnore in the v3 PostgreSQL layer - it never writes to the database. The preflights table has no record_expires_at column. Cleanup is handled by ON DELETE CASCADE on async_job_id.

Companion to:

Generated with Claude Code

withRecordExpiry is DynamoDB-era and postgrestIgnore in v3 - no TTL column
exists on the preflights table. Expiry is via ON DELETE CASCADE on async_job_id.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@codecov
Copy link
Copy Markdown

codecov Bot commented May 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copy link
Copy Markdown

@MysticatBot-Dev MysticatBot-Dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @GeezerPelletier,

Strengths

  • Corrects ADR 002 to reflect the actual PostgreSQL implementation rather than leaving DynamoDB-era assumptions in the design record (docs/decisions/002-preflight-api-rest-redesign.md:305-309)
  • Clear explanation of the real expiry mechanism (ON DELETE CASCADE) and why withRecordExpiry is a no-op in the v3 layer
  • Well-scoped companion PR that keeps documentation in sync with the data-service and shared library changes

Assessment

Ready to merge? Yes
Reasoning: This is a factual correction to an ADR, aligning the documented TTL mechanism with the actual PostgreSQL implementation. The change is accurate, well-explained, and ships alongside the companion PRs that established the correct behavior. CI is green.


Skill: pr-review | Model: us.anthropic.claude-opus-4-6-v1[1m] | Duration: 1m 22s | Cost: $0.50 | Commit: 269e96bac61d0060faa803117d8e8c22035cbd90
If this code review was useful, please react with 👍. Otherwise, react with 👎.

@MysticatBot-Dev MysticatBot-Dev added the ai-reviewed Reviewed by AI label May 23, 2026
MysticatBot-Dev

This comment was marked as duplicate.

@github-actions
Copy link
Copy Markdown

This PR will trigger no release when merged.

@GeezerPelletier GeezerPelletier merged commit a4bc337 into main May 25, 2026
20 checks passed
@GeezerPelletier GeezerPelletier deleted the docs/fix-preflight-ttl-adr branch May 25, 2026 11:02
GeezerPelletier pushed a commit that referenced this pull request May 25, 2026
Resolves conflict between ADR-002 Data Model section extraction (our branch)
and the TTL correction landed in main (#2477). ADR-002 keeps the short
reference to ADR-003; the ON DELETE CASCADE expiry correction is applied
directly into ADR-003 where the entity design now lives.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@solaris007
Copy link
Copy Markdown
Member

🎉 This PR is included in version 1.513.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants