Bundle Business mail attachments

[a-github-name]

What changed

• regenerate the bundled Business adapter from merged mere-business main (8588695, PR #104), exposing repeatable --attach PATH on mail send and mail reply
• add an end-to-end bundled-root test that reads two local files and verifies the exact mail.send workspace payload, MIME types, and Base64 bytes
• fix the Node 24 adapter generator regression caused by passing recursive: undefined to fs.rm
• retain the regenerated atomic-session-write updates shared by the other adapters; these were recovered by the full source-first build and are intentionally not discarded
• replace the legacy schema-v1 adapter manifest with an honest schema-v2 development manifest for all 16 clean, canonical main sources

User impact

The locally bundled command now supports:

mere business mail send \
  --mailbox-id mb_123 \
  --to person@example.com \
  --subject "Approval packet" \
  --body "Attached." \
  --attach ./approval-packet.pdf \
  --yes

Local validation

• pnpm verify passed
  • 91 tests passed
  • coverage passed
  • supply-chain checks passed
  • all 16 adapter safety and coverage checks passed
  • root, MCP, and package-content smokes passed
• bundled Business attachment test passed against a mock /api/cli/v2 workspace endpoint
• root app manifest confirmed attach on both mail.send and mail.reply
• all 16 recorded source repositories were clean, canonical, and at their current tracked main heads during the development build

Release-provenance blocker

This PR is intentionally draft and its manifest is intentionally mode: development; it must not be published as-is.

The strict release preflight currently fails because:

• mere-business PR #104 and mere-email PR Default mere.run source dir to ~/mere/mere-run #27 have no non-author approval bound to their exact reviewed heads
• the other 14 current source heads are not exact merge commits from merged non-draft PRs
• GitHub Actions on Business #104 did not execute any steps because the account reports failed payments or an Actions spending-limit issue

The repository's publication gate correctly rejects this snapshot. Do not weaken or fabricate provenance; satisfy those source-review/CI prerequisites, then rerun pnpm build:adapters:release and pnpm check:adapter-provenance before marking this ready.

[a-github-name]

Follow-up production/source truth:

• Business attachment code merged in mere-business #104.
• The tracked per-tenant workspace artifact merged in mere-business #105.
• suite-workspace deployed as 5de38c2c-b4e4-4b94-96c9-d1a2808735b1.
• suite deployed as d9aebedc-e22e-4dcd-a353-f1c0517bcb0d.
• This PR's development manifest now binds Business to current canonical main e6b6ccd0b0916a0809a84491897a63cb49efebe7; Business adapter bytes remain 4645c34210b35861a35e13c26bd581e7b4c6fe4379ef790021454e01221271b2 (328,980 bytes).

The Mere Network Growth tenant itself still needs the supported owner-dashboard "Sync to latest" action (or mere-admin workspaces sync ws_748658e71528). The currently signed-in director@thebarc.ca browser account is not a platform admin, so it correctly could not authorize mere-admin; no access-control bypass was attempted.