Merge pull request #57 from ScriptKittyOS/chore/approve-061

feat(s061): slice 061 approved; the README counts 22 tags

Signed-off-by: Ayla Croft <aylacroft@proton.me>

Author: HackTuah

README.md

@@ -10,10 +10,10 @@ desktop application. Apache-2.0, developed in the open from the first commit.
 
 ## Status
 
-Pre-alpha, and usable from source. Milestones M0 to M4 are approved, and the first two slices
-of M5a (059, the MCP measurement; 060, the MCP client) with them: 21 slices, each merged with a
-merge commit and tagged `slice/NNN` (`git tag -l 'slice/*' | wc -l` → 21, on 2026-09-21). What
-that means in practice:
+Pre-alpha, and usable from source. Milestones M0 to M4 are approved, and three slices of M5a
+(059, the MCP measurement; 060, the MCP client; 061, the MCP server) with them: 22 slices, each
+merged with a merge commit and tagged `slice/NNN` (`git tag -l 'slice/*' | wc -l` → 22, on
+2026-09-22). What that means in practice:
 
 - **Talks.** Streaming chat with any provider behind one behaviour (`Trinity.LLM`), switched by
   configuration; the assistant's text is persisted as a draft every 500 ms or 2 KB while it
@@ -143,7 +143,7 @@ engineering contract that every change is held to.
 | M7 Sandboxed | Executable skills in an in-VM sandbox | 110 approved |
 | M9 Donatable | Open-source hygiene audited, supply chain signed, shared libraries extracted | 002 and 120 to 123 approved |
 
-M0 to M4 are approved as of 2026-09-21, and 059 and 060 of M5a with them. Slice numbers have gaps on purpose (000, 001, 010, 011 and so on) so that a slice can be inserted
+M0 to M4 are approved as of 2026-09-22, and 059, 060 and 061 of M5a with them. Slice numbers have gaps on purpose (000, 001, 010, 011 and so on) so that a slice can be inserted
 later without renumbering anything.
 
 ## What is in the repository

ROADMAP.md

@@ -54,7 +54,7 @@ standards register names the rows that ask for them.
 | 050 | Scheduler: Oban cron agent tasks with delivery targets | 5 Automation | M | 012 | planned |
 | 059 | MCP capability gap against beam_mcp, and the server seam probe | 6 MCP | S/M | 020 | approved |
 | 060 | MCP client: Trinity's thin driver (2026-07-28 preferred, 2025-11-25 compat, MRTR, Tasks) | 6 MCP | L | 059, 021 | approved |
-| 061 | MCP server (stateless 2026-07-28 + compat, MRTR approvals, headless profile) | 6 MCP | M | 060, 024 | done |
+| 061 | MCP server (stateless 2026-07-28 + compat, MRTR approvals, headless profile) | 6 MCP | M | 060, 024 | approved |
 | 062 | MCP authorization: OAuth client role, RS, embedded AS, Enterprise Managed Authorization (ID-JAG) | 6 MCP | L | 061 | planned |
 | 070 | Gateway core: adapter behaviour, routing, PubSub fan-out | 7 Gateways | M | 012 | planned |
 | 071 | Gateway: Telegram | 7 Gateways | S | 070 | planned |