1.5 KiB
1.5 KiB
id, name, status, depends_on, scope, risk, impact, level
| id | name | status | depends_on | scope | risk | impact | level | |||
|---|---|---|---|---|---|---|---|---|---|---|
| review/complete-system | Review complete system — CLI, NAPI, end-to-end integration | pending |
|
system | low | project | review |
Description
Final review of the complete wraith system. Verify CLI binary works end-to-end, NAPI wrapper provides correct JavaScript API, and both layers properly wrap the core library.
Acceptance Criteria
wraith serve+wraith connectend-to-end: SSH tunnel established, SOCKS5 proxy routes traffic- All CLI flags work: transport modes (tcp, tls, iroh), auth options, proxy, stealth, rate limits
- Environment variables (
WRAITH_SERVER,WRAITH_IDENTITY) work as defaults --stealthvalidates--transport tlsrequirement- NAPI
connect()returns Duplex stream; data flows bidirectionally - NAPI
serve()accepts connections;onConnectionemits Duplex streams - NAPI key material from Buffer works (not just file paths)
- Feature flags:
tls,iroh,acmecorrectly gate optional functionality - Base build (
cargo build -p wraith-corewith no features) compiles and works - All tests pass:
cargo test --workspace - NAPI tests pass:
cd crates/wraith-napi && npm test cargo clippy --workspacepasses- No logging of tunnel destinations anywhere in the system
References
- docs/architecture/overview.md, docs/architecture/napi-and-pubsub.md
Notes
To be filled by implementation agent
Summary
To be filled on completion