batchcode v0.3.1

Fixes and usability

• Explicit session name/ID references must exist; typos never create new contexts. Omit task reference to create, or use explicit session add/fork. session set conf is strict too.
• task --name=NAME names a new session; task EXISTING --name=NEW renames while continuing, with stable ID/history/artifact paths. Conflicts/busy/preflight errors are rejected. Batch JSON uses session only for existing refs and name for new labels (including fork_from targets).
• Keep name-based output prefixes even if invoked by ID; long ID appears only in useful summary/info/list locations.
• Summary instructions require at least one submit_answer for finished, abandoned and no-task replies (including greetings). Soft character target, revision support, normal closing and warned fallback remain.
• File-not-found/permission/directory/space errors report the actual filesystem cause and requested path, not invalid JSON.
• Clearing ctx intentionally leaves a runnable/listed session identity.

Verification

149 offline/mock tests passed locally AND GitHub Actions Python 3.10/3.12/3.14 (run 36332775175). Clean ZIP install/query/key-check/uninstall/reinstall passed. The revised v0.3.1 prompt has NOT been tested against real paid APIs; mock greeting submissions do not prove actual-model compliance. External v0.3.0 DeepSeek/Tavily report remains separate evidence; no OpenAI live certification.

Upgrade

Same ctx schema as v0.3.0; no migration needed for that data. Invocation semantics tightened: use --name to create instead of an unknown positional name; fork batch destinations use name, not session. Do not overlay ZIP on filled profile files. Downloads include ZIP + matching SHA256; no private histories, keys or DNS repair script.