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
{{ message }}
Repository navigation
Commit 306380c
Browse filesBrowse the repository at this point in the historyBrowse files
- Scope client evidence to server-facing changes, with a targeted probe
otherwise, and require both clients consistently
- HTTP+SSE is deprecated, not removed, in the 2026-07-28 spec
- Scope labels only where an issue concerns one server
- S7 depends on S5 and S8
- Release prep is up to three PRs under #4472's two bump PRs
- Action pinning covers claude.yml too
- Sweep dry runs write nothing
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: docs/agent-guidance-inception.md
+37-21Lines changed: 37 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ The **Sub-issue** column points into [§9](#9-proposed-sub-issues).
105
105
|`board-ops`|`gh project` recipes for two boards; ID tables; resolving option IDs by name; the option-deletion hazard and its recovery | Adapt | One board, #43. Its fields: Status (with **Incoming**), Priority, Size. Hazard and recovery copy unchanged | S5 |
106
106
|`issue-create`| Five-step create flow: version label, type label, milestone, card, Status + Priority; duplicate check across all states | Adapt | Version label is always `v2`. Add a **server-scope label** step (`server-<name>`). Milestone = nearest due v2.x | S5 |
107
107
|`issue-triage`| Two-pass sweep (board as Incoming, then human approval), priority rubric with a score comment, 12-check board audit | Adapt | The **highest-leverage skill here** given the inflow (§3.4). Add spam/registry-redirect classes, server-scope labelling, and outside-PR triage | S7 |
108
-
|`pr-flow`| Assign + In Progress, branch naming, DCO signoff, screenshots, `Closes #N`, `addCloseIssueReferences`, In Review, Copilot loop to exhaustion, per-thread replies, manual close-out | Adapt | Board #43; branch `v2/<type>/<N>-<slug>`. **DCO: N/A**, since no DCO app is installed here (§10). **Screenshots → client evidence**: Inspector/LLM-client transcript in both spec eras (§3.2). The Copilot loop copies unchanged | S6 |
108
+
|`pr-flow`| Assign + In Progress, branch naming, DCO signoff, screenshots, `Closes #N`, `addCloseIssueReferences`, In Review, Copilot loop to exhaustion, per-thread replies, manual close-out | Adapt | Board #43; branch `v2/<type>/<N>-<slug>`. **DCO: N/A**, since no DCO app is installed here (§10). **Screenshots → client evidence**: for a server-facing change, Inspector and LLM-client transcripts in both spec eras; otherwise a targeted probe (§3.2). The Copilot loop copies unchanged | S6 |
109
109
|`pre-push-gate`| Running `local:gate`; diagnosing each stage | Adapt | Rewrite around our stages: TS workspaces, Python per server, per-file coverage both sides | S10 |
110
110
|`project-structure`| Where a file goes; who owns what | Adapt | Per-server layouts (e.g. `everything`'s `tools/`, `resources/`, `prompts/`, `transports/`) | S11 |
111
111
|`local-dev`| Install/run each client; dependency-placement reasoning | Adapt | Workspaces + `uv`; running each server over stdio / Streamable HTTP; `npx`/`uvx` local builds | S11 |
@@ -197,12 +197,16 @@ The **Sub-issue** column points into [§9](#9-proposed-sub-issues).
197
197
-**Protocol-level client harnesses, in-process**: an SDK `Client` (TS) or
198
198
`ClientSession` (Py) over an in-memory transport, asserting on the wire. This
199
199
is the design of #4854/#4855, and the `testing` skill (S11) documents it.
200
-
-**Client smoke tests in both spec eras**, per #4857: every change is checked
201
-
against a 2026-07-28 client and a 2025-11-25 client, using the Inspector V2
202
-
and an LLM client. This replaces the Inspector's screenshot rule. Instead of
203
-
images, a PR carries **client evidence**: what the Inspector (or an LLM
204
-
client) was asked to do, and what it returned. That gives the `client-smoke`
205
-
skill (S11) and the `pr-flow` evidence step (S6).
200
+
-**Client smoke tests in both spec eras**, per #4857: every change to
201
+
**server behavior** is checked against a 2026-07-28 client and a 2025-11-25
202
+
client, using **both** the Inspector V2 and an LLM client. This replaces the
203
+
Inspector's screenshot rule. Instead of images, a server-facing PR carries
204
+
**client evidence**: what each client was asked to do, and what it returned.
205
+
A change with no client-observable surface (docs, skills, workflows, gate
206
+
tooling) instead carries a **targeted probe**, as the Inspector's ledger
207
+
allows: the thing that proves it, such as a guard made to fire or a
208
+
before/after run. That gives the `client-smoke` skill (S11) and the
209
+
`pr-flow` evidence step (S6).
206
210
-**Interface-diff CI** (#4860) gives interface-level evidence that a change
207
211
is transparent. The gate sub-issue (S10) wires it in once #4860 lands.
208
212
@@ -273,7 +277,7 @@ deleting. Every section goes somewhere:
273
277
| MCP Protocol Reference (`.mcp.json` docs server, schema repo) |`AGENTS.md`: a two-line rule to look protocol questions up via the `mcp-docs` server, with a link to the schema repo | S1 |
274
278
| Key Patterns: `registerTools`/`registerResources`/`registerPrompts`|`AGENTS.md` TS instructions (the rule). Where each server keeps them goes to `project-structure`| S1, S11 |
275
279
| Key Patterns: tool annotations |`AGENTS.md` (rule: set `readOnlyHint`, `idempotentHint`, `destructiveHint` on every tool) | S1 |
276
-
| Key Patterns: transports |`AGENTS.md`: stdio default, Streamable HTTP; **SSE is deprecated** (and removed by the 2026-07-28 spec, #4857) | S1 |
280
+
| Key Patterns: transports |`AGENTS.md`: stdio default, Streamable HTTP; **HTTP+SSE is deprecated** (still deprecated, not removed, in the 2026-07-28 spec, #4857) | S1 |
277
281
| Key Patterns: PR template checklist |`AGENTS.md` Contributing (MCP docs read, security practice, tested with an LLM client). The evidence step goes to `pr-flow`| S1, S6 |
278
282
279
283
`src/everything/AGENTS.md` (a per-server guide) also exists. S1 decides its
@@ -390,7 +394,7 @@ the Servers V2 board (#43). "After" means the listed issue must merge first.
0 commit comments