Adopt the official MCP Go SDK for ward-mcp transport/session handling #20

New issue

Closed

opened 2026-07-14 09:59:19 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-14 09:59:19 +00:00

Member

Decision

Go, from coilysiren/inbox#211.

Adopt the official MCP Go SDK for the transport/session/runtime layer in ward-mcp, while preserving the current guardfile grant-to-tool projection as the product-specific logic.

Scope

Replace custom MCP protocol/session scaffolding with the official MCP Go SDK where it cleanly fits.
Keep existing tool projection semantics: guardfile grants become exposed MCP tools, denied operations stay absent.
Preserve existing HTTP/SSE behavior or document any intentional transport changes.
Add regression coverage for initialize, tools/list, tools/call, health, and current error mapping.

Non-goals

Do not change the MCP tool contract as part of this refactor.
Do not bundle this with the ward-mcp -> agent-guard-mcp rename.
Do not add Ward-specific MCP control verbs.

Parent: coilysiren/inbox#211.

## Decision Go, from coilysiren/inbox#211. Adopt the official MCP Go SDK for the transport/session/runtime layer in ward-mcp, while preserving the current guardfile grant-to-tool projection as the product-specific logic. ## Scope - Replace custom MCP protocol/session scaffolding with the official MCP Go SDK where it cleanly fits. - Keep existing tool projection semantics: guardfile grants become exposed MCP tools, denied operations stay absent. - Preserve existing HTTP/SSE behavior or document any intentional transport changes. - Add regression coverage for initialize, tools/list, tools/call, health, and current error mapping. ## Non-goals - Do not change the MCP tool contract as part of this refactor. - Do not bundle this with the ward-mcp -> agent-guard-mcp rename. - Do not add Ward-specific MCP control verbs. Parent: coilysiren/inbox#211.

coilyco-ops added the

headless

labels

2026-07-14 09:59:19 +00:00

coilyco-ops commented

2026-07-14 10:01:02 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-mcp-20 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-14T10:01:02Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward-mcp#20 · branch issue-20 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-mcp-20 · ward v0.675.0 · dispatched 2026-07-14T10:00:59Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.675.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-mcp-20` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T10:01:02Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward-mcp#20` · branch `issue-20` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-mcp-20` · ward `v0.675.0` · dispatched `2026-07-14T10:00:59Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.675.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-14 10:17:52 +00:00

Adopt the official MCP Go SDK for transport/session handling #23

coilyco-ops commented

2026-07-14 10:29:10 +00:00

Author

Member

WARDED_WORKFLOW: #23

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: mostly plumbing cleanup, with one SDK error-mapping wrinkle confidence: high surprise: the SDK mapped unknown tools to invalid params, so I rewired that edge back to method-not-found follow-ups: director merge, then close #20

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward-mcp/pulls/23 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: mostly plumbing cleanup, with one SDK error-mapping wrinkle confidence: high surprise: the SDK mapped unknown tools to invalid params, so I rewired that edge back to method-not-found follow-ups: director merge, then close #20 </details>

coilyco-ops closed this issue

2026-07-14 10:33:08 +00:00