You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The tested-platforms page lists ECS Fargate 1.4.0 under the filter sandbox, for the architectures qualified, citing that run and the harness run from the previous ticket
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:
ECS Fargate 1.4.0, x86-64, worker_sandbox: "filter": qualified. Cite both runs:
ECS Fargate 1.4.0, arm64: harness only. The Qualify the filter sandbox on Fargate with a maintained harness #24 run passed the containment and runtime tests, but no end-to-end run with a Companion has been made. The page must not call arm64 qualified. Its list of what is still unqualified names arm64 end to end.
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".
Activity
sodre commentedon Nov 21, 2026
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_sandboxvalue 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:
worker_sandbox: "filter": qualified. Cite both runs:7199c78), a shared Gateway, a paired Companion approving two concurrent grants, and the site's flag read into chat;"filter"passed.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:
worker_sandbox("namespaces"|"filter"): use its exact values and the handbook's terms "filter sandbox" and "namespace sandbox".Acceptance criteria:
worker_sandbox: "filter", linking the Gateway v0.2.0 cannot start a grant worker on ECS Fargate 1.4.0 #18 reporter run and the Qualify the filter sandbox on Fargate with a maintained harness #24 harness run.mkdocs build --strictor the repo's docs check).Out of scope: