Add a manual live-server smoke test suite

docs/confluence/ と既存の golden および --json のテストカバレッジから始め、どのライブ Confluence の挙動がテストされていないかを把握します。ページ幅、添付ファイルの同期、受け入れられる添付ファイル名、公開されたテーブルのレンダリングを対象とする、手動で呼び出す最小限のスイートを定義します。完了条件は、呼び出し方法、認証情報と個人スペースの扱い、ガードレール、クリーンアップ、アサーション、および go test ./... と CI からの除外が明記されていることです。

Add a test suite a developer runs by hand against a real Confluence server —
credentials from the usual CONFLUENCE_* resolution, pages created in a personal
space — covering a small, critical set of behaviour.

Why

The current suite proves what markfluence emits: the converter's goldens pin the
storage format, and the --json schema guards the output contract. Neither can
prove what Confluence does with what we send, and docs/confluence/
is explicit that this is where confident wrong conclusions come from — body.storage
shows only what was stored, never what takes effect. Several behaviours were
established by experiment and are currently protected by nothing but those notes:

• page width living in two content properties, where writing one leaves the reader
  and the editor disagreeing;
• attachment sync's checksum/recorded-path logic (skip, update, repair a mangled
  path) and the multipart charset requirement;
• what attachment names Confluence accepts;
• whether a published table keeps its layout, alignment, and highlight colours.

A suite that runs against a live server would turn those from documented
observations into something re-checkable when Atlassian changes behaviour.

Deliberately undecided

Nothing about the design is settled yet — to be worked out when this is picked up:

• what it covers (which commands, which round trips, how minimal is minimal)
• how it is invoked and how it is kept out of go test ./... and CI
• how the target space and credentials are supplied
• what guardrails and cleanup it needs, given it writes real pages
• where the files live and what they assert against

Notes

Came up while fixing #18. Not urgent — parked for now.