feat: compare live post write clock with analysis-run cutoff (v0.87.0) by seonghobae · Pull Request #150 · ContextualWisdomLab/LineageWeave

seonghobae · 2026-08-16T16:21:27Z

Buyer gap

ADR 0016 already hid later-created titles from an analysis-run detail, but every remaining title still carried a generic “the live body may have changed” warning. After make seed, source_post.updated_at defaulted to now, so the operator could not tell which January titles were actually rewritten after the run.

What the operator sees

Stacked on current #74 (7f2d4bc). Do not merge before #74.

GET /api/analysis-runs/{id} still lists only ABAC-visible titles with created_at <= knowledge_cutoff.
Each title now includes updated_at and live_after_cutoff. No post body, DSN, or source SQL.
After make seed, open Lineage reconstruction · Succeeded · Demo Corp: Demo public post is marked Updated after cutoff (2026-01-13); Demo private post is not.
Opening a marked title still shows the live body. Cutoff body versioning stays a later slice.
List payloads stay aggregates-only.

Boundaries

Synthetic fixtures only. No real-org names or records.
TEPP stays behind tepp_client. This write does not invent a theta.
Null channels stay dropped. Reconstruct grouping keys are unchanged.
No AGENTS.md rewrite. No admin merge retry.

Tests

tests/test_analysis_run_create.py — write clock > cutoff, equal times stay in-cutoff.
backend/tests/test_api.py — edited own-corp title is in the January run; late-created title is not; body is omitted.
frontend/src/App.test.tsx — badge and accessible name only on rewritten titles; pending-create mock now returns the created row on the next list fetch.

Supersedes conflicting draft #131 (same buyer gap, stale #74 base).

cursor · 2026-08-16T16:21:31Z

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.

coderabbitai · 2026-08-16T16:21:37Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 83b5c9e6-a4a3-4b5c-8f99-4c35b37b0ba4

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.}

seonghobae · 2026-08-16T16:22:01Z

Stacked on current #74 7f2d4bc. Do not merge before #74. No admin merge retry.

In-cutoff titles now say whether the live row was rewritten after the run. Demo public post is the edited counter-example; Demo private post still matches the January cutoff. Bodies stay live. TEPP stays behind tepp_client.

Prefer the v0.86.3 disclosure successor over #139. Write-clock stays #150; pending-copy stays #149; retention/Storybook stays #154. Co-authored-by: Seongho Bae <seonghobae@users.noreply.github.com>

seonghobae · 2026-08-16T16:25:01Z

Rebased onto #74 6f79ecb (0.86.2 R&R catalog ids). Changelog keeps both 0.87.0 and 0.86.2. Do not merge before #74.

cursor

Stale comment

Reviewed #150 b4e6d2b as the write-clock landing (ADR 0016). Prefer over #131. Do not merge before #74. Do not invent a theta.

What is sound

Admission clock stays created_at <= knowledge_cutoff on all four scope branches. Write clock is a separate updated_at comparison. Equal times stay in-cutoff evidence.

Naive timestamps are treated as UTC. Detail returns updated_at + live_after_cutoff and still omits post_body.

After make seed, Demo public post is the rewritten counter-example (2026-01-13); Demo private post matches the January cutoff.

Accessible name is Open live post (updated after cutoff): … only on rewritten titles. Unchanged titles stay Open live post: ….

Tests lock > vs ==, the edited own-corp title in the January run, the late-created title out, and no body in the payload.

W3C Time / ISO 8601-1 doctoring on ADR 0016 is updated. List payloads stay aggregates-only.

Before merge
Rebase onto #74 39ed6eb. This head is still based on 6f79ecb. #148 already changed CLAUDE.md (pending lineage sentence) and App.tsx (analysisRunNextAction kind switch + detail next-action). Keep those. Do not drop the pending-lineage sentence while adding the write-clock sentence.

Version 0.87.0 is fine after #153's 0.86.3 person-catalog slice, or land this first and let #153 rebase. Do not give both PRs the same version.

Independent reviewer remains seonghobae. This token cannot self-approve #74 or merge.

_{Sent by Cursor Automation: Fix Issues}

cursor · 2026-08-16T16:30:21Z

+    ``created_at <= knowledge_cutoff`` admits the title. ``updated_at`` is
+    the live write clock (ADR 0016). Equal times stay in-cutoff evidence.
+    """
+    return _as_utc(updated_at) > _as_utc(knowledge_cutoff)


Admission (created_at <= cutoff) and write clock (updated_at > cutoff) stay distinct. Equal times correctly stay in-cutoff. Naive values become UTC.

Next action after rebase onto 39ed6eb: keep all four created_at <= $n filters. Do not let the write-clock mark admit a late-created title. The existing API test (edited January title in, 2026-01-20 title out, no post_body) is the buyer proof.

cursor · 2026-08-16T16:30:21Z

 Digest prefixes stay audible; hover a prefix to read the full digest.
-Opening a cutoff title shows the live post -- compare it with the
-cutoff before treating the body as reconstructed evidence (ADR 0016).
+Opening a cutoff title shows the live post. Titles marked updated


#148 already landed a pending-lineage sentence on #74 39ed6eb just above this block. This patch is against the pre-#148 text.

Next action: rebase onto 39ed6eb and keep both sentences — pending lineage says reconstruction has not started; titles marked updated after cutoff were rewritten after the run. Do not replace one with the other.

seonghobae

Reviewed #150 b4e6d2b as the write-clock landing (ADR 0016). Prefer over draft #131. Do not merge before #74. Do not invent a theta.

Verdict: NEEDS_CHANGES

CodeRabbit GitHub skipped (non-default base). CLI 0.7.3 coderabbit auth login --agent timed out (automatic_login_failed). That skip is not a clean review.

What is sound

Admission stays created_at <= knowledge_cutoff on all four scope branches. Write clock is a separate updated_at > cutoff. Equal times stay in-cutoff evidence. Naive values become UTC.
Detail returns updated_at + live_after_cutoff and still omits post_body. List payloads stay aggregates-only. No DSN or source SQL.
After make seed, Demo public post is stamped 2026-01-13T09:00:00Z; Demo private post matches created_at. Fixture posts set updated_at = occurred.
Accessible name is Open live post (updated after cutoff): … only on rewritten titles. Opening a marked title still shows the live body.
TEPP stays behind tepp_client. Null channels are untouched. Synthetic fixtures only. W3C Time / ISO 8601-1 clocks stay distinct.

Blocking

seeded_db inserts Edited own-corp private post (own-corp, private, in-cutoff). test_post_list_includes_public_and_own_corp_but_excludes_other_corp still exact-sets {"Public post", "Own-corp private post", "Late own-corp private post"} at backend/tests/test_api.py:612. Same class as #110/#114. Add the edited title to that set.

Residual (rebase, not a product defect)

Live #74 is 69c035b, not 6f79ecb. #148 (39ed6eb) already added the pending-lineage sentence and a kind-specific analysisRunNextAction. Retention purge on 69c035b already took 0.87.0 and added an ADR 0020 section to CLAUDE.md. Rebase and keep those. Take 0.87.1 or 0.88.0 — do not ship a second 0.87.0.

Product-gap residuals correctly out of scope

Cutoff body versioning (ADR 0016 later slice).
A source_post.updated_at bump trigger (0001 has default now() only; seed stamps both clocks explicitly).
Showing the write date on the badge (API already returns updated_at; the mark is the next action).
Snapshot source_counts 3 vs two live in-cutoff titles (pre-existing fixture).

Test gaps (residual)

No seed-script lock that Demo public is 2026-01-13 and Demo private is not.
No HTTP assertion for updated_at == cutoff (unit test covers it).
Process-unit / thread-group / all-visible scopes share the comparison loop and are not HTTP-tested for the new fields.

Independent reviewer remains needed. This token cannot self-approve #74 or merge.

seonghobae · 2026-08-16T16:37:28Z

+                "A January post rewritten after the run cutoff.",
+                created_at="2026-01-10T12:00:00Z",
+                updated_at="2026-01-13T09:00:00Z",
+            )


This own-corp private insert is visible on GET /api/posts. test_post_list_includes_public_and_own_corp_but_excludes_other_corp still exact-sets {"Public post", "Own-corp private post", "Late own-corp private post"} at line 612, so the shared seeded_db fixture will fail that test once the live stack is up. Same class as #110/#114. Add Edited own-corp private post to that set. Do not drop this row — it is the buyer proof that an in-cutoff title can still be live_after_cutoff.

seonghobae · 2026-08-16T16:37:29Z

 Digest prefixes stay audible; hover a prefix to read the full digest.
-Opening a cutoff title shows the live post -- compare it with the
-cutoff before treating the body as reconstructed evidence (ADR 0016).
+Opening a cutoff title shows the live post. Titles marked updated


#74 69c035b already has two sentences this patch must not replace: a pending lineage row says reconstruction has not started yet, and the ADR 0020 retention-purge section above the seed block. Rebase onto that head and keep both, then keep this write-clock sentence. Do not drop the pending-lineage line while adding the mark.

seonghobae · 2026-08-16T16:37:30Z

 name = "lineageweave"
-version = "0.86.2"
+version = "0.87.0"
 description = "Reconstructs git-branch-style lineage DAGs from scattered short records using multi-channel score fusion and LLM adjudication."


Live #74 69c035b already shipped 0.87.0 for the granted retention purge (ADR 0020). This head cannot keep the same version after rebase. Take 0.87.1 or 0.88.0 in pyproject.toml, lineageweave/__init__.py, frontend/package.json, uv.lock, and the changelog fragment.

cursor

Reviewed exact head b4e6d2b (rebased onto #74 6f79ecb). CodeRabbit GitHub skipped this non-default base; CodeRabbit CLI cannot authenticate in this environment, so this is a full technical review of the committed diff, not a CodeRabbit result.

What holds

The buyer slice is the right one. created_at <= knowledge_cutoff still admits the title; updated_at > knowledge_cutoff only marks a rewrite. Equal clocks stay in-cutoff. The detail payload stays titles plus clocks — no body, DSN, or source SQL. Seed pins Demo public post to 2026-01-13 and Demo private post to the January create clock. Unit, API, and UI tests cover that counter-example.

Do not merge before #74. Do not treat draft #131 as a second landing vehicle.

Required before merge

Rebase onto current #74 69c035b and take 0.87.1. #74 already shipped 0.87.0 as granted retention purge plus Storybook tokens. This head still claims 0.87.0 (dated 2026-08-17). git merge-tree against 69c035b conflicts in ARCHITECTURE.md, CHANGELOG.md, and the version files. Keep the retention-purge 0.87.0 notes and add this write-clock slice as 0.87.1.
Keep source_post.updated_at honest after a body write. The comparison is correct only if the write clock moves when the live row is rewritten. There is still no trigger (or write-path assignment) that bumps updated_at on post_title / post_body changes while honoring an explicit updated_at in the same statement. Seed then does a body-only UPDATE after the pin. A later product edit, or a trigger that always sets now(), will either hide a rewrite or destroy the Demo public post counter-example. #131 had that trigger; this head dropped it.
Carry the mark through click-through. Opening a marked title still shows the live body with no write-clock vs cutoff line. The list badge is not enough: the next action has to survive the popup. Repeat updated_at and the cutoff on that opened post, then compare those two clocks before treating the body as reconstructed evidence.

After the rebase

Repeated cutoff badges should use the ADR 0020 tokens already on #74 (frontend/src/styles/tokens.css + Storybook inventory), not a one-off .post-badge opacity. Close #131 as superseded once this head is the only write-clock vehicle.

Frontend lint/test/build and the full suite were still queued on this head at review time. Re-run them on the rebased 0.87.1 commit; do not merge on the 6f79ecb stack.

_{Sent by Cursor Automation: Fix Issues}

cursor · 2026-08-16T16:38:03Z

 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

+## [0.87.0] - 2026-08-17


Current #74 tip 69c035b already published ## [0.87.0] for granted retention purge and Storybook tokens. Rebase onto that tip and move this write-clock entry to 0.87.1 so both buyer slices stay in the changelog. Merging this 0.87.0 block as-is will conflict and collapse two releases into one version.

cursor · 2026-08-16T16:38:03Z

+    ``created_at <= knowledge_cutoff`` admits the title. ``updated_at`` is
+    the live write clock (ADR 0016). Equal times stay in-cutoff evidence.
+    """
+    return _as_utc(updated_at) > _as_utc(knowledge_cutoff)


