Forge: port custom T3 server to v0.0.35 - #1
Closed
naytewilson wants to merge 1 commit into
Closed
naytewilson wants to merge 1 commit into
naytewilson wants to merge 1 commit into
Conversation
github-actions
Bot
added
vouch:trusted
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.
Campaign
Controlled fork upgrade of Nayte's custom T3 server from the v0.0.31-era Work Lane / Source Truth fork to official stable T3 Code v0.0.35.
Base: official v0.0.35 commit
f925d639421844f02b3166d29281905dbba6d529.Temporarily closed on 2026-08-28 to prevent GitHub Actions billing while the port is being completed directly. This is not an abandonment of the branch or migration bridge.
Wave 1: migration-35 compatibility
The historical custom database records official-ledger migration id 35 as
WorkLanesAndSourceTruth. Official v0.0.35 also owns id 35 forProjectionThreadTitleRegeneration. Effect's migrator skips every migration id less than or equal to the latest recorded id, so the official migration is skipped on the legacy custom database.Already landed:
effect_sql_migrationsrow 35 unchanged;WorkLanesAndSourceTruth;t3_custom_schema_migrationsand adopts legacy custom migration as custom id 1;Remaining work is being committed directly to
forge/t3-custom-v0035-portwithout workflows. Production remains untouched until cloned-DB and Dell-local validation.