docs/SUPPORT.md

# Support

Report reproducible problems or request improvements through [GitHub Issues](https://github.com/battle-doll/orbit-secretary/issues). Orbit Secretary is maintained by [battle-doll](https://github.com/battle-doll). Support is provided on a best-effort basis, with no guaranteed response time.

## Before reporting a problem

Record the package version, operating system, Codex host/version if visible, the action requested and whether the required native task tools were available. For source-tool problems, include Python version and the failing command's redacted output. Distinguish a missing host capability from a package defect.

Use a minimal synthetic reproduction. Do not include raw session archives, private task text, account tokens, credentials, personal data or unrelated project contents. For suspected sensitive-data exposure, stop sharing the data. Public issues are not a confidential channel; do not include sensitive details.

## Known limits

- A partial task inventory cannot support a complete account-wide briefing.
- An idle task can still have an incomplete objective; a completed objective should not be restarted merely because the task is idle.
- Finite Act requires explicit scope and currently callable host tools. Missing tools produce a draft and a capability explanation.
- No unattended schedule, persistent supervisor or verified complete OFF cancellation is included.
- An unknown message-send outcome must be reconciled; blindly resending can duplicate instructions.
- A nickname in a loaded manager conversation does not establish global alias routing. Use `$orbit` for explicit invocation where the host supports it.

For local source checks, follow [Platform support](PLATFORM_SUPPORT.md). Do not interpret passing offline fixtures as evidence of installation, all-platform support, marketplace acceptance or live host cancellation.