Skip to content

Route pinned operations through SSH and registered host environments #400

Closed

Description

@ecochran76

Parent

#393

What to build

Windows/WSL/remote registration, SSH-principal mapping, fleet freshness and caller-independent single execution authority; disconnected mutation effects stay explicit.

Acceptance criteria

  • Windows/WSL/remote registration, SSH-principal mapping, fleet freshness and caller-independent single execution authority; disconnected mutation effects stay explicit.
  • Demonstrate the stated end-to-end behavior through public operations and every capable CLI/API/MCP surface.
  • Cover authorized success, stale/unsupported/unauthorized targets and relevant crash/reconnect or uncertain-effect cases.
  • Record source/package evidence and preserve existing work, authority and cumulative accounting; production effects need separate authorization.

Existing upgrade reconciliation

New controller capability; reuse the existing owners and the specification’s recorded decisions. No existing completed acceptance is invalidated.

Delivery boundary

Use public-seam TDD and exact red/green receipts. Source, integration, installed disposable acceptance and production activation are distinct. No provider experiment, credential copying, shared restart, governor activation or resource renewal is implied.

Activity

  1. self-assigned this
    on Oct 30, 2026
  2. ecochran76 commented on Oct 30, 2026

    @ecochran76
    ContributorAuthor

    Integrated0d895443+92f05ff and full public acceptance18f83fac. Primary rebuilt/reinstalled combined integration538694c and reran installed host acceptance successfully: actual CLI, stdio MCP, OAuth API/MCP/remote CLI list/resolve/routing, exact authority generations, scope attenuation, revocation, offline refusal and uncertain/no-replay receipts. SSH-shaped executable is explicitly synthetic; real separate-host Windows/WSL/SSH matrix remains405.34 integrated controller tests pass. Evidence docs/dev/evidence/plan0190/hosts400-public.md. No production effects or provider credentials. Closing source plus isolated installed contract; no real-fleet deployment claim.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

ready-for-agentMatt engineering triage state: ready-for-agent

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions