worktree-isolation

OMP Native Task Isolation

This skill defines isolation policy for Autopus executor fan-out on OMP. The native task tool owns workspace materialization, patch/branch integration, and cleanup.

Activation

Use per-item isolation only when all conditions hold:

• the current dynamic task schema exposes isolated;
• OMP settings enable a non-none isolation mode;
• the project is a git repository;
• the item writes files;
• ownership is disjoint from every concurrent item.

Do not request isolation for --solo, read-only work, overlapping ownership, shared migration numbering, or an environment where the field is absent. Missing required isolation is a blocker, not permission to imitate it with shell commands.

Native Dispatch Contract

Inspect the current dynamic schema before each wave. When it exposes batch mode, dispatch independent isolated work in one batch with top-level i and shared context. Each item uses a unique stable name, a discovered custom role when needed, a complete assignment, the discovered isolation field enabled, the strict five-field receipt schema, and schemaMode: strict. When batch mode is absent, dispatch the corresponding flat calls and reference one shared local:// context.

The parent must check dynamic availability before adding isolated or effort. isolated does not exist when task.isolation.mode = none, and effort does not exist when its setting is off. Omit either unsupported field rather than sending it from a static example.

Ownership Preflight

Before fan-out:

1. normalize every owned and forbidden path to a project-relative path;
2. reject absolute paths, traversal, symlinks, nested ownership, and ambiguous globs;
3. detect exact overlap and directory-prefix containment;
4. serialize tasks that share a generated artifact, migration directory, package manifest, lockfile, schema registry, or other mutable authority;
5. put cross-task interfaces in top-level context before dispatch.

A maximum of five Autopus executor items may be active in one wave. Queue overflow by task id. This policy is stricter than OMP's session-wide semaphore and prevents excessive integration churn.