[Feat]: the agent should not be able to disable autocontinue

[mhenke]

Findings: A proposal that autocontinue should not be disableable by the agent. Autocontinue is an OpenCode-core feature with no references in this plugin's source, so the plugin cannot control its exposure. The thread showed active disagreement: a collaborator argued autocontinue-as-tool is valuable and trapping loops are the real annoyance. No repro or config was provided.

What was said:

• @ryanleecode: autocontinue is pointless if the agent can disable it.
• @ReqX (collaborator, disagreed): called it strongly opinionated and said being trapped in a loop is the bigger annoyance in omo; suggested an optional config or "nightshift mode" instead.
• @adikpb: asked whether the proposal means auto-continue should be command-only, not a bundled tool.

Open questions:

1. Should this be filed against opencode-ai/opencode instead, since autocontinue is a host-level feature?
2. Is the real ask a plugin-side config to hide autocontinue from the agent tool list, or removing the tool entirely upstream?
3. Would an optional "nightshift mode" or similar config address the underlying concern without removing the tool?

Original issue: #483