orcho-core

Use when editing Orcho CLI behavior: orcho-core/cli/*, CLI help text, output modes, interactive prompts, stdout/stderr formatting, transcript behavior, latest/resume commands, or public `orcho`, `orcho run`, `orcho cross`, `orcho status`, `orcho evidence`, `orcho diff`, `orcho web` UX. Do not use for pipeline semantics alone.

Use when editing cross-project orchestration lifecycle and wiring: orcho-core/pipeline/cross_project/*, handoff, contract check, artifact bundle, profile projection, child dispatch, cross-project gate handoff, release-gate orchestration, and final-acceptance bundle flow. Pair with quality-gates for parser/verdict/gate semantics; do not use for single-project gate/parser changes.

Use for Orcho evidence/observability storage, emission, mirrors, bundles, events, metrics, run diff, and artifact metadata: orcho-core/pipeline/evidence/*, pipeline/observability/*, core/observability/*, pipeline/artifacts/types.py, run_diff.py, artifact_mirror.py, run_logging.py, including persisted prompt-render evidence. Do not use for prompt wording/templates/render contracts unless paired.

Use when editing orcho-core isolation and workspace safety: pipeline/project/isolation_setup.py, worktree selection/bootstrap, pre-run dirty intake, sandbox policy, runspace paths, dependency checkout subjects, git worktree tests, sandbox ADRs, or generated worktree handling. Do not use for runtime agent sessions or phase lifecycle unless paired.

Use when editing phase lifecycle/execution mechanics: phase handlers/registry, orcho-core/pipeline/phases/*, project run phase bookkeeping, subtask DAG execution, StepOutcome, subtask receipts, done-criteria attestation, phase transitions, and phase-level handoff/routing. Do not use for parser verdicts, gate decisions, or runtime adapter internals unless paired.

Use when editing Orcho profiles and plugin extension surfaces: profile schema/catalogue, semantic profiles, operating modes, profile projection, phase config, profile-driven gate scheduling/configuration, PluginConfig loading, entry-point groups for agent_runtimes/phases/skills, plugin authoring docs, and profile validation. Do not use for runtime execution internals or SDK wire unless paired.

Use when editing orcho-core parser and gate semantics: plan_parser, review_parser, release_parser, plan_contract, quality_gates, pipeline/control, review/repair/final acceptance, halt/resume/operator decisions, release verdicts. Do not use for prompt wording or public wire shape unless paired.

Use only for orcho-core triage/routing questions when the affected subdomain is unclear and no specific specialist, file path, or known subsystem is named. Route among prompt engine, runtime/session, phases/DAG, parsers/gates, evidence/observability, isolation/worktrees/sandbox, test infrastructure/goldens, cross-project, profiles/plugins, skills registry, SDK wire, and CLI UX. Do not use for implementation once a specialist scope is clear.

Use when editing Orcho runtime/session code: orcho-core/pipeline/runtime/*, pipeline/engine/session.py, pipeline/session_adapters.py, agents/runtimes/*, agents/protocols.py, agents/registry.py, runtime invocation, session continuity/reset, runtime context autonomy, or agent runtime adapters. Do not use for prompt rendering unless paired.

Use when editing orcho-core/sdk/*, docs/sdk_schema.json, public dataclasses, status/history/evidence/metrics/cost/run-diff payloads, plan/review/release wire schemas, or any core shape exposed through MCP. Pair with orcho-mcp for MCP-visible changes. Do not use for private parser internals or prompt prose.

Use when editing Orcho skill support: orcho-core/pipeline/skills/*, agents/stream_parsers/skill_registry.py, skill discovery order, .agents/.claude/.forge compatibility, trust policy, roster rendering, skill injection, skill bindings, skill traceability/events, `orcho skills list/trace`, or MCP skill catalogue exposure. Pair with sdk-wire or orcho-mcp when exposed publicly.

Use when editing orcho-core shared test infrastructure: tests/conftest.py, tests/fixtures/*, golden snapshots, snapshot normalizers, pytest config, collection hooks, acceptance fixtures, schema/golden regeneration, or broad fixture behavior. High blast radius; inspect consumers before editing.

Use only when selecting targeted tests, smoke checks, pytest marks, or verification strategy for orcho-core changes, including questions like "which tests should I run?" Covers SDK schema, prompts, runtime/session, evidence, cross-project, CLI, profiles/plugins, skills registry, golden fixtures, and acceptance mock flows. Do not use for implementation, explanation, or final integrity gates.

Use for Orcho prompt authoring/rendering internals: orcho-core/pipeline/prompts/*, orcho-core/core/_prompts/*, prompt templates/contracts, cache-aware rendering, session/delta prompt metadata, prompt snapshots, and prompt boundary tests. Pair with evidence/observability only when rendered prompt data is stored as evidence/events/artifacts.