Ota v1.6.10 Now available

v1.6.10 is a boundary-release.

The hard part was not adding more surface area. It was making the selected path honest when a repo mixes host file prep, container setup, task-scoped requirements, native prerequisites, and runtime proof. That kind of boundary drift is easy to miss until a real repo crosses it.

This release makes the path more explicit from doctor through run and proof: workflow preparation is first-class, selected prerequisites are scoped to the task or workflow that needs them, native provisioning follows the real task body, and proof artifacts stay tied to the selected runtime.

v1.6.10 ships a focused set of workflow and provisioning improvements:

1. Native prerequisite activation now reaches the actual task bodies selected by ota run and ota up, so Windows visual_studio_dev_shell support applies to the real native path instead of a guessed one.
2. Conflicting task-level native activations are rejected early, and ota up --dry-run only advertises native activation on native workflow paths.
3. Container-mode workspace mounts on Windows now normalize canonical worktree paths before Docker sees them, which avoids leaking raw \\?\\... paths into container execution.
4. Container readiness output now states plainly that validation is for the selected execution image and container path, while host-only checks stay on the native diagnosis lane.
5. ota proof runtime adds a native proof surface that captures execution topology, doctor, and up artifacts under .ota/proof/ and tears the runtime back down without repo-local glue.
6. First-class file checks and copy_if_missing actions make deterministic host prep explicit instead of hiding it in shell snippets.
7. Task-scoped prerequisite surfaces let selected workflow and task paths declare the exact runtime, tool, env, and precondition checks they need, while workflow selection stays explicit across ota tasks, ota workflows, ota execution topology, and ota up.

This release is about preserving execution intent. If the repo needs host prep, container setup, native provisioning, or runtime proof, each of those should stay on the right side of the boundary.

Use these docs to apply v1.6.10 patterns directly:

• Get Started: Install Ota and verify the repo with ota doctor.
• Contract reference: Contract for workflows, tasks, requirements, tools, and agent boundaries.
• Command reference: Commands for ota workflows, ota up, ota doctor, and ota proof runtime.
• JSON validation: JSON output for machine-readable proof, topology, and readiness surfaces.

v1.6.10 is live here: https://ota.run/releases/v1.6.10

If you already run Ota, verify quickly:

ota --versionota validateota doctorota proof runtime

If your repo depends on Windows native tooling, container-backed workflows, or task-scoped prerequisites, this release gives you cleaner selected-path behavior and better proof boundaries.