skills/orchestrate-coding-agent-execution/references/session-and-context-policy.md

# Coding session and context adapter

Canonical generic rules live in [Context Package](../../../shared/expert-system/context-package.md) and [session lifecycle](../../../shared/expert-system/session-lifecycle.md). Read them for source slicing and session decisions. This adapter retains only coding-specific additions; it is not another authority or health model.

Include current repository/worktree, revision or snapshot, dirty ownership, approved task/attempt, source manifest, gate, harness/instruction versions, relevant previous failure and next acceptance evidence. Reverify identities before dispatch and acceptance; do not import unrelated company context.

Migrated projects use their approved active suite and relevant source slice. Missing coverage, conflicting references or suspicious omissions require targeted historical inspection, not loading the whole archive. A migration claim needs its accepted coverage record.

For resumption use `$handoff-work-between-chats` and its coding-agent state block. Verify recipient access; local paths are not portable by assertion. If transfer is needed, prepare an authorized artifact packet. Do not upload private code or secrets merely to simplify context. No provider installation, agent dispatch or external action is authorized by a handoff alone.