refactor(help): update `engram --help` output to show the right configuration example for engram mcp addition

[pablon]

📋 Pre-flight Checks

• I have searched existing issues and this is not a duplicate
• I understand this issue needs status:approved before a PR can be opened

📝 Bug Description

engram --help instructs the user to add the following block to opencode.json:

{
  "mcp": {
    "engram": {
      "type": "stdio",
      "command": "engram",
      "args": ["mcp", "--tools=agent"]
    }
  }
}

This produces the following error @ opencode:

❯ opencode
Error: Configuration is invalid at ~/.config/opencode/opencode.json
↳ Invalid input mcp.engram

Using the following syntax seems to go through, opencode opens without complaining:

{
  "mcp": {
    "engram": {
      "type": "local",
      "command": ["engram", "mcp", "--tools=agent"],
      "enabled": true
    }
}

🔄 Steps to Reproduce

1. Configure engram mcp as instructed by engram --help in opencode.json:

{
  "mcp": {
    "engram": {
      "type": "stdio",
      "command": "engram",
      "args": ["mcp", "--tools=agent"]
    }
  }
}

2. Start opencode:

❯ opencode

You will see the following error:

Error: Configuration is invalid at ~/.config/opencode/opencode.json
↳ Invalid input mcp.engram

Note

❯ opencode --version
1.2.27

❯ engram --version
engram 1.10.1

✅ Expected Behavior

❯ opencode mcp list

┌  MCP Servers
│
●  ✓ engram connected
│      engram mcp --tools=agent
│
└  1 server(s)

❌ Actual Behavior

❯ opencode
Error: Configuration is invalid at ~/.config/opencode/opencode.json
↳ Invalid input mcp.engram

Operating System

macOS

Engram Version

1.10.1

Agent / Client

OpenCode

📋 Relevant Logs

💡 Additional Context

No response

[pablon]

Linked to PR #89

[Alan-TheGentleman]

Approving this issue because the bug is real: the confusing part is the output, not the setup flow itself. ✓ Installed opencode plugin (2 files)
→ /Users/alanbuscaglia/.config/opencode/plugins

Next steps:

1. Restart OpenCode — plugin + MCP server are ready
2. Run 'engram serve &' for session tracking (HTTP API) already writes the correct format, but the example is still misleading. A follow-up fix should align the help text with the actually supported OpenCode configuration instead of introducing extra fields casually.

[Alan-TheGentleman]

Correcting the implementation note clearly: the bug here is the confusing help output, not the setup flow itself.

engram setup opencode already writes the correct OpenCode configuration format. The remaining fix should align the help text with the actually supported OpenCode config instead of introducing extra fields casually.