Cardano Updates

This setup was long superseded by demo/2025-11 and will be retained as
the "demo/burst" scenario.

The proto-devnet demo moved to tx-centrifuge

CLAUDE.md: add workspace structure, key design decisions (HRTB codecs,
Runner pattern, try_send demuxer, IngressCounter, supervisor), update
phase list to show Phase 1 complete with 4 phases total.

implementation-plan.md: mark Phase 1 complete with notes on what was
built vs planned (supervisor, security hardening, capture command, test
vectors -- all additions beyond the original plan).

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Require a systematic audit of all untrusted-input paths at the end of
each implementation phase: allocation bounds, buffer caps, non-blocking
demuxer, timeout coverage, error propagation, and no-panic grep.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Add analysis of Pallas v1 vs v2 event-driven models and Haskell's actor
approach. Document a three-layer strategy:
- Layer 1 (net-core): pure protocol state machines, codecs, mux, bearer
- Layer 2 (connection): single-connection facade for tools/tests
- Layer 3 (node/behavior): multi-peer coordination (Phase 3+, model TBD)

Add four implementation phases: mux+handshake, chainsync+blockfetch,
remaining praos+multi-peer, leios protocols.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

- CLAUDE.md: project overview, code standards, architecture notes, doc index
- docs/praos-network.md: complete N2N protocol reference from spec + blueprint
  (mux wire format, all 6 mini-protocols with state machines, CDDL, timeouts,
  concrete Cardano era-tagged types)
- docs/implementation-haskell.md: ouroboros-network architecture survey
  (typed-protocols framework, mux Wanton scheduling, connection manager)
- docs/implementation-pallas-v1.md: pallas-network v1 survey
  (facade API, runtime agency checks, design assessment)
- docs/implementation-pallas-v2.md: pallas-network2 survey
  (Interface/Behavior/Manager pattern, pure state machines, promotion system)
- docs/leios-changes.md: CIP-0164 Leios network additions
  (LeiosNotify/LeiosFetch protocols, EB/vote/certificate types, QoS requirements,
  structural implications for net-rs)
- plans/masterplan.md: project vision, requirements, design areas
- plans/implementation-plan.md: Phase 1 plan (bearer, mux, codec, handshake, CLI)

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

The thread labeling was creating more streams than supported, especially
due to the polling of the N2C endpoint.