Converge selected native MCP mounts across hosts and warded agents #609

New issue

Closed

opened 2026-07-23 17:57:06 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-23 17:57:06 +00:00

Owner

Dependency

Depends on coilyco-bridge/agentic-os-kai#748 and participates in coilyco-flight-deck/agentic-os#655.

Problem

The kai-config role links the canonical mcporter inventory and hydrates Claude, but it intentionally leaves Codex on the lazy CLI path. A manual sync on one host renders the inventory into Codex config, which proves the generator path but does not converge the fleet or warded containers.

Goal

Converge the selected-native MCP policy from agentic-os-kai across personal host harnesses and warded containers. The first required server is the existing tailnet Forgejo issue MCP. Unselected MCPs remain lazy.

Acceptance

Run the agentic-os-kai Codex projection from the kai-config role after the mcporter inventory link step.
Check mode uses the projection's dry-run or drift-check path and reports change without writing.
Claude and Codex receive the selected-native set defined by agentic-os-kai #748, not an infrastructure-owned duplicate list.
Warded container startup carries the same selected-native projection or deterministic generated artifact alongside the existing lazy mcporter inventory.
Base and work host classes do not receive Kai-private MCP inventory.
Existing lazy mcporter access remains available for unselected servers.
A new eligible Claude or Codex session discovers the guarded Forgejo issue tools without requiring AWS SSO.
Session restart or regeneration requirements are explicit. A config write is not reported as live in an already-running harness.
AOS #656 measures the eager Forgejo schemas on every lane that receives them and confirms zero eager cost on lanes that do not.
Add idempotence, check-mode, missing-checkout, host-class, selected-only, and warded-container fixture coverage.
Update the kai-config and warded-mcporter walkthroughs to replace the blanket “Codex stays lazy” statement with the selected-native contract.
Live reachability verification is an operator/director checkpoint. Engineers prove repository wiring locally and do not iterate against the cluster.

Done condition

Infrastructure convergence leaves the eligible fleet with no generated MCP drift, fresh sessions expose Forgejo through the native selected surface, and all other inventory entries remain lazy unless separately approved.

## Dependency Depends on coilyco-bridge/agentic-os-kai#748 and participates in coilyco-flight-deck/agentic-os#655. ## Problem The kai-config role links the canonical mcporter inventory and hydrates Claude, but it intentionally leaves Codex on the lazy CLI path. A manual sync on one host renders the inventory into Codex config, which proves the generator path but does not converge the fleet or warded containers. ## Goal Converge the selected-native MCP policy from agentic-os-kai across personal host harnesses and warded containers. The first required server is the existing tailnet Forgejo issue MCP. Unselected MCPs remain lazy. ## Acceptance * Run the agentic-os-kai Codex projection from the kai-config role after the mcporter inventory link step. * Check mode uses the projection's dry-run or drift-check path and reports change without writing. * Claude and Codex receive the selected-native set defined by agentic-os-kai #748, not an infrastructure-owned duplicate list. * Warded container startup carries the same selected-native projection or deterministic generated artifact alongside the existing lazy mcporter inventory. * Base and work host classes do not receive Kai-private MCP inventory. * Existing lazy mcporter access remains available for unselected servers. * A new eligible Claude or Codex session discovers the guarded Forgejo issue tools without requiring AWS SSO. * Session restart or regeneration requirements are explicit. A config write is not reported as live in an already-running harness. * AOS #656 measures the eager Forgejo schemas on every lane that receives them and confirms zero eager cost on lanes that do not. * Add idempotence, check-mode, missing-checkout, host-class, selected-only, and warded-container fixture coverage. * Update the kai-config and warded-mcporter walkthroughs to replace the blanket “Codex stays lazy” statement with the selected-native contract. * Live reachability verification is an operator/director checkpoint. Engineers prove repository wiring locally and do not iterate against the cluster. ## Done condition Infrastructure convergence leaves the eligible fleet with no generated MCP drift, fresh sessions expose Forgejo through the native selected surface, and all other inventory entries remain lazy unless separately approved.

coilyco-ops referenced this issue from a commit

2026-07-23 18:53:29 +00:00

feat: converge shared native MCP projection (closes #609)

coilyco-ops closed this issue

2026-07-23 18:53:29 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/infrastructure#609

No description provided.

Rows
Columns