Two options every transport accepts and four cannot act on Follows the code change that made SendTimeout and the OpenAsync cancellation token mean something. The options table said "all" for SendTimeout, which was true of what a transport accepts and not of what it does: UDP writes and SSH.NET's single operation timeout have no blocking write to bound, so four transports store the value and never use it. A new section says which, and says the same for how far the cancellation token reaches on each transport - the API and REST transports await the whole connect, the CLI family covers the login but not the synchronous socket connect, WinBox native cannot honour it once the EC-SRP5 handshake starts. Also: the two pages that said the 3.x names LoadAsync / LoadListenAsync "still work" now say they no longer compile, which is what Obsolete(error: true) means. RawSentences is gone from the three pages that described it as an alias of RawCommand. The new TikUnknownSentenceTypeException joins the hierarchy and the table on Exception handling. And the anchor two pages had been pointing at for the low-level API's own language: the section existed, but as a heading inside a blockquote, which GitHub gives no id. Promoted to a real section - two pages linking to it as a destination is the argument for it being one.
Async CRUD: a title, and the old names as they stand today
LoadAsync is LoadWithCallback, and these pages no longer apologise for the name Two pages carried a warning that LoadAsync and LoadListenAsync are "not part of this family despite the name" - they return a running ITikCommand and callbacks, while LoadListAsync/LoadAllAsync/SaveAsync return a Task, and all of them are extension methods on ITikConnection that land in one completion list. They are LoadWithCallback and LoadListenWithCallback now, so the caveat is a statement of what they are rather than a correction of what they are called. The old names still compile as [Obsolete] forwarders and the pages say so. 53 references across 16 pages. History.md keeps the old names, as it should. Matches tik4net master: "LoadAsync was not awaitable, and sat in the list beside the ones that are".
Async CRUD page for the O/R mapper New page for LoadAllAsync / SaveAsync / DeleteAsync and the rest of the Task-based mapper surface (tik4net A7), linked from the CRUD, reading-data, O/R-mapper and ADO.NET pages. Says explicitly that these are the same rules awaited rather than a parallel implementation, that the token comes before the params filter array, and which methods deliberately have no async form — including that LoadAsync and LoadListenAsync are NOT part of this family despite the name. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>