[a-shannon]

Add native Bitcoin Cash network and Cashonize packages, opt-in Rosen Service scanning/accounting, and thin app wiring. This remains a draft pending review of the related RCS integration document and resolution of its design and dependency gates.

Network reads, fee/transaction algorithms, signature validation and bounded submission belong to networks/bitcoin-cash. Wallet configuration, session, pairing and signing belong to wallets/cashonize. App query actions use the existing wrap/unwrapFromObject convention. Shared form/wallet fixes, data-source API changes, icon-type refactors and Webpack adaptations are excluded; integration documentation lives outside this repository.

BCH remains disabled while its Rosen index is unassigned. Cashonize is excluded from the active wallet registry until an accepted pairing interaction is available. The proposed WalletConnect SDK and dedicated submission contract still need direction. The latter retains streamed-body bounds, cancellation and a trusted deadline through the final submission write.

Local preparation validation:

• Network: 458 tests; package build and TypeScript pass.
• Wallet: 86 tests in six suites; package build and TypeScript pass.
• App registration/configuration/actions: 22 tests; constants: two tests; actual Next submission route: five tests.
• Actual environment module: three cases; prepared wallet factory: two cases. Changed-path Biome 2.5.4 checks pass.
• Service storage: 11 tests including populated PostgreSQL upgrade, alias CRUD, uniqueness, rollback-only DOWN and reconnect. Independent review inspects source; it does not replay PostgreSQL.
• Corrected Service configuration/scanner/health/calculator closure: 170 tests across six suites and independent exact-source review; the renamed root configuration spec subsequently passes its 27 cases. Scanner cadence uses constants; warn/critical thresholds use global healthCheck keys and validate only when enabled. Calculator tests consume its public package entry and actual update/save behavior.
• Independent source review of the ownership moves found no relaxed quote, signed-body, cancellation or deadline predicate in the selected joins.

These checks use a local linked-package graph. A preceding default Next/Turbopack attempt reported 293 errors; its raw log was not recovered or replayed in this audit. Normal clean installation/build is pending. Earlier Webpack/browser receipts apply to the previous candidate. New BCH codec/scanner/observation packages are not published on npm. After accepted producer releases, dependent ranges and the ordinary lockfile must be regenerated and checked through a clean install.

Service currently has one type error caused by the v2/v4 scanners' nominal private fields. A separate scheduler prerequisite restricts its argument to the consumed update()/name() API. Seven independently executed contract checks compile the actual scanner APIs, reject four wrong interfaces and verify unchanged executable output. That shared change is excluded from this BCH PR.

The integration document and matrix records the pinned RCS requirements, pending RCS review, pairing/SDK/submission decisions, producer release order and operator inputs. Assigned index, contracts, represented tokens, released installation and enabled operational qualification remain open. This update corrects the existing draft's scope; it does not request chain-code review before the RCS review.

Coordinated BCH drafts: Utils #11, Scanner #16, Guard #29, Watcher #17, Health Check #5. Sign Protocols #9 is a separate generic fix.