OpenCode Entry Workflow

Goal

Use OpenCode as the daily AI entry point for this workspace without losing project context.

Open this repository as its own VS Code workspace.
Run opencode from the integrated terminal at the repository root.
Use the fidelity primary agent for this project profile, or the generic workspace agent for reusable profile work.
Let project-level config load from AGENTS.md, opencode.json, .opencode/commands/, and .opencode/plugins/.
Treat .agents/ as the shared source for reusable workflows and skill/rule content; .opencode/ is the OpenCode runtime view over that source.

Run /workspace-context at the start of the day, or /fidelity-context when you want the Fidelity alias.
If live communication sync is configured, let the inbox refresh automatically or run /communication-sync.
When new work happens on the main development machine, run /sync-context ... or /log-note ....
When you need a supervisor update, run /manager-update ....
When you need polished English for Mattermost, run /translate ....
When you need a standup, run /standup.

Project instructions load automatically from opencode.json.
Root rules also load automatically from AGENTS.md.
Shared workflow/rule content can stay centralized in .agents/ while OpenCode keeps using .opencode/.
The main context command reads the reusable core/, active profile, stable workspace files, and today's log.
Stable context is split by systems, workstreams, process, people, and decisions so the agent can pull the right layer instead of overloading one project file.
Live communication context can be refreshed into ai/inbox/ using the configured connector.
Direct prompts are also treated as memory opportunities, so the agent can update workspace context during normal conversation.
Daily updates go back into the workspace, so later prompts inherit better context.
The local compaction plugin helps preserve the most important workspace context during long sessions.
This reduces reliance on fragile session memory.