`updateIncomplete` does not travel with carried work either, leaving a false banner on trunk

The gap

updateIncomplete is the same shape of bug #236 was, in the same handler, and it is still there.

The work-meta documentation in src/main.js names appliedPatch and updateIncomplete as describing the work rather than the site. A trunk update run from trunk writes updateIncomplete: true at site level. If the contributor then edits something, links a ticket and chooses to take the loose work along, the rebuild finishes on the branch and sites:mark-update-complete clears the branch's copy only.

Trunk is left with a true updateIncomplete and no path to clearing it: a permanent, false "Update incomplete" banner, on a site where the update did complete. Exactly #236's failure, one field over.

Found by the review pass on #473, which fixed the appliedPatch half and deliberately did not touch this one.

The part that needs deciding

Whether the flag should travel at all is a judgement call, and that is the substance here rather than the plumbing.

appliedPatch describes a diff sitting in the worktree, so it belongs wherever those files go. updateIncomplete describes the state of one shared node_modules and build/, which the branches of a site all share. A flag about a build is arguably a property of the site and not of the work, in which case the fix is the opposite one: stop writing it per branch, and clear it at site level wherever the rebuild finishes.

Both readings end the false banner. They differ in what happens when two tickets are worked in turn with a rebuild half done, so it is worth answering before writing anything.

Related

• #236 — the same bug in the other field
• #473 — the fix that named this one
• #446 — the earlier false "Update incomplete", from a different cause

Start in src/main.js and read the work-meta documentation alongside the handling described in #236 and the appliedPatch fix in #473. Decide whether updateIncomplete belongs to carried work or to the shared site state, then define the behavior for sequential tickets and incomplete rebuilds. Done means the chosen model prevents a false persistent “Update incomplete” banner.