chore: sync main to dev before repair wave

[LeXwDeX]

Why

The approved repair wave for #472-#475 must follow the repository rule that delivery branches start from main, while the current main and dev histories have diverged after the v1.0.36 promotion and v1.0.37-dev.1 prerelease. Starting four repair branches before restoring ancestry would make PRs to dev carry unrelated main-side history or require an explicit branch-policy exception.

Scope

Synchronize the current main history into dev through the normal PR gates before any repair branch is created. Do not change product behavior, tests, CI policy, release mechanics, or the four repair issues.

Approach

Create the delivery from the fetched origin/main snapshot, target dev, preserve any dev-only commits, and verify the resulting merge base makes origin/main an ancestor of the updated dev.

Acceptance criteria

• The PR targets dev and contains no product or test changes beyond the synchronization delivery metadata.
• Required Typecheck and Unit Tests (linux) checks pass.
• specgit finish --json exits 0 before merge.
• After merge, git merge-base --is-ancestor origin/main origin/dev exits 0.
• Issues fix(test): make HttpAPI CI composite exit on macOS #472-fix(sdk): eliminate OpenAPI cleanup race during generation #475 remain open and unchanged, ready for separate branches from main.

Blocked by

None - can start immediately.

[LeXwDeX]

SpecGit delivery branch: feat/476-sync-main-to-dev-before-repair-wave (draft pull request #478).

[LeXwDeX]

Superseded: delivery draft PR #478 was closed unmerged, and the objective (restore main/dev ancestry before the repair wave) was achieved by later syncs — PR #497 (main→dev, Closes #496) — while the repair wave itself (#472–#475) shipped on branch-naming-compliant branches via PRs #480/#482/#485/#486/#487. Closing as completed-by-supersession.