Plans are fetched asynchronously, and file paths appear in responses only for certain sessions.
What's wrong with this entry?
Fetching the current plan over the control channel now goes through the async path using the session's storage handle rather than a synchronous read. Plan and file-read responses now include the filesystem path only for certain sessions: reads add an absolute path when a per-session check holds, and plan responses include a path when it does not. Which sessions that check selects is decided elsewhere in the bundle.
getPlanAsync
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Plan mode can carry a session workshop document
Both mention plan mode
-
v2.1.221
Plan mode prototype-artifact offer
Both mention plan mode
-
v2.1.235
Very large plans cannot be approved
Both mention plan mode