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
- Run a source audit for
TODO, FIXME, HACK, stub, placeholder, and not implemented across headers, sources, examples, and tests.
- Build a table with path, symbol/module, current behavior, classification, and disposition.
- For each
production row, add or verify tests proving the behavior is real.
- For each
experimental row, document it in README/docs and ensure names or docs make the status explicit.
- For each
test-only row, keep it out of public documentation and release notes.
- For each
remove row, open a focused cleanup issue or PR.
Acceptance Criteria
Verification
What
Audit every stub, placeholder, TODO, and partial protocol implementation in
network_system, then classify each asproduction,experimental,test-only, orremove.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_systemexposes 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.mdfeature matrixCHANGELOG.mdif support status changesHow
Approach
TODO,FIXME,HACK,stub,placeholder, andnot implementedacross headers, sources, examples, and tests.productionrow, add or verify tests proving the behavior is real.experimentalrow, document it in README/docs and ensure names or docs make the status explicit.test-onlyrow, keep it out of public documentation and release notes.removerow, open a focused cleanup issue or PR.Acceptance Criteria
removeormust-fixVerification
rg -n -i "TODO|FIXME|HACK|stub|placeholder|not implemented" include src libsresults are either eliminated or explicitly accounted for in the audit table