Promote staging to main (7549ca42)

[stateofkate]

Caution

DO NOT USE THE MERGE BUTTON ON THIS PULL REQUEST.
THE BUTTON CREATES A NEW COMMIT AND BREAKS THE RELEASE MODEL.
COMMENT /promote TO COMPLETE THE PROMOTION.

Summary

Ships trajectory-taxonomy improvements (grouped label vocabulary, writing_report, contentless-step filtering before summarisation), live transcripts on public experiment share links, and a task-browser perf revert plus the migration-revision repair that followed it.

Commits in this promotion

7549ca42 feat(summary): drop contentless steps before the summariser reads them (#1155)
bd139668 fix(migrations): restore applied task browse revision (#1157)
241419bc Revert "perf(tasks): bound task browser page work" (#1156)
8697d5d9 feat(taxonomy): give the model grouped, defined labels (#1154)
aa54cd62 perf(tasks): bound task browser page work (#1152)
3dc0cf30 feat(taxonomy): add writing_report to the trajectory component vocabulary (#1153)
c7515f66 Allow live transcripts on public experiment share links (#1149)

Note: aa54cd62 (#1152) is reverted by 241419bc (#1156) within this range, and bd139668 (#1157) restores the task-browse alembic revision the revert dropped. Net effect of that trio is no task-browser perf change, with migration state consistent.

Validation

main is a clean ancestor of staging (0 commits on main not in staging), so this fast-forwards.

Staging Deploy on the pinned target 7549ca42 must be green before /promote.

---

Note

Medium Risk
Public live endpoint expands unauthenticated surface area but stays token-scoped; trajectory prompt/taxonomy changes affect all new summaries; migration runs DDL and heavy backfill on deploy.

Overview
This promotion bundles trajectory-analysis improvements, public live viewing on share links, and migration housekeeping after a reverted task-browser perf change.

Trajectory summarization restructures component labels into explore vs implement groups with per-label definitions in the prompt (writing_plan / plan_correction move to explore; new writing_report on implement). The summarizer strips contentless steps before building the model prompt (step IDs and validation still use the full trajectory). Frontend types, labels, and --tc-writing-report styling support the new kind.

Public sharing adds GET /public/experiments/{token}/trials/{id}/live (core + Next.js proxy) and documents it. trial-detail-panel shows the Live tab for running/retrying trials without requiring the analysis view—relevant for public share pages.

Database: task_browse_summary_001 migration adds task_version_browse_summaries, indexes, and backfill SQL—restoring revision consistency after the task-browser perf revert (#1156/#1157); net perf behavior from that experiment is unchanged per the promotion notes.

^{Reviewed by Cursor Bugbot for commit 7549ca4. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
oddish-app	Ready	Preview	Aug 11, 2026 4:43am

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7549ca4. Configure here.}

[cursor]

Stale alembic head assertion

High Severity

test_verdict_state_migration_is_the_only_head still expects verdict_state_001 as the sole Alembic head, but restoring task_browse_summary_001 chains onto that revision and becomes the real head. The assertion is now false and will fail anywhere this test runs.

 

^{Reviewed by Cursor Bugbot for commit 7549ca4. Configure here.}

[cursor]

Clip before inert-step drop

Medium Severity

Overflow retries in generate still clip by raw step count, while drop_inert_steps runs only later inside _fmt_trajectory. On long runs where the kept head and tail are mostly contentless, the retry prompt can collapse to little more than the omission marker after the contentful middle was discarded.

Additional Locations (1)

• backend/api/services/blocks/analyzer/trajectory/trajectory_component_block.py#L219-L227

 

^{Reviewed by Cursor Bugbot for commit 7549ca4. Configure here.}

[cursor]

Risk: high. Left a non-blocking comment — Cursor Bugbot finished as skipping with 2 unresolved findings (including a high-severity Alembic head assertion), and this staging→main promotion exceeds the medium approval threshold. Assigned reviewers for human review.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}

[stateofkate]

/promote

[github-actions]

Promoted. main now points at 7549ca42cf6838e2e72139b009972994532e651c, the same commit as staging.