feat: show cutoff-known post body beside the live rewrite (v2.1.0) - #218
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
Open a marked Demo public post from the Demo Corp lineage run and the
January follow-up sits under Body this run knew; the live body names
the later delivery window. GET /api/posts/{id}?as_of= reads
source_post_revision. A missing cover is omitted. Do not invent a
cutoff sentence or a TEPP theta.
66ce369 to
516f49f
Compare
bda10d6
into
feat/role-responsibility-agent-ontology
Buyer impact
Opening a title marked Updated after cutoff now shows the body that run knew beside the live rewrite. After
make seed, open Lineage reconstruction · Succeeded · Demo Corp, then Demo public post: Body this run knew is the January follow-up; the live body names the later delivery window. Compare those two texts. Demo private post stays unmarked and has no second text.Scope
0024_source_post_revision.sql(ADR 0025) stores each title/body rewrite as a half-open valid-time interval. Clock-only updates do not pretend to be a rewrite.GET /api/posts/{id}?as_of=returnsknown_atwhen a revision covers that clock. The livepost_bodystays the live row. A missing cover is omitted — never a fabricated cutoff sentence.Base
Rebased onto #74 exact head
d4d1048(v2.0.0, includes #216). Do not merge before #74. Do not mix leftover pairs (#211) or #215 into this branch. Do not add commits to #74 or #92.Review
Do not self-approve. Squash-merge only with independent current-head APPROVE and exact-head required success.
Verify
Frontend: oxlint clean, 67 passed. Python contract tests: 6 passed (16 skipped without local Postgres).