Skip to content

chore(audit): classify protocol stubs and placeholder implementations #1144

Description

@kcenon

What

Audit every stub, placeholder, TODO, and partial protocol implementation in network_system, then classify each as production, experimental, test-only, or remove.

Part of kcenon/common_system#684 and #964.

The 2026-05-21 analysis found placeholder/stub markers in protocol-heavy areas, including HTTP/2 library stubs and DTLS/TLS TODO paths. This issue should turn that loose signal into an explicit support matrix.

Why

network_system exposes multiple protocol libraries (network-tcp, network-udp, network-websocket, network-http2, network-quic, network-grpc). Consumers need to know which modules are production-supported and which are structural placeholders or experimental surfaces. That is especially important before v1.0 freeze language is finalized.

Where

  • include/kcenon/network/**
  • src/**
  • libs/network-*/*
  • docs/protocols/**
  • README.md feature matrix
  • CHANGELOG.md if support status changes

How

Approach

  1. Run a source audit for TODO, FIXME, HACK, stub, placeholder, and not implemented across headers, sources, examples, and tests.
  2. Build a table with path, symbol/module, current behavior, classification, and disposition.
  3. For each production row, add or verify tests proving the behavior is real.
  4. For each experimental row, document it in README/docs and ensure names or docs make the status explicit.
  5. For each test-only row, keep it out of public documentation and release notes.
  6. For each remove row, open a focused cleanup issue or PR.

Acceptance Criteria

  • Support-status table committed or posted in this issue
  • README protocol feature matrix reflects the audited support status
  • Public headers do not expose undocumented placeholder behavior
  • Any production-classified protocol has at least one unit or integration test exercising non-happy-path behavior
  • Follow-up issues are opened for rows classified as remove or must-fix
  • [EPIC] Ecosystem hardening follow-up from 2026-05-21 analysis common_system#684 receives the final support-status summary

Verification

  • rg -n -i "TODO|FIXME|HACK|stub|placeholder|not implemented" include src libs results are either eliminated or explicitly accounted for in the audit table
  • Relevant protocol tests pass on the standard CI preset

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions