docs(coil): re-baseline the seam ledger against the 2026-08-17 merge-base

Both halves regenerated against cd096b9: the file list and the churn/risk
columns, which are measured over the 60 days preceding the merge-base and so go
stale every time it moves.

The footprint shrank, +2622/-1093 -> +2590/-1042, while gaining two rows. The
shrink is the interesting half:

- ComposerPrimaryActions.tsx +128/-55 -> +74/-5. Upstream pingdotgg#4781 hoisted its inline
  send button to a `const` itself, which is the hoist the fork had carried since
  #35, so the fork's copy was deleted rather than re-synced. That retires the
  stale-hoist hazard this row has carried since 2026-08-08 -- a copy cannot
  conflict, so it reverted upstream restyles silently. -55 -> -5 is the signal:
  the fork now extends upstream's running/idle dispatch instead of displacing it.
- SourceControlProviderDiscovery.ts +20/-8 -> +12/-5. Upstream pingdotgg#6223 fixed the
  timeout half of issue #4 independently, and better, so the fork ceded it.

The two new rows are both consequences of upstream moving, not new fork work:
manifest.webmanifest became an add/add seam when upstream shipped its own, and
ComposerPrimaryActions.test.tsx takes one assertion.

Also records this cycle's re-checks of the two logic mirrors that fail silently
(the steer allowlist and the mobile send-label mirror), and the parallel-path
review of upstream's two apps/marketing commits, neither of which is ported.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: 2 people