updated_at > knowledge_cutoff is the right predicate (equal clocks stay in-cutoff). It only matches a real rewrite if source_post.updated_at moves when post_title / post_body change. Add a write-clock trigger that sets updated_at = now() unless the statement already assigned updated_at, and cover three cases: explicit historical pin stays, a body-only update after cutoff marks the title, a body-only update at the create clock does not.

cursor · 2026-08-16T16:38:03Z

-                "where post_title in ('Demo public post', 'Demo private post') "
-                "and created_at > '2026-01-12T12:00:00Z'"
+                "update source_post set created_at = '2026-01-10T12:00:00Z', "
+                "updated_at = '2026-01-13T09:00:00Z' "


This pin is the Demo public post counter-example. The next statement updates post_body without touching updated_at. If you add the write-clock trigger requested on live_write_after_cutoff, either assign updated_at again on that body write or re-pin after every Demo public / Demo private body update so make seed still shows public marked and private unmarked.

cursor · 2026-08-16T16:38:03Z

                      {post.post_title}
                    </button>
+                    {post.live_after_cutoff && (
+                      <span className="post-badge">Updated after cutoff</span>


The list mark disappears as soon as the operator opens the title. Pass updated_at and live_after_cutoff into that live-post popup and state the two clocks there (“written 2026-01-13, after cutoff 2026-01-12 — compare this body with the run before you treat it as reconstructed evidence”). After the #74 rebase, render this badge with the ADR 0020 tokens already used for repeated chips.

cursor

Reviewed exact head b4e6d2b (rebased onto #74 6f79ecb). CodeRabbit GitHub skipped this non-default base; CodeRabbit CLI cannot authenticate in this environment, so this is a full technical review of the committed diff, not a CodeRabbit result.

What holds

The buyer slice is the right one. created_at <= knowledge_cutoff still admits the title; updated_at > knowledge_cutoff only marks a rewrite. Equal clocks stay in-cutoff. The detail payload stays titles plus clocks — no body, DSN, or source SQL. Seed pins Demo public post to 2026-01-13 and Demo private post to the January create clock. Unit, API, and UI tests cover that counter-example.

Do not merge before #74. Do not treat draft #131 as a second landing vehicle.

Required before merge

Fix the seeded_db post-list exact set. Inserting Edited own-corp private post makes test_post_list_includes_public_and_own_corp_but_excludes_other_corp fail: it still asserts exactly {Public post, Own-corp private post, Late own-corp private post}. Add the edited title to that set.
Rebase onto current #74 69c035b and take 0.87.1. #74 already shipped 0.87.0 as granted retention purge plus Storybook tokens. This head still claims 0.87.0 (dated 2026-08-17). git merge-tree against 69c035b conflicts in ARCHITECTURE.md, CHANGELOG.md, and the version files. Keep the retention-purge 0.87.0 notes and add this write-clock slice as 0.87.1.
Keep source_post.updated_at honest after a body write. The comparison is correct only if the write clock moves when the live row is rewritten. There is still no trigger (or write-path assignment) that bumps updated_at on post_title / post_body changes while honoring an explicit updated_at in the same statement. Seed then does a body-only UPDATE after the pin. A later product edit, or a trigger that always sets now(), will either hide a rewrite or destroy the Demo public post counter-example. #131 had that trigger; this head dropped it.
Carry the mark through click-through. Opening a marked title still shows the live body with no write-clock vs cutoff line. The list badge is not enough: the next action has to survive the popup. Repeat updated_at and the cutoff on that opened post, then compare those two clocks before treating the body as reconstructed evidence.

After the rebase

Repeated cutoff badges should use the ADR 0020 tokens already on #74 (frontend/src/styles/tokens.css + Storybook inventory), not a one-off .post-badge opacity. Close #131 as superseded once this head is the only write-clock vehicle.

Frontend lint/test/build and the full suite were still queued on this head at review time. Re-run them on the rebased 0.87.1 commit; do not merge on the 6f79ecb stack.

_{Sent by Cursor Automation: Fix Issues}

cursor · 2026-08-16T16:39:08Z

 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

+## [0.87.0] - 2026-08-17


Current #74 tip 69c035b already published ## [0.87.0] for granted retention purge and Storybook tokens. Rebase onto that tip and move this write-clock entry to 0.87.1 so both buyer slices stay in the changelog. Merging this 0.87.0 block as-is will conflict and collapse two releases into one version.

cursor · 2026-08-16T16:39:08Z

+    ``created_at <= knowledge_cutoff`` admits the title. ``updated_at`` is
+    the live write clock (ADR 0016). Equal times stay in-cutoff evidence.
+    """
+    return _as_utc(updated_at) > _as_utc(knowledge_cutoff)


updated_at > knowledge_cutoff is the right predicate (equal clocks stay in-cutoff). It only matches a real rewrite if source_post.updated_at moves when post_title / post_body change. Add a write-clock trigger that sets updated_at = now() unless the statement already assigned updated_at, and cover three cases: explicit historical pin stays, a body-only update after cutoff marks the title, a body-only update at the create clock does not.

cursor · 2026-08-16T16:39:08Z

-                "where post_title in ('Demo public post', 'Demo private post') "
-                "and created_at > '2026-01-12T12:00:00Z'"
+                "update source_post set created_at = '2026-01-10T12:00:00Z', "
+                "updated_at = '2026-01-13T09:00:00Z' "


This pin is the Demo public post counter-example. The next statement updates post_body without touching updated_at. If you add the write-clock trigger requested on live_write_after_cutoff, either assign updated_at again on that body write or re-pin after every Demo public / Demo private body update so make seed still shows public marked and private unmarked.

cursor · 2026-08-16T16:39:08Z

                      {post.post_title}
                    </button>
+                    {post.live_after_cutoff && (
+                      <span className="post-badge">Updated after cutoff</span>


The list mark disappears as soon as the operator opens the title. Pass updated_at and live_after_cutoff into that live-post popup and state the two clocks there (“written 2026-01-13, after cutoff 2026-01-12 — compare this body with the run before you treat it as reconstructed evidence”). After the #74 rebase, render this badge with the ADR 0020 tokens already used for repeated chips.

cursor · 2026-08-16T16:39:08Z

                created_at="2026-01-20T12:00:00Z",
            )
+            _insert_post(
+                "Edited own-corp private post",


seeded_db now inserts this own-corp private title, so GET /api/posts will include it. test_post_list_includes_public_and_own_corp_but_excludes_other_corp still exact-sets three titles and will fail on this head. Add Edited own-corp private post to that set (and any other exact-set list that uses seeded_db) before the full suite is treated as green.

cursor

REQUEST_CHANGES on b4e6d2b.

The write-clock slice is the right buyer gap (prefer over draft #131). Admission stays created_at <= knowledge_cutoff; updated_at is a separate comparison; equal clocks stay unmarked; Demo public is the 2026-01-13 counter-example. TEPP stays behind tepp_client. List payloads stay aggregates-only.

Do not merge this head:

Blocking — Edited own-corp private post is inserted on the shared API fixture but test_post_list_includes_public_and_own_corp_but_excludes_other_corp still exact-sets three titles. Full test suite will fail the same way #110/#114 did.
Blocking — base is stale 6f79ecb. Live #74 is 69c035b (retention purge already took 0.87.0 and added ADR 0020 to CLAUDE.md). Merging this as-is drops the pending-lineage sentence and the retention section.
Blocking — 0.87.0 is already shipped on #74. Take 0.87.1 after rebase.

Landing vehicle is the rebased successor on cursor/bc-d9c9c898-f8dd-4055-a82f-1ef4c0e94184-f040 (v0.87.1, exact-set includes the edited title, seed clocks locked, PostBadge token). Do not merge #150 or #131 in parallel.

Cutoff body versioning stays a later slice. Independent reviewer still needed; this run does not self-approve.

_{Sent by Cursor Automation: Fix Issues}

cursor · 2026-08-16T16:42:58Z

+                "A January post rewritten after the run cutoff.",
+                created_at="2026-01-10T12:00:00Z",
+                updated_at="2026-01-13T09:00:00Z",
+            )


This edited own-corp row is the buyer proof for live_after_cutoff, but test_post_list_includes_public_and_own_corp_but_excludes_other_corp still exact-sets {"Public post", "Own-corp private post", "Late own-corp private post"} at line 612. Keep the row and add the title to that set.

cursor · 2026-08-16T16:42:58Z

-cutoff before treating the body as reconstructed evidence (ADR 0016).
+Opening a cutoff title shows the live post. Titles marked updated
+after cutoff were rewritten after the run; compare those bodies
+before treating them as reconstructed evidence (ADR 0016).


Keep this write-clock sentence, but rebase onto live #74 69c035b first. That head already has the ADR 0020 retention section and the pending-lineage next-action sentence. Merging this file as-is drops both.

cursor · 2026-08-16T16:42:58Z

 [project]
 name = "lineageweave"
-version = "0.86.2"
+version = "0.87.0"


0.87.0 is already taken by #74 retention purge (69c035b). After rebase, ship this slice as 0.87.1 in pyproject.toml, lineageweave/__init__.py, frontend/package.json, and uv.lock.

cursor

Do not merge #150 at b4e6d2b.

This head is dirty against current #74 (69c035b). #74 already shipped v0.87.0 as retention purge and Storybook tokens. Landing this slice as another 0.87.0 would collide and drop the retention entry.

Use #176 (9d57cbe) instead: same write-clock contract on current #74, recorded as v0.88.0. After make seed, open the Demo Corp lineage run — Demo public post is marked Updated after cutoff; Demo private post is not. Opening a marked title still shows the live body.

#162 and #167 still stack on this dirty head. Rebase those onto #176 after #74, or close them in favor of a #176-based successor.

Queued or predecessor-head gates are non-passing. This automation cannot merge.

View PR

_{Sent by Cursor Automation: Fix Issues}

seonghobae · 2026-08-16T18:08:39Z

Superseded by #193, which squash-merged the write-clock / live_after_cutoff slice onto live #74 (e4d7461, v0.89.0). Do not merge this head.

This was referenced Aug 16, 2026

Milestone 2: port verified direct-PostgreSQL analysis into the protected product architecture #79

Open

feat: compare live post write clock with analysis-run cutoff (v0.84.2) #131

Closed

seonghobae force-pushed the feat/analysis-run-live-write-clock branch from c6b0ee7 to b4e6d2b Compare August 16, 2026 16:24

This was referenced Aug 16, 2026

fix(ui): keep digest disclosure panels and 24px targets (v0.86.3) #155

Closed

fix(ui): keep digest disclosure panels and 24px targets (v0.86.3) #158

Closed

cursor Bot reviewed Aug 16, 2026

View reviewed changes

cursor Bot mentioned this pull request Aug 16, 2026

feat: record the seeded period report on the analysis-run registry (v0.86.4) #161

Closed

seonghobae mentioned this pull request Aug 16, 2026

feat: warn that cutoff-rewritten titles open the live body (v0.88.0) #162

Closed

cursor Bot mentioned this pull request Aug 16, 2026

fix: wait for affiliated corps before lineage create (v0.87.1) #164

Open

seonghobae mentioned this pull request Aug 16, 2026

feat: start a pending lineage reconstruction (v0.89.0) #167

Closed

seonghobae commented Aug 16, 2026

View reviewed changes

cursor Bot requested changes Aug 16, 2026

View reviewed changes

seonghobae mentioned this pull request Aug 16, 2026

fix(ui): name the next action on the cutoff live-body warning (v0.88.0) #171

Closed

cursor Bot requested changes Aug 16, 2026

View reviewed changes

This was referenced Aug 16, 2026

fix: rebase write-clock slice to 0.87.1 with honest updated_at #172

Closed

feat: record the seeded period report on the analysis-run registry (v0.87.1) #175

Closed

feat: compare live post write clock with analysis-run cutoff (v0.88.0) #176

Closed

cursor Bot requested changes Aug 16, 2026

View reviewed changes

seonghobae mentioned this pull request Aug 16, 2026

feat(ui): name next action on plural affiliation chips (v0.77.0) #192

Open

3 tasks

This was referenced Aug 16, 2026

feat: compare live post write clock with analysis-run cutoff (v0.89.0) #193

Merged

feat: warn that cutoff-rewritten titles open the live body (v0.90.0) #194

Merged

seonghobae closed this Aug 16, 2026

Uh oh!

Conversation

seonghobae commented Aug 16, 2026

Buyer gap

What the operator sees

Boundaries

Tests

Uh oh!

cursor Bot commented Aug 16, 2026

Uh oh!

coderabbitai Bot commented Aug 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

seonghobae commented Aug 16, 2026

Uh oh!

seonghobae commented Aug 16, 2026

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

seonghobae left a comment

Choose a reason for hiding this comment

Uh oh!

seonghobae Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

seonghobae Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

seonghobae Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

What holds

Required before merge

After the rebase

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

What holds

Required before merge

After the rebase

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot Aug 16, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot left a comment

coderabbitai Bot commented Aug 16, 2026 •

edited

Loading

cursor Bot left a comment •

edited

Loading