Repository navigation
chore(upstream): advance intake baseline to cf1ba3d7da - #547
Merged
Merged
Conversation
incognitojam
added a commit
that referenced
this pull request
Sep 29, 2026
The upstream intake baseline advanced to `cf1ba3d7da` in #547, and the upstream intake runbook calls for regenerating the committed T3 Code import fixture from the new boundary. This PR regenerates `apps/server/src/dataImport/testFixtures/t3-code` from `cf1ba3d7da` (previously `8de9169f07`), so the Fork CI import test uses data from the upstream version styal is reconciled against. Between the two boundaries, T3 Code's stored events are unchanged: 171 events of the same types. Upstream's `ProjectionThreadPullRequests` migration adds a `projection_thread_pull_requests` table, which is empty for every generated thread, and a new `projection.attachment-cleanup` projector adds a cursor row to `projection_state`. The import replays events rather than reading projections. The rest of the diff is new IDs, timestamps, the attachment file name and the recorded server revision. ## Validation - Ran `generate-t3-import-fixture.ts` against an upstream checkout at `cf1ba3d7da`. It built the usual scenario through the server's HTTP API with the fake Codex CLI: completed (with an image attachment), settled, unsettled, archived, deleted, failed, worktree, empty and second-project threads. - `LegacyImport.fixture.test.ts` passes against the new fixture with no new expected differences. --- Written by an agent (Claude Code, claude-opus-5-5).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The upstream intake queue's baseline was still at
3997b9a3a4, though main has since taken every upstream commit throughcf1ba3d7da(the pingdotgg#11346 squash merge). The batch ending there was promoted asf5ff4a372c. This moves the baseline to that boundary, so the next batch starts at pingdotgg#11338.It also removes four entries from
.github/upstream-tracked-prs.jsonthat the last two batches recorded: pingdotgg#9921, pingdotgg#11302, pingdotgg#11103 and pingdotgg#11107. Their follow-ups, such as pingdotgg#8309, stay tracked.This PR changes only those two state files; it contains no intake commits.
Validation
node scripts/upstream-queue.ts advance cf1ba3d7da98357243ee056d2fd358eed8171981accepted the boundary. The command rejects a boundary with unresolved earlier commits or one inside a multi-commit PR.node scripts/upstream-queue.ts statusafterwards: baseline and reconciled-through are bothcf1ba3d7da; 317 of 338 commits up to the target are pending, 21 recorded, no exceptions. No tracked PR is listed as recorded.node scripts/upstream-queue.ts next --count 1now starts at fix: restore provider history and prompts when rewinding pingdotgg/t3code#11338.Written by an agent (Claude Code, claude-opus-5-5).