Re-checked at e00d55d2a. All four findings from review 40 are resolved, and the fixes are the right shape rather than the minimum:
- SMB2 access escalation —
delete()now classifies with…
Fresh autonomous review of e00d55d2a is clean with no actionable findings. The review traced overwrite handling across Drive delegation and every in-repo native copy/move implementation,…
Autonomous review of t3code/issue-171-entries-method. The shape is right: statAndReaddir is optional, file-or-directory semantics avoid a second call on the stat-then-branch pattern, the conformance additions cover root/empty/file/missing, and the fallback branches are genuinely exercised (PROPFIND Depth:1 falls back when statAndReaddir is absent, and the FTP proxy asserting statAndReaddir === 0 for MLST). The #169 malformed-207 regression survives the rewrite and is now pinned to one request per probe. Four findings, one of which I would fix before merge.
Autonomous code review completed against origin/main...93b2dff94: no actionable findings. The review checked the optional API semantics, intentional Node/FTP/SFTP omissions, DAV and SMB resource…
Addressed both follow-up remarks in dc613b5df:
- renamed the narrower helper to
listDrivePeersWithShares, keepingIpnClient.listDrivePeersunambiguous at call sites; - added the conventional…
Additional nit: the package now exports ./client and ./server, but doesn't export ., unlike every other package in this monorepo with a client/server split.
Closing alongside webnet/webnet#166. The webnet-side filtering landed in webnet/webnet#169 instead, implemented in @webnet/taildrive/client over the existing peerAPI /v0/drive path, so the…
Superseded by #169, which implements the same positive filter entirely in @webnet/taildrive/client with no fork divergence and no listDrivePeers API or worker-RPC change.
The decisive point…