Skip to content

List Fargate as a tested platform #25

Closed

Description

@sodre

Parent

#21

What to build

Fargate joins the tested platforms once the reporter on #18 has qualified the filter sandbox on their own deployment. Their run uses two concurrent grants: a paired Companion approves a client certificate, then the mock MCP tool reads the mTLS-protected flag into chat. This waits on someone outside the team, so it is not for an agent.

Acceptance criteria

Decided in: #21 (spec); ADR 0001; the probe and research on prototype/18-isolation-probe
Live step at merge: none

Activity

  1. added theissue type on Nov 20, 2026
  2. added and removed on Nov 21, 2026
  3. sodre commented on Nov 21, 2026

    @sodre
    MemberAuthor

    This was generated by AI during triage.

    Agent Brief

    Category: enhancement
    Summary: List ECS Fargate 1.4.0 x86-64 under the filter sandbox on the handbook's tested-platforms page, and close #18

    Why this moves from ready-for-human to ready-for-agent: the step only a human could take, the reporter's own Fargate run, is done. It passed on 2026-11-21 and is recorded on #18. What remains is documentation and closing issues.

    Current behavior:
    The handbook's "Tested platforms" reference page covers desktops (native identity and packages) and end-to-end runs, but says nothing about which Gateway hosts each worker_sandbox value has been qualified on. Fargate appears in the handbook only as the example host for "filter" and as the maintainer's qualification harness. #18 is still open.

    Desired behavior:
    The tested-platforms page has a section on Gateway hosts that says which hosts the worker sandbox has been qualified on, and with what evidence:

    Each run is cited with the revision it exercised, because the page's opening line names a single implementation revision that these runs do not share.

    After the change merges, close #18 with a comment linking the v0.2.1 release, the first release that carries the filter sandbox.

    Key interfaces:

    • The handbook page titled "Tested platforms" under Reference (in the docs site nav).
    • The Gateway configuration field worker_sandbox ("namespaces" | "filter"): use its exact values and the handbook's terms "filter sandbox" and "namespace sandbox".

    Acceptance criteria:

    Out of scope:

  4. self-assigned this
    on Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions