Skip to content

feat(etl): rebuild replay on refreshed cancellation stack - #256

Draft
seonghobae wants to merge 8 commits into
repair/durable-job-cancellation-894e1fdfrom
repair/durable-job-replay-1fd2691
Draft

feat(etl): rebuild replay on refreshed cancellation stack#256
seonghobae wants to merge 8 commits into
repair/durable-job-cancellation-894e1fdfrom
repair/durable-job-replay-1fd2691

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

Stack repair

This Draft repairs the next invalid durable-job boundary without rewriting old PR #148. Its immediate predecessor is refreshed cancellation PR #254 at exact head 1fd2691dde1ebfd235c53703e6018eee11249f04; old #148 still targets the obsolete #147 branch and therefore cannot prove ancestry from the refreshed cancellation implementation. No #148 check, review, approval, status or synthetic-merge evidence transfers.

TDD phase

Exact first head 121654bfa463f90e2d64222f9ca60f1750a33e0e adds only EtlJobReplayBoundaryTest from the preserved replay work. The test reaches the production replay boundary by requiring EtlJobReplay and EtlJobReplayService, which are intentionally absent on the refreshed cancellation ancestry. The required first hosted result is RED at missing replay production types/contract after normal production compilation; setup, dependency, fixture or runner failure does not qualify.

After a valid RED, rebuild only the bounded replay production surface and then the persistence/state tests from #148 through auditable GREEN commits, proving exact file/semantic preservation before considering #148 superseded. Do not claim the larger obsolete #135 replay design, migrations, HTTP exposure or release semantics that #148 itself had not rebuilt.

No force-push, destructive rebase, ours/theirs shortcut, gate weakening, stale-evidence transfer, protection bypass or cross-repository write is permitted.

@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b1780914-e1d1-4b7d-90b7-9681fb365ec2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@opencode-agent opencode-agent Bot added area: ci-cd CI, GitHub Actions, checks, release, or supply chain area: data Database, schema, migration, ETL, or lineage priority: medium Normal-priority or P2 work status: draft Draft pull request type: feature New or expanded product capability labels Aug 22, 2026
@seonghobae seonghobae added the enhancement New feature or request label Sep 7, 2026 — with ChatGPT Codex Connector
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: ci-cd CI, GitHub Actions, checks, release, or supply chain area: data Database, schema, migration, ETL, or lineage enhancement New feature or request priority: medium Normal-priority or P2 work status: draft Draft pull request type: feature New or expanded product capability

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant