AGENTS.md@packages/agent-orchestration-kit/profiles/azhou-balanced git:20261027.d2ad7faA

Immutable. This exact content never changes and is served at /api/v1/blob/9a953859edb30ebb.

<!-- ASTRA-LUNA-ORCHESTRATOR:BEGIN -->
# Global Sol/Luna orchestration with optional Astra

For complex coding tasks or explicit delegation requests, use the installed `astra-orchestrator` skill (discover it by name).
Default to Sol/high for the root and the independent `reviewer`; use Luna/max for `explorer`, `worker`, `tester`, and `researcher`. The configured role settings take precedence over generic subagent-model preferences.
Use the `astra-specialist`, instructed to stay read-only, only for an explicit Astra request, an evidenced Sol reasoning blocker, or a concrete high-risk architecture/security decision. Explain the reason, provide a bounded question, and use at most one Astra specialist at a time; follow the skill's escalation rules.
Role instructions do not create a separate permission sandbox; Codex subagents inherit the parent session permissions.
Keep small tasks in the root. Delegate for distinct value, assign non-overlapping file ownership, keep handoffs concise, wait for required agents, and report actual verification evidence. Preserve Standard speed unless the user requests otherwise.
These are the host defaults for ordinary tasks, not a claim on a task the user explicitly assigned to another workflow. When the user selects a pstack workflow for the current task, that workflow owns the task's decomposition, stages, child dispatch, and verification: start no second decomposition, delegation, or review flow on top of it, and leave the active root model unchanged. A status question or an added constraint within the same task keeps that owner; a new task after it finishes returns to these defaults. On a mid-task workflow switch, first bring running children to a recoverable boundary and stop or finish them. Ordinary delegation selects the named roles above; a selected workflow sets its children's explicit model and effort itself, and these role defaults must not override them.
Explicit user instructions and more specific project instructions take precedence. Respect project or session model overrides; never switch the active root model merely to match a default profile. Permissions, concurrency limits, and project rules apply on every path; no orchestrator chains into another.
<!-- ASTRA-LUNA-ORCHESTRATOR:END -->