[SoundMatt]

Summary

Addresses #45. RELAY spec v1.14 expanded §13.7.2's standard module-name
registry with canonical names for RCP protocol-core concerns (avtp,
acf, lifecycle, regmap, discovery, request, fragment, e2e).
This is a pure naming/structure reconciliation — no protocol behavior
change.

Verified each delta from #45 against current code before acting:

• rcp/wire.hpp → rcp/avtp.hpp + rcp/acf.hpp — confirmed still
  real: wire.hpp bundled AVTPDU header framing together with
  ACF_ABB/ACF_GBB message-format encoding under the "wire" name (the
  inverse of how the other three RCP replacements name things). Split
  into rcp/avtp.hpp (AVTPDU/NTSCF/TSCF framing) and rcp/acf.hpp
  (ACF_ABB/ACF_GBB message format), matching the registry's separate
  entries. rcp/legacy_wire.hpp (the pre-replacement 16-byte codec,
  still used internally by rcp/udp.hpp until v2.13.0) is untouched.
• rcp/sequencer.hpp → rcp/request.hpp — confirmed still real, but
  it's a rename, not a split: the file already covered exactly the
  registry's request entry ("conditional-request taxonomy... and
  sequencers") in one place. SequencerTable keeps its name as the
  internal sequencer-state sub-concept within the module.
• lifecycle, regmap, discovery — confirmed already correct, no
  action (issue was right that this repo is the reference case here).
• e2e — confirmed already correct, no action.
• request module for conditional-request taxonomy — confirmed real
  at time of filing; resolved by the sequencer→request rename above,
  since that file already held both halves the registry's request
  entry names.
• fragment.hpp — not created. This repo's ROADMAP.md milestone
  52 (v2.8.0) already decided fragmentation no-go for this cycle (see the
  milestone's "Done" writeup and regmap.hpp's kOptFragmentation
  comment) — there is no fragmentation logic anywhere in the tree to
  extract into a module. The issue's phrasing ("if AVTPDU/ACF
  fragmentation logic exists elsewhere... consider extracting") already
  anticipated this might not apply; current code confirms it doesn't.
  Added a short note to ROADMAP.md's disposition section so this isn't
  re-litigated by a future pass.
• canbr.hpp/linbr.hpp DEPRECATE vs. ADAPT — left unresolved, as
  the issue explicitly asked. This repo currently calls DEPRECATE; noting
  it's still an open cross-repo architectural question, not a naming fix.

Also updated the doc comments, README module table, and .fusa-reqs.json
requirement text that referenced the old module names, and added a short
"Post-hoc naming reconciliation" note to ROADMAP.md rather than rewriting
its historical per-milestone narrative (which still accurately describes
rcp/wire.hpp as it existed at each point in time).

Test plan

• cmake --build (AppleClang, Release) — full build succeeds
• ctest — all 59 tests pass (rcp_avtp, rcp_acf, rcp_request new/renamed; rcp_wire/rcp_sequencer removed)
• cpp-rcp version/CLI build succeeds with -DRELAY_BUILD_CLI=ON
• RELAY relay conform --strict against the built cpp-rcp CLI — PASS
• CI (build-and-test matrix, relay-conform, clang-tidy, cpfusa-* jobs) — pending on this PR