[meta] decide on .github/copilot/coding-agent.yml MCP config (from stale-branch cruft 2026-06-02)

[hyperpolymath]

Summary

Branch claude/safedom-res-stale-sweep (PR #34 squash-merged 2026-05-27) had three subsequent ci: fix CI/CD configuration (campaigns C001-C005) commits pushed by estate-wide automation on 2026-06-01. Branch deleted during 2026-06-02 sweep — most content was superseded, but one file was net-new:

# .github/copilot/coding-agent.yml
mcp_servers:
  boj-server:
    command: npx
    args: ["-y", "@hyperpolymath/boj-server@latest"]
    env:
      BOJ_URL: http://localhost:7700

Captures the MCP server configuration for GitHub Copilot coding agent. If this is desired estate-wide, file as a standards-template item or as a per-repo opt-in. Marking as opt-in to capture decision without forcing it on the repo.

[hyperpolymath]

Status check 2026-06-02:

The file is not present in valence-shell main (gh api repos/hyperpolymath/valence-shell/contents/.github/copilot/coding-agent.yml → 404). The 2026-06-01 stale-branch automation appears to have not landed it on main — so the open-questions framing of "keep / remove / standardize" reduces to one: does valence-shell want to opt in to the estate canonical?

Estate state

• hyperpolymath/standards/.github/copilot/coding-agent.yml EXISTS and IS the canonical (identical content to the snippet in this issue):

  mcp_servers:
    boj-server:
      command: npx
      args: ["-y", "@hyperpolymath/boj-server@latest"]
      env:
        BOJ_URL: http://localhost:7700

• Valence-shell does not carry it locally.

Resolution options (owner-decides)

1. Opt-in (recommended for now): leave it not-present in valence-shell. The MCP config is canonical in standards/; downstream repos copy it in only if they actively use Copilot with the boj-server MCP. Issue closes as "owner-decided: opt-in, no per-repo file".
2. Adopt: file a small PR adding the file with content from standards/. Costs ~zero (the npx server is local-loopback).
3. Restandardize via standards template: make it part of the rsr-template / repo-skeleton so every new repo gets it. Larger scope; would suggest a separate standards-side issue.

Leaving open for owner decision; if no objection within a session or two, will close as option 1 by default.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com