[kahrendt]

Addresses #133.

The spec has the server alone start a source stream (roles/source/v1.md "Default streaming behavior"); a client reports line sense as a hint. The library already supports that through SourceRoleConfig::line_sense and SourceRole::set_signal(), and detection stays in the application.

• docs/integration-guide.md: says detection is the application's job and to call set_signal() on each change.
• examples/source_client: -s DBFS meters each buffer's RMS level and reports present after 100 ms at or above the threshold, absent after 2 s below. Capture runs from startup in that mode; audio reaches write_audio() only while the stream is open. Without -s the example is unchanged.

Testing: built and run on macOS; -s -70 on the laptop mic reported absent then present, and an invalid threshold is rejected. No unit tests (example code).

[Copilot]

🟡 Changes recommended

The untested metering state machine and inaccurate timing documentation should be addressed before approval.

5 open findings

• Add pure-helper tests for RMS debounce state machine · New
• Document asymmetric line-sense hold delays · New
• Include line-sense hold times in option summary · New
• Clarify separate metering and forwarding gates · New
• Document line-sense present and absent hold times · New

What changed in this PR

Adds optional RMS-based line sensing to the source client example.

Changes:

• Adds -s DBFS with 100 ms present and 2 s absent holds.
• Keeps capture active for metering while gating audio forwarding.
• Documents application-managed line sensing.

File	Description
examples/​source_client/​README.md	Documents line-sense usage.
examples/​source_client/​main.cpp	Implements RMS metering, holds, and signal reporting.
docs/​integration-guide.md	Clarifies line-sense responsibilities.

🧠 Review effort: Balanced

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.