summaryrefslogtreecommitdiffstats
path: root/packages/meshbay-node/src/meshbay_node/hub_client.py
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-09-10 18:54:22 +0200
committerChristophe Besson <cbesson@gmail.com>2026-09-10 18:54:22 +0200
commit2baebeebecd1c1a201d1ce5649ab5d0e04c3617b (patch)
treeddbe07d2cecb09f06c77254e4e984f00322270f7 /packages/meshbay-node/src/meshbay_node/hub_client.py
parent481d1ef89fa89366a6484a703491dee2c767cdfc (diff)
downloadmeshbay-2baebeebecd1c1a201d1ce5649ab5d0e04c3617b.tar.gz
docs(node): the ack comment described scalars that are gone
The handshake ack's app-directories entry still said "the same three answers in one shape" and "the scalars above are derived from these and kept for MNP 1.0 clients". Neither is true since the per-app ops were folded into one: there are no scalars above, and a 1.0 client cannot reach this code at all — the floor moved to 3.0 with the lease flag day. A comment that contradicts the code beside it is worse than no comment, because one of them is wrong and the reader cannot tell which. This is the same fault the leaseless-bound comment had, one commit earlier. What it says instead is what is actually load-bearing: `<app>_directories` is the only form on the wire, and `chat_directory` below is safe as a second name for one of them because `_app_directories_ctx` derives it on every build rather than storing it alongside — which is precisely what the removed scalars did not do. daemon.py had the same stale reference three lines from the code that produces these, pointing at `video_root` for the shape a per-group signed setting takes. Comments only; no behaviour change. Node suite green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YVoHVCcfBqud6ZjG4db3y7
Diffstat (limited to 'packages/meshbay-node/src/meshbay_node/hub_client.py')
0 files changed, 0 insertions, 0 deletions