Release reconciliation — sync #418 reviewed fixes back to develop

[Flow-Fly]

Context

PR #418 was squash-merged into main as 520107f89ed943aeaae2249ae1337a3f77be66db from independently reviewed head 925b12650fb4dae325070a982033875797eca1ad.

The release branch was deleted after merge. develop remains at 278b6561ded5c8563909f952c71861a5216dd60a and does not contain the final release-review repairs. New feature branches from the current develop tree would therefore regress already released fixes.

Outcome

Make the develop tree exactly match the released and reviewed main tree before new feature work begins, while preserving develop as the continuing integration branch.

Scope

• Start from current origin/develop.
• Apply the exact tree delta between origin/develop and released origin/main.
• Do not reinterpret, simplify, or extend the released changes.
• Open one draft pull request targeting develop.
• Record the released commit and reviewed head in the PR.

Acceptance criteria

• The reconciliation branch tree is byte-for-byte identical to origin/main and reviewed head 925b12650fb4dae325070a982033875797eca1ad at creation time.
• The PR contains no changes beyond that exact tree reconciliation.
• The full repository verification gate passes.
• Independent exact-head review confirms tree parity and no scope expansion.
• The PR remains unmerged until explicit owner approval.

Verification

git diff --exit-code HEAD origin/main
git diff --exit-code HEAD 925b12650fb4dae325070a982033875797eca1ad
npx tsc --noEmit
npm run lint
npm run test:run
npm run build
npm run fallow:audit
git diff --check

Non-goals

• No new feature work.
• No Avoid full-cel rescans during project autosave without risking stale pixels #419 performance redesign.
• No Guided Drawing — choose or create a saved palette #383 Guided Drawing work.
• No dependency changes or unrelated cleanup.

[Flow-Fly]

Agent Assessment

• Risk: low. The patch is a mechanical copy of the already released, independently reviewed tree; it introduces no new product behavior.
• Permission: ready for agent implementation.
• Hard boundary: branch from current origin/develop, produce exact tree parity with origin/main / reviewed head 925b126, and stop on any live-head drift or non-parity.
• Human gate: the owner merges the reconciliation PR after exact-head review and green checks.

[Flow-Fly]

Workflow Director decision — reconcile current main

The first worker correctly stopped because origin/main advanced after this issue was created.

Current approved target:

• origin/develop: 278b6561ded5c8563909f952c71861a5216dd60a
• origin/main: 230611dfa4665177f725eeb0d4063a64c42ce6fe
• Release editor, PWA, backend, and observability foundations #418 reviewed release snapshot: 520107f89ed943aeaae2249ae1337a3f77be66db / tree-equivalent head 925b12650fb4dae325070a982033875797eca1ad
• post-release main additions: build(deps): bump sharp and wrangler #422 (sharp / wrangler) and build(deps-dev): bump postcss from 8.5.16 to 8.5.24 #420 (postcss), both merged with green required checks

Reconcile the exact current origin/main tree into develop, including those two dependency updates. This keeps the integration branch at the complete production baseline and avoids a later dependency downgrade.

PR #421 is still open and behind current main. It is explicitly outside this reconciliation.

The worker must stop again if either approved branch head drifts before editing or pushing.

[Flow-Fly]

Reconciliation complete

PR #424 merged into develop as 97f5ef646ade1a2e1f3266e52f5ef4b459b46b54.

The merged tree was independently verified byte-for-byte identical to corrected main at cd62f5cf746d7dc6b93bdd56fbf9c2a334e853f4. CI, automatic Codex review, and Terra exact-head review were clean. The legacy empty-image compatibility finding was repaired on main by #426 before reconciliation and is covered by public regression tests.