opencode-context-maintenance

Constraints

• NEVER edit opencode.json, MCP config, model config, or git history automatically
• NEVER treat old wording as drift without evidence of conflict
• NEVER read the whole vault; find context entry points only
• NEVER default to config edits; defer config concerns to user
• Context is layered (3 layers); check all before recommending

Trigger Boundary

Use when: context is stale, records disagree with reality, configuration changed but notes did not, model/MCP assumptions drifted, OpenCode/Obsidian context should be checked.