[torlando-tech]

Summary

The docs and code comments carried a stale "native ReticulumSwift node in the
NE" phantom that contradicted how Model B actually runs. A ground-truth pass
over the code confirmed the single RNS runtime is the embedded-Python RNS
node (app/rns_bridge.py via NEPythonRNS) in both flavors:

• Shipping runs it in-process in the app (PythonRNSBackend).
• Model B runs it in-process in the Network Extension; the app is a thin
  IPC proxy / UI client.

ReticulumSwift is not the runtime in either flavor. The app targets carry
it only as a compile-time link so retained shared sources that reference
ReticulumSwift / LXMFSwift types type-check (e.g. MessageRepository,
LocationSharingManager, CeaseTelemetry). The NE target declares it as a
compile-time packageProductDependency only - it is not in the NE's
frameworks build phase, so it is not linked into the extension binary and no
ReticulumSwift object runs there.

This is comment/string-accuracy only - zero logic changes.

Files

• ARCHITECTURE.md, README.md, docs/MODEL_B_BACKGROUND_DELIVERY.md:
  correct the "runs the native stack" claim, the NE-owns-ReticulumSwift
  bullet, the ReticulumSwift link paragraphs, and the flavor table.
• Swift comments in ColumbaApp.swift, AppServices.swift,
  BackendPreference.swift, ProxyRnsBackend.swift, AppGroupPaths.swift,
  OutboxQueue.swift, ProxyIPC.swift: replace references to the removed
  NEReticulumNode type and non-existent methods with the current
  NEPythonRNS / rns_bridge names; correct the misleading
  "Auto stays local" tunnel-mode wording to state it is a no-op in Model B.

Verification

• All 9 edited Swift files pass swiftc -parse (no syntax errors).
• The mermaid graph in ARCHITECTURE.md is byte-identical to HEAD; only a
  clarifying note above it changed.
• Diff is comment + one log string literal only (no logic).

Scope note

ReticulumSwift / LXMFSwift removal is intentionally out of scope here.
The build graph (pbxproj), the reconciler (isolate-modelb-targets.rb), and
the static contract tests all enforce ReticulumSwift linkage as a deliberate
invariant (the @_exported import ReticulumSwift in LXMFSwift means the kept
LXMFSwift product transitively pulls it in). Reversing that is a separate,
coordinated change.

[greptile-apps]

Confidence Score: 5/5

[Low impact] The PR appears safe to merge; the revised graph note addresses the previous finding.

Summary

The PR corrects documentation and comments to describe embedded-Python RNS as the runtime in both app flavors.

• Architecture notes now place each flavor’s Python node in its host process.

_{Reviews (2) · Last reviewed commit: "Update ARCHITECTURE.md" · Reviewed by Greptile}