forked from boos/BoosAPI
cita-777
f335a330e3
This release branch starts from the latest origin/main and folds in the current origin/dev snapshot so the PR to main can follow the repo's publish flow without opening directly from dev. Conflict-heavy files were normalized back to the dev snapshot where necessary so the release branch reflects the code currently being carried on dev instead of a line-merged hybrid. Constraint: Publication flow requires a clean release branch from latest origin/main rather than a PR directly from dev Constraint: The branch must preserve the current dev snapshot even when main and dev have drifted substantially Rejected: Open the PR directly from dev | violates the repo publication flow Rejected: Manually redesign every historic dev/main conflict during release prep | too broad for a publish branch Confidence: medium Scope-risk: moderate Reversibility: clean Directive: Treat this branch as a publication snapshot of dev-on-top-of-main, not as a general cleanup pass over old divergence Tested: update-center focused vitest suite on release branch; typecheck; build:web; docs:build; repo:drift-check Not-tested: Full npm test remains red from inherited tmp/sub2api frontend suites and an existing firstByteTimeout unhandled error