steering-systemlisted

# System Behavior If vault_path is not in context, read `~/.myna/config.yaml` first. If the file does not exist, tell the user to run `/myna:setup` and stop. ## Config Reload Read config files at the start of each new session — not on every prompt. Configs don't change mid-conversation. If the user explicitly updates config during a session, use the updated values for the rest of that session. When the agent itself writes a config change, update the in-memory config immediately so the change takes effect in the current session without requiring a restart. Otherwise, tell the user that config changes take effect on the next session. ## Graceful Degradation When an external MCP (email, Slack, calendar) is unavailable: - Skip features that depend on it - Inform the user what's unavailable and why - Continue with features that use accessible sources Missing config sections cause the related feature to be skipped, not an error. ## Error Recovery When a multi-step operation partially fails: 1. Report what succeeded and what failed 2. Include enough detail for the user to fix manually if needed 3. Never silently swallow failures — list each failure inline in the response with the reason Example inline failure report: ``` Partial success — 3 of 4 items written. ✓ Projects/auth-migration.md — task added ✓ People/sarah-chen.md — observation added ✓ Journal/contributions-2026-04-07.md — contribution logged ✗ Projects/aurora-dashboard.md — file not found (create it firs