[josephnef]

Follow-up to #129. CLAUDE.md only described the WFB-NG data path. This adds:

• the two link modes in the intro and module table
• an APFPV section: StaLink responsibilities, preference keys, the camera-side data path (static IP, UDP forwarding to the unchanged loopback consumers, air_man_ap TCP 12355 and the aalinkFPV HTTP API), the single-flight TCP client rules, and the agreed key-frame auth follow-up
• the dev_mutex / withDevice() device-access rule and lock order that APFPV link mode: join the OpenIPC apfpv camera's open AP with devourer #129 introduced in WfbngLink
• the pixelpilot-sta log tag and tools/apfpv-open-static-cam.sh

Docs only.

🤖 Generated with Claude Code

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can ask Qodo to dismiss a finding you disagree with, with your reason on record

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Document APFPV link mode and device-access rules in CLAUDE.md

📝 Documentation 🕐 Less than 10 minutes

AI Description

• Explain how APFPV and WFB-NG use the same video and telemetry consumers.
• Document APFPV settings, camera control, TCP behavior, and the key-frame authentication follow-up.
• Record device-lock rules, the station log tag, and the camera setup tool.

Diagram

graph TD
  Settings["Link settings"] --> Link["WfbngLink"] --> WFB["WFB-NG mode"] --> UDP["Loopback UDP"] --> Consumers["Video and telemetry"]
  Link --> STA["APFPV StaLink"] --> UDP
  Camera["Camera AP"] --> STA

Loading

High-Level Assessment

Documenting these existing implementation rules in CLAUDE.md is appropriate for contributor and coding-agent guidance. The file points to the README for user-facing instructions rather than duplicating them.

Files changed (1) +41 / -5

Documentation (1) +41 / -5

CLAUDE.mdDocument APFPV architecture and device-access constraints +41/-5

Document APFPV architecture and device-access constraints

• Describes both link modes, APFPV preferences and data paths, camera-control behavior, and the unchanged loopback consumers. Records the single-flight TCP rules, key-frame authentication follow-up, device mutex and lock ordering, VPN behavior, camera setup tool, and station log tag.

CLAUDE.md